Show HN: Meteosource MCP server, weather data for AI assistants

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.

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.

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.

get_forecast

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

get_alerts

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

get_weather_history

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

get_air_quality

Hourly air quality about four days ahead.

get_solar_production

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

get_wind_production

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

All tool details

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

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

Questions about your key or plan go to Meteosource support. For the server itself, open an issue on GitHub.