Flood vs Atlassian MCP Server
A side-by-side look at the Flood and Atlassian MCP Server 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 Atlassian MCP Server for version control over a hosted endpoint. 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 Atlassian MCP Server when
- You need dedicated capabilities in the Version Control domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Version Control |
| Quality signal | 56/100 · Good | 80/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 1,118 |
| Directory activity | 2 views 0 installs 0 upvotes | 9 views 0 installs 1 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Flood | View Atlassian MCP Server |
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.
Atlassian MCP Server 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"
]
}
}
}
Atlassian MCP Server
{
"mcpServers": {
"atlassian-mcp-server": {
"url": "https://mcp.atlassian.com/v2/mcp"
}
}
}
Frequently asked questions
Flood is categorized under Environment & Nature and uses a local stdio subprocess. Atlassian MCP Server belongs to Version Control and uses a remote HTTP/SSE transport. Pick Flood for environment & nature work and Atlassian MCP Server 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. Atlassian MCP Server is listed as free. Auth: other. 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 atlassian-mcp-server 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. Atlassian MCP Server has 80/100 (Excellent) with 9 views, 0 installs and 1,118 GitHub stars.