Meteoswiss Mcp

🌦️ meteoswiss-mcp

[CI] [PyPI] [Python] [License: MIT] [swiss-public-data-mcp]

MCP server for Swiss weather and climate data from MeteoSwiss.

Connects AI models to the SwissMetNet measurement network (160+ stations, 10-minute interval), MeteoSwiss ICON-CH1/CH2-EPS forecasts and climate normals 1991–2020. Part of the swiss-public-data-mcp portfolio.

🇩🇪 Deutsche Version

Demo query (anchor example)

How suitable is next Wednesday for the sports day at Leutschenbach school?

→ meteo_school_check(location="Zürich Oerlikon", activity="Sporttag") returns a 🟢/🟡/🔴 traffic light for each day of the coming week — straight from the MeteoSwiss ICON model.

Combined with swiss-environment-mcp:

How were air quality and weather at Leutschenbach school yesterday?

→ meteo_current(station='REH') + env_nabel_current(station='ZUE') = a complete environmental picture. → More use cases by audience →

Tools (6)

Tool annotations (MCP hints)

All tools carry explicit MCP annotations — relevant for the client approval UI and for the LLM's safety decisions.

Read rules: all 6 tools are readOnly + non-destructive — the server fundamentally cannot write or delete anything. idempotentHint=False marks tools that return different values depending on when they are called.

MCP protocol version

→ Full roadmap & update strategy: docs/roadmap.md

Quick start

Claude Desktop

{  "mcpServers": {    "meteoswiss": {      "command": "uvx",      "args": ["meteoswiss-mcp"]    }  }}

Claude Desktop (local development)

{  "mcpServers": {    "meteoswiss": {      "command": "uv",      "args": ["run", "--directory", "/path/to/meteoswiss-mcp", "meteoswiss-mcp"]    }  }}

Cloud / Render.com (Streamable HTTP)

Configuration via ENV variables (the CLI flags --http / --port N still work as an override):

# Local test (safe, loopback only)MCP_TRANSPORT=streamable-http meteoswiss-mcp
# Container / RenderMCP_TRANSPORT=streamable-http MCP_HOST=0.0.0.0 MCP_ALLOW_ANY_HOST=1 meteoswiss-mcp

Docker / Render

The repo includes a production-ready multi-stage Dockerfile (non-root user, HEALTHCHECK) and a render.yaml blueprint:

# Build + test locallydocker build -t meteoswiss-mcp .docker run --rm -p 8000:8000 meteoswiss-mcpcurl http://127.0.0.1:8000/health   # → {"status":"ok","service":"meteoswiss-mcp"}

On Render: "New → Blueprint" → select the repo. Defaults (plan starter, Frankfurt, single instance) are set in render.yaml.

Important: numInstances: 1 is set deliberately — sticky-session routing for multi-replica (audit SCALE-002/003) is not yet implemented.

Structured logging

All tool invocations, upstream failures and egress blocks are emitted as JSON events on stderr (stdio-transport safe). Example:

{"tool": "meteo_forecast", "days": 7, "has_coords": false, "event": "tool_invoked", "level": "info", "timestamp": "2026-05-20T07:00:00Z"}{"tool": "meteo_forecast", "endpoint": "geocoding", "error_type": "HTTPStatusError", "event": "upstream_failed", "level": "warning", "timestamp": "..."}{"url": "https://evil.example.com/", "method": "GET", "reason": "host not in allow-list", "event": "egress_blocked", "level": "warning", "timestamp": "..."}

HTTP-mode security

• MCP_HOST deliberately defaults to 127.0.0.1 so that --http on a dev laptop is not accidentally exposed to the local subnet (audit finding SEC-016).
• All outgoing HTTP calls (including redirect follows) are validated against an allow-list: data.geo.admin.ch, api.open-meteo.com, geocoding-api.open-meteo.com, opendata.swiss. Other hosts and IP literals (in particular 169.254.169.254, RFC1918) are rejected with EgressBlocked (SEC-004 / SEC-021).
• CORS: disabled by default (same-origin only). Browser clients (e.g. claude.ai web) need MCP_ALLOWED_ORIGINS=<csv> — the Mcp-Session-Id header is then automatically in Access-Control-Expose-Headers (SDK-004).
• API-key auth: disabled by default. In a production HTTP setup, always set MCP_API_KEY=<random> — requests without a valid X-API-Key or Authorization: Bearer … are rejected with 401 (SEC-009 / SEC-013). /health stays open for container health probes.

Example: production HTTP stack

# 32 bytes of randomness as the auth keyexport MCP_API_KEY=$(python -c "import secrets; print(secrets.token_urlsafe(32))")
MCP_TRANSPORT=streamable-http \MCP_HOST=0.0.0.0 \MCP_ALLOW_ANY_HOST=1 \MCP_ALLOWED_ORIGINS=https://app.example.com \MCP_API_KEY="$MCP_API_KEY" \meteoswiss-mcp

Example queries

School planning

Which days next week are suitable for a sports day in Zürich?→ meteo_school_check(location="Zürich", activity="Sporttag")
What will the weather be at Leutschenbach school on Friday?→ meteo_forecast(location="Zürich Oerlikon", days=5)
Show me current readings from the nearest MeteoSwiss station to Zürich-Schwamendingen.→ meteo_current(station="REH")

Climate comparison

How much rain normally falls in June in Zürich?→ meteo_climate_normals(station="KLO")
Is Lugano really much sunnier than Zürich? Show me the annual values.→ meteo_climate_normals(station="LUG") + meteo_climate_normals(station="SMA")

Infrastructure & environment

Are there currently any weather warnings for the canton of Zürich?→ meteo_warnings(canton="ZH")
Show me a 10-day forecast for the Heerenschürli sports facility with hourly values.→ meteo_forecast(location="Sportanlage Heerenschürli Zürich", days=10, hourly=True)

Architecture

Claude Desktop / AI agent        │        │ MCP (stdio / Streamable HTTP)        ▼meteoswiss-mcp (MCPServer)        │        ├── meteo_stations ──────────────── [embedded: ~20 SMN stations]        │        ├── meteo_current ───────────────── BGDI STAC API        │                                   data.geo.admin.ch/api/stac/v1        │                                   Collection: ch.meteoschweiz.ogd-smn        │        ├── meteo_forecast ──────────────── Open-Meteo        ├── meteo_school_check ──────────── api.open-meteo.com/v1/meteoswiss        │                                   (MeteoSwiss ICON-CH1/CH2-EPS, 1–2 km)        │        ├── meteo_climate_normals ───────── [embedded: normals 1991–2020]        │        └── meteo_warnings ──────────────── app-prod-ws.meteoswiss-app.ch                                            (MeteoSwiss App-API) + opendata.swiss

Data sources

Safety & limits

Known limitations

Responsibility matrix — snow & precipitation (delineation vs. swiss-environment-mcp)

To avoid duplicating snow and precipitation data across the portfolio, responsibilities are split as follows. meteoswiss-mcp owns atmospheric precipitation and weather; swiss-environment-mcp (SLF domain) owns snow on the ground and avalanche danger.

Rule: atmospheric precipitation (rain/snowfall as mm) plus weather, forecast, warnings and climate normals belong to meteoswiss-mcp; snow on the ground and avalanche danger belong to swiss-environment-mcp (SLF). The SLF IMIS precipitation sensor is used there only as context for the snowpack and is never exposed as a precipitation tool, so it does not duplicate MeteoSwiss.

¹ SLF/snow tools in swiss-environment-mcp are in preparation (Phase-1 live-probe completed 2026-07-19, see that repo's docs/probe-slf.md); the demarcation is fixed now so the two servers do not collide once implemented.

Portfolio synergies

meteoswiss-mcp    │    ├── swiss-environment-mcp   Combine weather + air quality (NABEL)    │                           "How were weather AND air at Leutschenbach school?"    │    └── zurich-opendata-mcp     School locations → weather forecast                                "Which schools in Zürich have sports-day weather?"

MCP Protocol Version

This server speaks two protocol eras over the same endpoint. The client's first request on a connection decides which one applies; a later claim from the other era is refused.

Both revisions are pinned in tests/test_protocol_version.py and asserted against the installed SDK, so a Dependabot bump of mcp cannot move either one silently. It is also measured on the wire: tests/test_spec_2026.py sends real requests of both eras through the same ASGI stack main() hands to uvicorn — a 2026-07-28 tool call with no handshake and no session, and an initialize that is capped at 2025-11-25.

No deprecated capability. 2026-07-28 deprecates logging, sampling and roots (SEP-2577). The server calls none of them: in-flight status goes out as notifications/progress (reaching any client that sends a progressToken, in both eras), and failures are stated in the tool result itself. A test keeps the source free of ctx.info/ctx.warning and friends.

Note that the SDK's LATEST_PROTOCOL_VERSION is an alias for the modern era, not for the handshake era — pinning against it alone would leave the era that current clients actually negotiate free to drift.

Update policy. When the gate fails, do not edit the constant blindly: read the spec changelog between the two revisions, verify the server still behaves, then move the constant, this section, README.de.md and CHANGELOG.md together.

Testing

# Unit tests (no network)PYTHONPATH=src pytest tests/ -m "not live" -v
# Live tests (real APIs) — also run daily at 05:17 UTC via# .github/workflows/live-tests.yml, so a format change upstream# surfaces even though the unit tests stay green.PYTHONPATH=src pytest tests/ -m live -v
# Linting — install the local gates once with `pre-commit install`# to run these (and the CI guards) before every commit.ruff check src/ tests/ scripts/ruff format --check src/ tests/ scripts/

Development

git clone https://github.com/malkreide/meteoswiss-mcpcd meteoswiss-mcppip install -e ".[dev]"

MCP Inspector (local test)

PYTHONPATH=src npx @modelcontextprotocol/inspector python -m meteoswiss_mcp.server

Contributing

See the contributing guidelines (Deutsch).

Security

See the security policy (Deutsch) for the security posture and how to report a vulnerability.

License

MIT License – see LICENSE.

Source data: MeteoSwiss Open Government Data (CC BY 4.0). When using the data, cite: Source: MeteoSwiss.

Author

Hayal Oezkan · github.com/malkreide

Related servers

[swiss-environment-mcp] [zurich-opendata-mcp] [swiss-transport-mcp]

Installation

Run via uv's uvx — no clone or manual install needed. Add to your MCP client config (mcpServers for Claude Desktop, Cursor and Windsurf; use a top-level servers key for VS Code in .vscode/mcp.json):

{  "mcpServers": {    "meteoswiss-mcp": {      "command": "uvx",      "args": [        "meteoswiss-mcp"      ]    }  }}