Flood

What flood MCP server does

The flood MCP server connects AI agents to the Open-Meteo Flood API for river discharge and flood forecast data. It is intended for queries tied to a geographic location and supports two pack-specific tools: one for daily discharge forecasts and another for multi-day flood projections.

get_river_discharge returns forecast river discharge in cubic meters per second, along with timestamps. This is useful when an agent needs a time series of expected water flow. get_flood_forecast provides current, mean, and peak discharge projections for multiple days, together with discharge statistics and a severity assessment.

Its results can support flood-risk reviews, water-flow monitoring, and questions about the expected timing and intensity of conditions.

How it works

Two connection modes are available. The hosted option uses the Pipeworx gateway at https://gateway.pipeworx.io/flood/mcp. The gateway exposes the flood tools and also adds shared Pipeworx meta-tools. These include routing and discovery functions such as ask_pipeworx, which can reach tools across the wider Pipeworx catalog from the same connection.

The gateway's tools/list response therefore contains more tools than the two listed for this pack. Its initialize response identifies the scope currently provided. A full gateway connection at https://gateway.pipeworx.io/mcp lists all packs directly, while the pack endpoint lists Flood tools directly and can still use gateway routing.

For clients or scripts that do not use MCP, the gateway offers HTTP tool calls. For example, get_river_discharge can be called with latitude and longitude in a JSON request sent to the corresponding /v1/tools/ endpoint.

Setup and configuration

Add the hosted endpoint to an MCP client under the flood server name:

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

A local stdio installation is also available through the @pipeworx/mcp-flood package:

{
  "mcpServers": {
    "flood": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-flood"]
    }
  }
}

Running npx -y @pipeworx/mcp-flood starts the local server. This mode handles MCP initialize, tools/list, and tools/call requests and does not include the gateway's shared meta-tools. The package runs without a Pipeworx account or gateway round trip.

Tools and capabilities

• Retrieve daily river discharge forecasts in cubic meters per second.
• Return discharge values with timestamps for a location.
• Retrieve multi-day forecasts with current, mean, and peak discharge projections.
• Return discharge statistics and a severity assessment.
• Ask the gateway to select and populate a suitable tool through ask_pipeworx.

Limitations and notes

The local package exposes only the Flood pack's tools, while the hosted endpoint includes shared gateway tools as well. The gateway's listed tool count can change as its shared scope changes, so the connection's initialize response is authoritative.

Treat the returned assessment as API output rather than an independently defined risk model. The hosted gateway and local package use the same source and tools, but only the gateway provides Pipeworx-wide routing through its meta-tools.