Open Meteo Mcp Server
Wire global weather, marine, air-quality, and elevation data from Open-Meteo into agent-driven app features without bespoke API glue.
Overview
io.github.cyanheads/open-meteo-mcp-server is a MCP server for the Build phase that queries Open-Meteo for forecasts, archives, marine, air quality, geocoding, and elevation.
What is this MCP server?
- Forecast, ERA5 historical archive, marine, air quality, geocoding, and elevation via Open-Meteo
- STDIO (Bun) and streamable-http remote at open-meteo.caseyjhand.com/mcp
- Optional DuckDB DataCanvas: set CANVAS_PROVIDER_TYPE=duckdb for historical spillover plus dataframe_query / dataframe_de
- Default CANVAS_PROVIDER_TYPE none disables spillover for lighter local runs
- MCP_LOG_LEVEL tuning for integration debugging
- Server version 0.1.4
- Six capability areas documented: forecast, ERA5 archive, marine, air quality, geocoding, elevation
- Default CANVAS_PROVIDER_TYPE none; duckdb enables DataCanvas spillover tools
Community signal: 2 GitHub stars.
What problem does it solve?
Building weather-aware features means repeatedly translating Open-Meteo REST parameters by hand instead of letting your agent fetch consistent environmental data.
Who is it for?
Builders adding forecasts, AQI, or marine layers to apps and agents who want Open-Meteo without maintaining custom API wrappers.
Skip if: Enterprise contracts requiring proprietary commercial weather vendors only, or teams that refuse optional DuckDB setup for large historical slices.
What do I get? / Deliverables
Your agent gains MCP tools for multi-layer Open-Meteo data, with optional DuckDB spillover for historical analysis when enabled.
- MCP-accessible Open-Meteo forecast and specialty endpoint tools
- Optional historical spillover workflow with dataframe_query and dataframe_describe when DuckDB is enabled
- Remote or local transport ready for agent-driven weather features
Recommended MCP Servers
Journey fit
Weather and geospatial feeds are integrated during Build when you add forecasts and environmental layers to products. Open-Meteo is an external API surface; Integrations is the right shelf for MCP tools that wrap forecast, archive, and geocoding endpoints.
How it compares
Open-Meteo data MCP integration, not a generic LLM prompt pack or infrastructure deployer.
Common Questions / FAQ
Who is io.github.cyanheads/open-meteo-mcp-server for?
Solo developers and agent users who need global weather and environmental APIs inside Claude Code, Cursor, or similar MCP clients.
When should I use io.github.cyanheads/open-meteo-mcp-server?
During Build integrations when you implement forecasts, historical ERA5 pulls, marine or air-quality features, or geocoding tied to Open-Meteo.
How do I add io.github.cyanheads/open-meteo-mcp-server to my agent?
Add @cyanheads/open-meteo-mcp-server via npm with Bun stdio (run start:stdio) or configure the streamable-http remote; set MCP_LOG_LEVEL and CANVAS_PROVIDER_TYPE if you need DuckDB spillover.