{"slug": "show-hn-meteosource-mcp-server-weather-data-for-ai-assistants", "title": "Show HN: Meteosource MCP server, weather data for AI assistants", "summary": "Meteosource released a Model Context Protocol server that gives AI assistants access to weather data over Streamable HTTP at https://mcp.meteosource.com/mcp, authenticated with a Meteosource API key sent as a Bearer token or X-API-Key header, with no OAuth or sign-in. The server exposes seven tools: search_places, get_forecast, get_alerts, get_weather_history, get_air_quality, get_solar_production and get_wind_production, the last two requiring the Renewables plan while the other five work on the Free, Startup and Standard plans. Meteosource says the key is used only to call its API on the user's behalf, is never stored in full, and caches are kept per key, with setup guides for Claude Code, Claude Desktop, claude.ai, Codex and Antigravity in the project's GitHub README.", "body_md": "## Two values, and the agent is online\n\nThe 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.\n\n1. **Get a Meteosource API key** Sign up at[meteosource.com](https://www.meteosource.com/) ; the free plan is enough to try the forecast tools.\n2. **Add the server in your client** Address`https://mcp.meteosource.com/mcp` , transport Streamable HTTP.\n3. **Add the header**`Authorization: Bearer YOUR_METEOSOURCE_API_KEY` . Clients with a plain API-key field can send`X-API-Key` instead.\n4. **Ask about the weather** The agent picks the right tools itself, from place lookup to forecast.\n\n**No OAuth, no sign-in.**\n\nThe 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.\n\n            Step-by-step setup for Claude Code, Claude Desktop and claude.ai, Codex, Antigravity and other\n            clients, including team setups that keep the key out of version control, is in the\n            [Connect section of the README](https://github.com/Meteosource/meteosource-weather-mcp#connect).\n          \n\n[Setup guide](https://github.com/Meteosource/meteosource-weather-mcp#connect)\n\n## Seven tools, one weather API\n\n        The weather tools are for the Free, Startup and Standard plans; the production tools need the\n        Renewables plan. See [plans and pricing](https://www.meteosource.com/pricing).\n      \n\n### `search_places`\n\nPlace name, postal code or coordinates to a place ID for the other tools.\n\nWeather plans\n### `get_forecast`\n\nCurrent conditions, hourly and daily forecast, minute-by-minute precipitation, up to 20 locations per call.\n\nWeather plans\n### `get_alerts`\n\nOfficial severe-weather warnings for the USA, EU and Canada.\n\nWeather plans\n### `get_weather_history`\n\nPast weather, hourly, daily or monthly, with long-term normals and records.\n\nWeather plans\n### `get_air_quality`\n\nHourly air quality about four days ahead.\n\nWeather plans\n### `get_solar_production`\n\nOutput of a PV system, 20 years back to four days ahead.\n\nRenewables plan\n### `get_wind_production`\n\nOutput of a wind farm, 20 years back to four days ahead.\n\nRenewables plan\n\n### All tool details\n\nParameters, limits and the shape of what the agent receives, in the README.\n\nOpen on GitHub\n## Everything else is on GitHub\n\nThe README is the reference for the server. Jump straight to the part you need.\n\n- [Connect](https://github.com/Meteosource/meteosource-weather-mcp#connect) setup for each client, including team setups that keep the key out of version control\n- [Tools](https://github.com/Meteosource/meteosource-weather-mcp#tools) what each tool accepts and returns\n- [Try it](https://github.com/Meteosource/meteosource-weather-mcp#try-it) example questions to ask the agent\n- [Plans and limits](https://github.com/Meteosource/meteosource-weather-mcp#plans-and-limits) quotas, per-call limits and the cache\n- [Your key and your data](https://github.com/Meteosource/meteosource-weather-mcp#your-key-and-your-data) how the key is handled\n- [Troubleshooting](https://github.com/Meteosource/meteosource-weather-mcp#troubleshooting) what the agent reports and what to do\n\n        Questions about your key or plan go to Meteosource support. For the server itself,\n        [open an issue](https://github.com/Meteosource/meteosource-weather-mcp/issues) on GitHub.", "url": "https://wpnews.pro/news/show-hn-meteosource-mcp-server-weather-data-for-ai-assistants", "canonical_source": "https://mcp.meteosource.com/", "published_at": "2026-11-04 08:02:25+00:00", "updated_at": "2026-11-04 08:20:18.416319+00:00", "lang": "en", "topics": ["ai-agents", "agent-protocols", "ai-tools", "artificial-intelligence"], "entities": ["Meteosource", "Model Context Protocol", "Claude Code", "Claude Desktop", "claude.ai", "Codex", "Antigravity", "GitHub"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/show-hn-meteosource-mcp-server-weather-data-for-ai-assistants", "markdown": "https://wpnews.pro/news/show-hn-meteosource-mcp-server-weather-data-for-ai-assistants.md", "text": "https://wpnews.pro/news/show-hn-meteosource-mcp-server-weather-data-for-ai-assistants.txt", "jsonld": "https://wpnews.pro/news/show-hn-meteosource-mcp-server-weather-data-for-ai-assistants.jsonld"}}