Swiss weather data for AI agents — MeteoSwiss open data exposed two ways: MCP server and agent skill
Meteoswiss MCP server exists for a simple reason — assistants are far more useful when they can act on Meteoswiss directly instead of describing what you should do. Swiss weather data for AI agents — MeteoSwiss open data exposed two ways: MCP server and agent skill.
Swiss weather data for AI assistants — powered by MeteoSwiss Open Government Data (OGD), the same data behind the MeteoSwiss app and website. Free, no API key required.
Once Meteoswiss is connected, these are the calls the assistant has available:
Multi — day forecasts** for ~6000 Swiss locations (postal codes, stations, place names)Real — time measurements** from ~300 stations (~160 full weather + ~140 precipitation-only), updated every 10 minutesmeteoswissLocalForecast — Multi-day forecasts by postal code, station, or place namemeteoswissCurrentWeather — Real-time measurements (temperature, wind, humidity, pressure)meteoswissStations — Search station network by name, canton, or coordinatesmeteoswissPollenData — Pollen concentration data from monitoring stationsmeteoswissClimateData — NBCN climate series — temperature, precipitation, sunshine, and climate indicators going back decadessearch — Search MeteoSwiss website content (DE, FR, IT, EN)fetch — Fetch full content from MeteoSwiss pagesBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Meteoswiss's toolset — Multi, Real, meteoswissLocalForecast and 6 more — is a fair guide to whether it matches your workflow. It is maintained by eins78; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Multi | day forecasts** for ~6000 Swiss locations (postal codes, stations, place names) |
| Real | time measurements** from ~300 stations (~160 full weather + ~140 precipitation-only), updated every 10 minutes |
| meteoswissLocalForecast | Multi-day forecasts by postal code, station, or place name |
| meteoswissCurrentWeather | Real-time measurements (temperature, wind, humidity, pressure) |
| meteoswissStations | Search station network by name, canton, or coordinates |
| meteoswissPollenData | Pollen concentration data from monitoring stations |
| meteoswissClimateData | NBCN climate series — temperature, precipitation, sunshine, and climate indicators going back decades |
| search | Search MeteoSwiss website content (DE, FR, IT, EN) |
| fetch | Fetch full content from MeteoSwiss pages |
{
"mcpServers": {
"server-meteoswiss": {
"command": "npx",
"args": ["-y", "skills"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.