Flood vs Jma
A side-by-side look at the Flood and Jma MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Flood for environment & nature work as a local process; choose Jma for environment & nature as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Flood when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_river_discharge, get_flood_forecast.
Choose Jma when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Environment & Nature |
| Quality signal | 52/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Flood | View Jma |
Tools & capabilities
Flood tools 2
get_river_dischargeGet 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_forecastGet 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.
Jma tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Flood
{
"mcpServers": {
"flood": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-flood"
]
}
}
}
Jma
{
"mcpServers": {
"jma": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-jma"
]
}
}
}
Frequently asked questions
Flood is categorized under Environment & Nature and uses a local stdio subprocess. Jma belongs to Environment & Nature and uses a local stdio subprocess. Pick Flood for environment & nature work and Jma for environment & nature.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Flood has no declared pricing — check the project's own site. Jma has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add flood and jma as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Flood has a quality signal of 52/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Jma has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.