Two values, and the agent is online
The server speaks the Model Context Protocol over Streamable HTTP. Every client needs the same two things: the address and your Meteosource API key in a header. The plan the key is on decides which tools the agent sees.
- Get a Meteosource API keySign up at meteosource.com; the free plan is enough to try the forecast tools.
- Add the server in your clientAddress
https://mcp.meteosource.com/mcp, transport Streamable HTTP. - Add the header
Authorization: Bearer YOUR_METEOSOURCE_API_KEY. Clients with a plain API-key field can sendX-API-Keyinstead. - Ask about the weatherThe agent picks the right tools itself, from place lookup to forecast.
The key travels in a request header, is used only to call Meteosource on your behalf and is never stored in full. Caches are kept per key.
Step-by-step setup for Claude Code, Claude Desktop and claude.ai, Codex, Antigravity and other clients, including team setups that keep the key out of version control, is in the Connect section of the README.
Setup guideSeven tools, one weather API
The weather tools are for the Free, Startup and Standard plans; the production tools need the Renewables plan. See plans and pricing.
search_places
Place name, postal code or coordinates to a place ID for the other tools.
Weather plansget_forecast
Current conditions, hourly and daily forecast, minute-by-minute precipitation, up to 20 locations per call.
Weather plansget_alerts
Official severe-weather warnings for the USA, EU and Canada.
Weather plansget_weather_history
Past weather, hourly, daily or monthly, with long-term normals and records.
Weather plansget_air_quality
Hourly air quality about four days ahead.
Weather plansget_solar_production
Output of a PV system, 20 years back to four days ahead.
Renewables planget_wind_production
Output of a wind farm, 20 years back to four days ahead.
Renewables planAll tool details
Parameters, limits and the shape of what the agent receives, in the README.
Open on GitHubEverything else is on GitHub
The README is the reference for the server. Jump straight to the part you need.
- Connectsetup for each client, including team setups that keep the key out of version control
- Toolswhat each tool accepts and returns
- Try itexample questions to ask the agent
- Plans and limitsquotas, per-call limits and the cache
- Your key and your datahow the key is handled
- Troubleshootingwhat the agent reports and what to do
Questions about your key or plan go to Meteosource support. For the server itself, open an issue on GitHub.