Uk Flood Monitoring MCP server

@pipeworx/uk-flood-monitoring

England's official flood warnings and river-gauge telemetry, from the Environment Agency's real-time flood-monitoring API.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

currently in force, with severity, named flood area, river or sea, and the EA message text. Answers "is there a flood warning near X".

• ukfloodwarnings(minseverity?, county?, limit?) — flood warnings and alerts

monitoring stations near a point and the measures each reports. This is where you get the station id for the next tool.

• ukfloodstationsnear(latitude, longitude, radius_km?, parameter?, river?, limit?) —

flow (m³/s) or rainfall (mm) from one station, latest per measure by default, or a time series with since.

• ukfloodstationreadings(station_id, since?, limit?) — water level (m), river

the named flood areas warnings are issued against, so a warning code resolves to a place.

• ukfloodareas(county?, search?, latitude?, longitude?, radiuskm?, limit?) —

Auth

Keyless. Open Government Licence v3.

Data sources

filterable by lat/long/dist (km), parameter, riverName.

• — warnings in force.
• — station registry,

telemetry; ?latest for the newest reading per measure, ?since= for a series.

• —

• — flood-area registry.
• Reference:

Things worth knowing:

Ireland publish separately. A Cardiff or Glasgow query legitimately returns nothing.

• England only. Wales (Natural Resources Wales), Scotland (SEPA) and Northern

returns items: [], and that matched the Environment Agency's own public page ("No flood alerts") when this pack was built. ukflood_warnings therefore returns severity counts and an explicit all-clear status alongside the empty list, so a caller can tell "nothing is happening" from "the call broke".

• Zero warnings is a normal state, not a failure. On a dry day /id/floods

path segment, which is the notation callers actually pass back in.

• The API returns JSON-LD. @id fields are URIs; the pack hands back the last

after over-fetching, so combine it with county on large counties.

• label is occasionally an array rather than a string.
• floodAreas has no text-search parameter; search is applied client-side

river discharge. This one is measured gauges and official warnings.

• Different source from the flood pack, which is Open-Meteo's global modelled

Verified

2026-09-17 — stations near London, readings from 5380TH (Walthamstow, Low Hall, River Lee) and Lincolnshire flood areas all returned rows; warnings returned a cross-checked genuine all-clear.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "uk-flood-monitoring": {
      "url": "https://gateway.pipeworx.io/uk-flood-monitoring/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/uk-flood-monitoring/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.