Weather MCP Server by Meteosource

npx add-mcp 'https://mcp.meteosource.com/mcp'

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.

1. Get a Meteosource API key Sign up at meteosource.com; the free plan is enough to try the forecast tools.
2. Add the server in your client Address https://mcp.meteosource.com/mcp, transport Streamable HTTP.
3. Add the header Authorization: Bearer YOUR_METEOSOURCE_API_KEY. Clients with a plain API-key field can send X-API-Key instead.
4. Ask about the weather The agent picks the right tools itself, from place lookup to forecast.

No OAuth, no sign-in.

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.

Seven 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 plans

get_forecast

Current conditions, hourly and daily forecast, minute-by-minute precipitation, up to 20 locations per call.

Weather plans

get_alerts

Official severe-weather warnings for the USA, EU and Canada.

Weather plans

get_weather_history

Past weather, hourly, daily or monthly, with long-term normals and records.

Weather plans

get_air_quality

Hourly air quality about four days ahead.

Weather plans

get_solar_production

Output of a PV system, 20 years back to four days ahead.

Renewables plan

get_wind_production

Output of a wind farm, 20 years back to four days ahead.

Renewables plan

All tool details

Parameters, limits and the shape of what the agent receives, in the README.

Open on GitHub

Everything else is on GitHub

The README is the reference for the server. Jump straight to the part you need.

• Connect setup for each client, including team setups that keep the key out of version control
• Tools what each tool accepts and returns
• Try it example questions to ask the agent
• Plans and limits quotas, per-call limits and the cache
• Your key and your data how the key is handled
• Troubleshooting what 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.