Skip to main content
Glama
MCP Weather Server

MCP Weather Server

by jakebailey15

MCP Weather Server

A Model Context Protocol server exposing three weather tools over the free Open-Meteo API, for use with Claude Desktop or any MCP client.

Tools

Tool

Description

get_current_weather(city)

Current temperature, feels-like, precipitation, wind

get_forecast(city, days)

Daily highs, lows, and precipitation, 1–16 days ahead

get_historical(city, date)

Past conditions for a given date (archive lags ~5 days)

City names are resolved to coordinates via Open-Meteo's geocoding endpoint, so tools take plain names rather than lat/long. No API key required.

Related MCP server: mcp-weather

Setup

uv venv
source .venv/bin/activate
uv add "mcp[cli]" httpx

Use with Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "weather": {
      "command": "/absolute/path/to/.venv/bin/python",
      "args": ["/absolute/path/to/weather.py"]
    }
  }
}

Restart Claude Desktop. Both paths must be absolute.

Notes

Built against MCP Python SDK v2 (MCPServer, formerly FastMCP). Runs over stdio, so the client launches the server as a subprocess.

Known limitations

  • No retry or timeout handling on the upstream API; a network failure surfaces as a tool error rather than a graceful message.

  • Unknown city names return a message, but ambiguous ones silently take the first geocoding match.

Available Tools

3 tools
get_current_weatherB

Get current weather conditions for a city.

Args: city: Name of the city, e.g. "Toronto" or "London, Ontario"

Inputs: city (required). Returns: result

get_forecastA

Get a multi-day weather forecast for a city.

Args: city: Name of the city, e.g. "Toronto" days: How many days ahead to forecast, 1 to 16. Defaults to 3.

Inputs: city (required), days. Returns: result

get_historicalA

Look up past weather for a city on a specific date.

Args: city: Name of the city, e.g. "Toronto" date: The date in YYYY-MM-DD format. Must be at least 5 days in the past.

Inputs: city (required), date (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct temporal scope: current, forecast, and historical weather. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow the same verb_noun pattern (get_ + descriptor) with consistent parameter naming for city, making them predictable.

    Tool Count5/5

    Three tools cover the core weather server domain—current conditions, forecasts, and historical data—without unnecessary bloat or missing essentials.

    Completeness5/5

    The tool surface provides full coverage for typical weather queries: current, future, and past. No obvious gaps exist for a server of this scope.

    Maintenance

    ActivityStale
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides current weather information and forecasts for major cities through MCP tools and resources. Supports getting weather data, multi-day forecasts, and listing available cities with mock data for demonstration purposes.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables to interact with comprehensive weather data through the MCP protocol, including current conditions, multi-day forecasts, hourly forecasts, and geocoding.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables MCP clients to search for locations, fetch weather forecasts, and retrieve forecast meteogram images through the meteoblue Weather API.
      3
      17 npm
      1
      MIT