
Wraps the Open-Meteo Flood API so you can query flood forecasting and historical flood data through MCP without dealing with authentication. Part of the Pipeworx gateway ecosystem, which means you can either use this standalone server or access it alongside 673+ other data sources through their unified gateway. The ask_pipeworx feature is interesting: instead of calling tools with specific parameters, you can ask questions in plain English and it routes to the right endpoint automatically. Free to use, no API keys required. Useful when you're building climate risk tools, emergency response systems, or anything that needs flood predictions based on river discharge forecasts.
Flood MCP — wraps Open-Meteo Flood API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_river_discharge | Get daily river discharge forecast in cubic meters per second for a location. Returns discharge values with timestamps. Use to monitor water flow rates for flood risk assessment. |
get_flood_forecast | Get multi-day flood forecast for a location with current, mean, and peak river discharge projections. Returns discharge statistics and severity assessment. Use to evaluate flood risk and timeline. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"flood": {
"url": "https://gateway.pipeworx.io/flood/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/flood/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, 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.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Flood data" })
The gateway picks the right tool and fills the arguments automatically.
MIT