MCP Weather SSE Server

Created By
jdhettemaa year ago
An MCP server that connects AI assistants to real-time weather data through OpenWeatherMap API using Server-Sent Events.
Overview

What is MCP Weather SSE Server?

MCP Weather SSE Server is a Model Context Protocol (MCP) server that connects AI assistants to real-time weather data through the OpenWeatherMap API using Server-Sent Events (SSE).

How to use MCP Weather SSE Server?

To use the server, clone the repository, set up a virtual environment, install dependencies, and start the server with your OpenWeatherMap API key. Connect it with AI clients like Cursor AI or Claude Desktop by configuring the server settings.

Key features of MCP Weather SSE Server?

  • Implements the Model Context Protocol for seamless integration with AI tools.
  • Uses Server-Sent Events (SSE) for real-time communication.
  • Connects to the OpenWeatherMap API to fetch live weather data.
  • Provides tools to get current weather, multi-day forecasts, and weather by geographic coordinates.

Use cases of MCP Weather SSE Server?

  1. Providing real-time weather updates to AI assistants.
  2. Enabling AI clients to fetch weather data for various locations.
  3. Supporting applications that require live weather information for decision-making.

FAQ from MCP Weather SSE Server?

  • What programming language is used?

The server is built using Python 3.8 and above.

  • Do I need an API key?

Yes, you need to sign up at OpenWeatherMap to get an API key.

  • Is the server secure?

By default, the server binds to 127.0.0.1, making it accessible only from your local machine. For production, implement proper security measures.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jdhettema
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago