MCP Weather SSE Server
@jdhettema
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?
It is a Model Context Protocol (MCP) server that connects to the OpenWeatherMap API via Server-Sent Events (SSE) to provide real-time weather data to AI tools like Claude, CursorAI, and MCP-Inspector.
How to use MCP Weather SSE Server?
Install the server, create a virtual environment, and install dependencies (pip install mcp requests). Start it with your OpenWeatherMap API key using a command-line argument (--api-key) or the OPENWEATHER_API_KEY environment variable. Then configure your MCP client (e.g., Cursor AI, Claude Desktop) to connect to the SSE endpoint at http://127.0.0.1:3001/sse.
Key features of MCP Weather SSE Server
- Implements the Model Context Protocol for seamless AI tool integration
- Uses SSE transport for real-time communication
- Connects to OpenWeatherMap API for live weather data
- Provides three weather query tools: current, forecast, and by coordinates
- Supports optional metric or imperial units
- Defaults to localhost for safe local use
Use cases of MCP Weather SSE Server
- Ask an AI assistant for the current weather in any city
- Request a multi-day weather forecast for travel planning
- Get weather data for specific geographic coordinates
- Integrate live weather information into custom AI workflows
FAQ from MCP Weather SSE Server
What are the prerequisites?
Python 3.8+ and a free API key from OpenWeatherMap.
How do I start the server?
Run python mcp_weather_sse.py --api-key YOUR_API_KEY or export OPENWEATHER_API_KEY and run without the flag. Customize host/port with --host and --port.
What clients can connect to this server?
Claude Desktop, Cursor AI, and MCP-Inspector are explicitly supported.
What tools does the server provide?
Three tools: get_current_weather (by city), get_weather_forecast (city + days), and get_weather_by_coordinates (latitude/longitude).
What security measures are in place?
The server binds to 127.0.0.1 by default. For production, you should implement authentication, HTTPS, and rate limiting to protect your OpenWeatherMap API quota.
