openmeteo_get_historical
Historical weather from the ERA5 reanalysis archive (1940–present); large ranges spill to DataCanvas
How to use it
openmeteo_get_historical is exposed by the Open Meteo MCP Server MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the openmeteo_get_historical tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
Install Open Meteo MCP Server
docker run --rm -p 3010:3010 open-meteo-mcp-serverOther tools in Open Meteo MCP Server (11)
List tables and columns on a DataCanvas staged by openmeteogetforecast, openmeteogethistorical, openmeteogetmarine, openmeteogetairquality, openmeteogetensemble, openmeteogetflood, or openmeteogetclimate
Run a read-only SQL SELECT against tables staged on a DataCanvas
Modeled CAMS air quality: PM2.5, PM10, NO2, O3, CO, dust, pollen, and European/US AQI indices; up to 7 forecast days, pastdays, or a startdate/enddate archive range; large windows spill to DataCanvas
Bias-corrected daily CMIP6 climate projections (1950–2050) across up to 7 models; large ranges spill to DataCanvas
Terrain elevation from Copernicus DEM (~90m resolution) for up to 100 coordinate pairs per call
Probabilistic ensemble forecast: per-member hourly/daily time series (up to 51 members, 16 days) for exceedance and uncertainty analysis
GloFAS river discharge forecast (up to 210 days) or reanalysis (1984–present); coordinate-based, snaps to nearest river; large ranges spill to DataCanvas
Weather forecast for coordinates: hourly and/or daily variables for up to 16 days, with optional recent past data; wide windows spill to DataCanvas
Marine wave and ocean conditions for coastal or ocean coordinates: wave height, period, direction, swell, and sea-surface temperature; up to 8 forecast days, pastdays, or a startdate/enddate archive range; large windows spill to DataCanvas
Resolve a place name to ranked coordinate matches with country, region, elevation, timezone, and population
(0–92) covers recent history via the forecast model — use instead of openmeteogethistorical for dates within the last ~5 days to avoid ERA5 lag