Compare forecast rainfall and wind products to plan earthworks and temporary drainage inspections. Compare listed sources, access requirements and evidence for construction weather and rainfall mcp.
3 sources · For drainage engineers, flood consultants, hydrologists, construction and site managers, ecologists, geotechnical engineers, GIS analysts, planners. Enrichment describes potential applications; review source evidence and limitations.
Forecast uncertainty grows with lead time; project thresholds require a site-specific method statement.
Discover sources with MCP
Add this server to an HTTP-compatible MCP client, then call get_source to inspect the first source. The tool call is shown separately from the client configuration. Review upstream access details before requesting data.
A comprehensive MCP server providing access to Open-Meteo weather APIs for Large Language Models
What's in it
Data offered docs-verified
weather forecast up to 16 days · ERA5 historical weather from 1940 · air quality (PM2.5, PM10, ozone, NO2, pollen, European and US AQI, UV index) · marine waves, swell and sea surface temperature · ensemble forecasts · seasonal outlook from a few weeks to about 7 months · CMIP6 climate projections 1950 to 2050 · river discharge via GloFAS (flood_forecast) · geocoding · elevation
Coverage llm-inferred
Not stated for the server as a whole. GFS is global, DWD ICON focuses on Europe and MET Norway on Nordic countries. UK is not named. · 1940 to yesterday (ERA5 archive); CMIP6 projections 1950 to 2050
Resolution llm-inferred
Temporal: hourly, daily and 15-minute series. Spatial resolution not stated.
Formats llm-inferred
JSON · MCP stdio · MCP streamable HTTP
Access docs-verified
Free for non-commercial use; no API key needed for the Open-Meteo APIs. Server licence MIT. API_KEY applies only to the server's own HTTP transport.
Useful for
Use cases llm-inferred
ERA5 rainfall and temperature history (weather_archive) for FRA or drainage baseline climatology · Forecast rainfall and wind for construction-phase site planning · GloFAS river discharge screening (flood_forecast) at site coordinates before gauge data review · CMIP6 climate projections (climate_projection) for climate-change allowances in drainage strategy
Docs cover free use for non-commercial purposes only; commercial consultancy use must be checked against Open-Meteo terms · ENTRY auth lists API_KEY, but the docs say no key is needed for Open-Meteo; API_KEY only protects HTTP mode · Model-specific tools are regional (ICON for Germany/Europe, MET Norway for Nordic countries); UK coverage is not named · GloFAS flood discharge is modelled, not gauge observations · Responses over 25,000 characters are truncated; narrow the date range or variables to get full data · Response cache is in-memory only and not persistent · Archive ranges ending within the last 5 days are still being backfilled by Open-Meteo · Tool argument names in example_tool_calls are inferred from Open-Meteo API conventions, not from DOCS · Docs give no maintenance or release-status information
Weather forecast API combining multiple numerical models; separate historical APIs available.
What's in it
Data offered docs-verified
hourly temperature (2 m) · relative humidity (2 m) · dewpoint (2 m) · precipitation (rain + showers + snow) · rain · showers · snowfall · snow depth · soil temperature (0–54 cm) · soil moisture (0–81 cm) · reference evapotranspiration (ET₀) · wind speed and direction (10–180 m) · wind gusts (10 m) · cloud cover · visibility · CAPE and lifted index · solar radiation (GHI, DNI, DHI, GTI) · pressure-level variables · boundary layer height
Coverage llm-inferred
Global (ENTRY regions), with regional high-resolution models listed in DOCS (e.g. ECMWF, NCEP HRRR U.S. CONUS, DWD ICON EU, MET Norway Nordic, KNMI Harmonie AROME Europe, GEM HRDPS Canada) · Forecasts up to 16 days ahead; past data via the Past Days option (archived forecasts)
Resolution docs-verified
Model-dependent: from 9 km (ECMWF IFS HRES) to 0.25° (ECMWF IFS, NCEP GFS); temporal resolution for hourly data is documented separately
Formats llm-inferred
JSON
Access llm-inferred
No API key for free non-commercial use; commercial use requires a separate subscription. Data licence CC BY 4.0; service terms apply.
Useful for
Use cases llm-inferred
Short-term rainfall and snowfall forecast context for earthworks and construction weather-window planning · Soil moisture and reference evapotranspiration (ET₀) inputs for ecological or water-balance screening · Wind gust and precipitation checks for site risk assessments (crane lifts, temporary works, exposed drainage)
Audience llm-inferred
drainage engineers · hydrologists · flood consultants · geotechnical engineers · ecologists · construction and site managers
Limitations
Constraints llm-inferred
Forecast-oriented: DOCS describe forecasts up to 16 days; historical archive is not described on this page (ENTRY says separate historical APIs exist) · Past-data access is via archived forecasts through the Past Days feature, not observed records · Resolution and variable availability depend on the chosen weather model · No UK-specific model is named in DOCS · Commercial use needs a paid subscription · Service terms apply in addition to CC BY 4.0 data licence
Which listed sources support Construction weather and rainfall MCP?
Start with Open-Meteo MCP, Open-Meteo API, Met Office Weather DataHub. Compare forecast rainfall and wind products to plan earthworks and temporary drainage inspections.
What should I check before using these sources for construction weather and rainfall mcp?
Forecast uncertainty grows with lead time; project thresholds require a site-specific method statement.
How do I inspect Open-Meteo MCP through MCP?
Connect an MCP client to https://terramcp.earth/mcp and call get_source with slug open-meteo-mcp. Review its provenance, access requirements and limitations before contacting the upstream service. Discovery does not make every listed source directly executable through the router.
Are these sources free and independently verified?
Access and licence terms belong to each upstream provider; some products require registration or payment. Open each listing for evidence, health status and enrichment provenance. A wrapper and its underlying API can refer to the same dataset and are not independent observations.