ukflood_areas
Pack: uk-flood-monitoring · Endpoint: https://gateway.pipeworx.io/uk-flood-monitoring/mcp
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/ukflood_areas for the schema, then POST the same URL with its arguments for the data.
The named flood areas the Environment Agency issues warnings for — the geography behind a warning code. Each area has an fwdCode (e.g. “053FWFPUWI06”), a plain description of the land it covers, its county, EA operational area, the river or sea concerned, a centroid and a quick-dial number. Filter by county or search the description text. Use this to turn a warning code from ukflood_warnings into a place, or to find the code for a place before a flood happens.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
county | string | no | County filter as the EA spells it, e.g. “Lincolnshire”. |
search | string | no | Case-insensitive substring matched against the area label, description and river name, e.g. “Thames”. |
latitude | number | no | Optional latitude for a radius search, e.g. 53.22. |
longitude | number | no | Optional longitude for a radius search, e.g. -0.55. |
radius_km | number | no | Radius in kilometres when latitude/longitude are given (default 15, max 100). |
limit | number | no | Max areas to return (default 25, max 200). |
Example call
Arguments
{
"county": "Lincolnshire"
}
curl
curl -X POST https://gateway.pipeworx.io/uk-flood-monitoring/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ukflood_areas","arguments":{"county":"Lincolnshire"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('ukflood_areas', {
"county": "Lincolnshire"
});
More examples
{
"search": "Thames",
"limit": 2
}
Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"uk-flood-monitoring": {
"url": "https://gateway.pipeworx.io/uk-flood-monitoring/mcp"
}
}
}
See Getting Started for client-specific install steps.