Open Meteo MCP Server

What open-meteo-mcp-server does

open-meteo-mcp-server exposes Open-Meteo data through twelve MCP tools. It can resolve place names into coordinates and geographic metadata, retrieve current conditions and forecasts, read historical reanalysis data from 1940 onward, and return marine, air-quality, elevation, flood, ensemble, and climate information.

The weather tools support hourly and daily variables. Forecast requests cover up to 16 days and can include up to 92 previous days. Historical requests accept a date range beginning on 1940-01-01. Marine requests cover current conditions, forecasts of up to eight days, or archive ranges. Air-quality requests cover up to seven forecast days or archive data from August 2022.

Additional tools provide per-member ensemble results, GloFAS river-discharge forecasts and historical ranges, bias-corrected daily CMIP6 projections from 1950 through 2050, and Copernicus DEM terrain elevation.

How it works

An MCP client sends tool calls containing coordinates or a location query, requested variables, dates, models, and unit preferences. openmeteo_search_locations returns ranked matches with coordinates, country, region, timezone, population, and feature information. The resulting coordinates can then be passed to the environmental data tools.

Forecast and historical responses include timestamped hourly or daily records and unit maps. Selecting multiple models adds model-specific column suffixes so results can be compared. Models without coverage may be removed from a multi-model response with a notice; if none cover the requested point, the call fails.

The DataCanvas tools operate on staged tables and views. openmeteo_dataframe_describe lists their tables and columns, openmeteo_dataframe_query runs read-only SQL SELECT statements, and openmeteo_dataframe_drop removes a selected table or view when explicitly requested.

Setup and configuration

The package can run over STDIO or Streamable HTTP. A public hosted MCP endpoint is available at https://open-meteo.casey... and the project provides installation links for Claude Desktop, Cursor, and VS Code. It can also be installed through the npm package using npx.

No API key is required. Requests can use metric or imperial marine units, selectable temperature and wind-speed units, and Open-Meteo model selections where supported. The server also publishes an open-meteo-guide skill describing which tool fits common questions, including exceedance probabilities, frost, climate shifts, surf locations, river cells, and AQI timing.

Tools and capabilities

• Search place names with country and language filters, returning up to ten ranked results.
• Retrieve current, hourly, and daily forecasts from the best match or selected models.
• Read reanalysis history, including multi-model comparisons and date ranges.
• Query marine waves, swell, sea-surface conditions, pollutants, pollen, and AQI.
• Fetch elevation for up to 1,000 coordinate pairs; up to 100 are sampled per call.
• Inspect ensemble members, river discharge, and CMIP6 climate projections.
• Describe staged DataCanvas data, run read-only SQL, or opt in to dropping a table or view.

Limitations and notes

Forecast windows, archive coverage, and model availability differ by tool. Marine requests can return nulls for inland points, while pollen data is modeled for Europe. Some regional models have limited geographic coverage, and ERA5-based data can lag by about a week. The elevation tool reports coordinates beyond its per-call sampling limit for later submission. For recent history, the forecast tool's past_days option may be preferable because the historical archive can lag.