Flood vs Git
A side-by-side look at the Flood and Git 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 Git for version control 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 Git when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Version Control |
| Quality signal | 56/100 · Good | 81/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,512 |
| Directory activity | 2 views 0 installs 0 upvotes | 49 views 0 installs 0 upvotes |
| Tools | 2 | 16 |
| Full listing | View Flood | View Git |
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.
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on 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"
]
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Frequently asked questions
Flood is categorized under Environment & Nature and uses a local stdio subprocess. Git belongs to Version Control and uses a local stdio subprocess. Pick Flood for environment & nature work and Git for version control.
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. Git is listed as free. Auth: no auth required. 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 git 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 56/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Git has 81/100 (Excellent) with 49 views, 0 installs and 91,512 GitHub stars.