Skip to content
All engineering use cases

Rainfall data MCP

Separate observed gauge rainfall from gridded reanalysis and satellite estimates for an event review. Compare listed sources, access requirements and evidence for rainfall data mcp.

4 sources · For drainage engineers, flood consultants, GIS analysts, hydrologists, planners. Enrichment describes potential applications; review source evidence and limitations.

Accumulation periods and time zones must agree before rainfall series are compared.

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.

{
  "mcpServers": {
    "terramcp": {
      "url": "https://terramcp.earth/mcp"
    }
  }
}

// After connecting, call this discovery tool:
{
  "name": "get_source",
  "arguments": {
    "slug": "open-meteo-mcp"
  }
}

Listed sources

mcp
74/100Currency A

Open-Meteo MCP ↗

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
Audience llm-inferred
flood consultants · drainage engineers · hydrologists · planners · GIS analysts

Limitations

Constraints llm-inferred
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
climategishydrology

Globalhealthy

Frequently asked questions

Which listed sources support Rainfall data MCP?

Start with Open-Meteo MCP, EA Rainfall API (flood-monitoring), Met Office MIDAS Open (CEDA). Separate observed gauge rainfall from gridded reanalysis and satellite estimates for an event review.

What should I check before using these sources for rainfall data mcp?

Accumulation periods and time zones must agree before rainfall series are compared.

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.