isdaniel/mcp_weather_server

mcp-name: io.github.isdaniel/mcp_weather_server
A Model Context Protocol (MCP) server that provides weather information using the Open-Meteo API. This server supports multiple transport modes: standard stdio, HTTP Server-Sent Events (SSE), and the new Streamable HTTP protocol for web-based integration.
Features
Weather & Air Quality
* Get current weather information with comprehensive metrics:
* Temperature, humidity, dew point
* Wind speed, direction, and gusts
* Precipitation (rain/snow) and probability
* Atmospheric pressure and cloud cover
* UV index and visibility
* "Feels like" temperature
* Sunrise and sunset times (local time at the location)
* Get weather data for a date range with hourly details and daily sunrise/sunset times
* Get air quality information including:
* PM2.5 and PM10 particulate matter
* Ozone, nitrogen dioxide, carbon monoxide
* Sulfur dioxide, ammonia, dust
* Aerosol optical depth
* Health advisories and recommendations
Time & Timezone
* Get current date/time in any timezone
* Convert time between timezones
* Get timezone information
Transport Modes
* Multiple transport modes:
* **stdio** - Standard MCP for desktop clients (Claude Desktop, etc.)
* **SSE** - Server-Sent Events for web applications
* **streamable-http** - Modern MCP Streamable HTTP protocol with stateful/stateless options
* RESTful API endpoints via Starlette integration
Installation
Installing via Smithery
To install Weather MCP Server automatically via Smithery:
Standard Installation (for MCP clients like Claude Desktop)
This package can be installed using pip:
Manual Configuration for MCP Clients
This server is designed to be installed manually by adding its configuration to the cline_mcp_settings.json file.
1. Add the following entry to the mcpServers object in your cline_mcp_settings.json file:
2. Save the cline_mcp_settings.json file.
HTTP Server Installation (for web applications)
For HTTP SSE or Streamable HTTP support, you'll need additional dependencies:
Server Modes
This MCP server supports **stdio**, **SSE**, and **streamable-http** modes in a single unified server:
Mode Comparison
| Feature | stdio | SSE | streamable-http |
|---------|-------|-----|-----------------|
| **Use Case** | Desktop MCP clients | Web applications (legacy) | Web applications (modern) |
| **Protocol** | Standard I/O streams | Server-Sent Events | MCP Streamable HTTP |
| **Session Management** | N/A | Stateful | Stateful or Stateless |
| **Endpoints** | N/A | /sse, /messages/ | /mcp (single) |
| **Best For** | Claude Desktop, Cline | Browser-based apps | Modern web apps, APIs |
| **State Options** | N/A | Stateful only | Stateful or Stateless |
1. Standard MCP Mode (Default)
The standard mode communicates via stdio and is compatible with MCP clients like Claude Desktop.
2. HTTP SSE Mode (Web Applications)
The SSE mode runs an HTTP server that provides MCP functionality via Server-Sent Events, making it accessible to web applications.
**SSE Endpoints:**
- GET /sse - SSE endpoint for MCP communication
- POST /messages/ - Message endpoint for sending MCP requests
3. Streamable HTTP Mode (Modern MCP Protocol)
The streamable-http mode implements the new MCP Streamable HTTP protocol with a single /mcp endpoint. This mode supports both stateful (default) and stateless operations.
**Streamable HTTP Features:**
- **Stateful mode (default)**: Maintains session state across requests using session IDs
- **Stateless mode**: Creates fresh transport per request with no session tracking
- **Single endpoint**: All MCP communication happens through /mcp
- **Modern protocol**: Implements the latest MCP Streamable HTTP specification
**Streamable HTTP Endpoint:**
- POST /mcp - Single endpoint for all MCP communication (initialize, tools/list, tools/call, etc.)
**Command Line Options:**
**Example SSE Usage:**