mcp · England

EA Flood MCP

A Model Context Protocol (MCP) server that provides access to the UK Environment Agency's Real Time Flood Monitoring API. This server allows you to access near real-time flood warnings, water level measurements, flow data, and monitoring station information.

Visit source ↗GitHub repository ↗

Claim this listing

Represent EA Flood MCP? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Explore paid sponsorship →

What's in it

Data offered docs-verified: flood warnings and alerts with severity levels · flood areas · water level readings · flow readings · temperature readings · wind readings · monitoring station information · historical readings
Coverage docs-verified: UK per docs (ENTRY regions says England only; verify)
Update frequency docs-verified: every 15 minutes
Formats docs-verified: MCP stdio
Access docs-verified: Free/open: no API key or registration. Server code MIT; data under the Open Government Licence v3

Useful for

Use cases llm-inferred: Nearest-gauge river level and flow context for FRA baseline · Check live flood warnings and alerts for a site's catchment · Pull recent level and flow readings for hydrological baseline review · Locate monitoring stations within a set radius of a project site
Audience llm-inferred: flood consultants · hydrologists · drainage engineers

Limitations

Constraints docs-verified: No service level guarantee; not suitable for safety-critical applications · Upstream Environment Agency API is Beta · Responses may be cached for short periods · List tools capped at 500 items (default 50; readings default 100), 60 KB truncation; use limit/offset to paginate · Coverage conflict: docs say UK, ENTRY metadata says England

Licence: MIT
Authentication: No API key required (repository README; check upstream requirements)
GitHub stars: 0
Last commit: 09/07/2026
Last successful page check: 14/10/2026
Page health: healthy
Package: Not recorded
Verification: Not independently verified

Auto-extracted, unverified fields: tools, install. Check upstream documentation.

Provenance & evidence

GitHub metadata observed via gh api. Authentication unknown unless README explicitly states it; review upstream access.

Metadata observed 14/10/2026 · editorial seed