Hydrata - ANUGA Flood Simulation MCP Server

com.hydrata/hydrata-mcp-server

answering

Hydrata - ANUGA Flood Simulation is answering right now. Last checked 7 min ago. It exposes 9 tools. Last commit 1 Mar 2026.

Run ANUGA flood simulations, track progress, and retrieve results on Hydrata Cloud.

Uptime history 44 hours of history

44 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

584 ms

Response time

average over 24h

Stars

last commit 1 Mar 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add hydrata-mcp-server --transport http https://hydrata.com/mcp/

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "hydrata-mcp-server": {
      "url": "https://hydrata.com/mcp/"
    }
  }
}

~/.codex/config.toml

[mcp_servers.hydrata-mcp-server]
url = "https://hydrata.com/mcp/"

.cursor/mcp.json

{
  "mcpServers": {
    "hydrata-mcp-server": {
      "url": "https://hydrata.com/mcp/"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "hydrata-mcp-server": {
      "url": "https://hydrata.com/mcp/"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

cancel

cancel_run

Cancel an in-flight simulation run. Works on runs in built, queued, or computing status. Cleans up compute resources (terminates EC2 instance, Celery task, or Batch job). Returns 409 if the run is already in a terminal state (complete, cancelled, or error).

get

get_run

Get full details of a simulation run including timing and results. Returns the complete run record: status, progress, timing (start/end timestamps, duration), compute details (backend, instance type, cost), mesh info, error messages, and result log. Use get_run_status for lightweight polling; use this for final results.

project

get_project

Get details of a specific ANUGA project including its scenarios. Returns the project name, projection (EPSG code), base map ID, and configuration.

projects

list_projects

List ANUGA simulation projects accessible to the authenticated user. Returns a paginated list of projects with their names, projections, and base map references.

retry

retry_run

Retry a failed simulation run. Resets an errored run back to 'created' status and triggers a new package build. The same run ID is reused. Only valid when status is 'error'. Returns 409 for any other state.

runs

list_runs

List all simulation runs across all scenarios in a project. Returns a paginated list of runs. Optionally filter by status to find active, completed, or failed runs.

scenario

get_scenario

Get scenario details including its current status and latest run. The status field is computed from the latest run and will be one of: created, building, built, queued, computing, processing, complete, error, or cancelled. A scenario must be in 'built' status before it can be run.

start

start_simulation

Start a flood simulation run for a built scenario. The scenario must be in 'built' status. Returns 202 with the new run. The run transitions through: built → queued → computing → processing → complete. After starting, poll get_run_status to track progress. Returns 409 if the scenario is not in the correct state.

status

get_run_status

Lightweight status check for a simulation run (fast, <50ms). Use this for polling instead of get_run. Returns only: id, status, progress_pct (0-100), eta_seconds, error_message, and compute_backend. Poll every 5-10 seconds. Terminal states: complete, error, cancelled.

Endpoints

URL	Transport	State	Latency	Checked
https://hydrata.com/mcp/	streamable-http	answering	579 ms	7 min ago

Hydrata - ANUGA Flood Simulation — questions

Answers built from our own checks of this server.

What can Hydrata - ANUGA Flood Simulation do?

It exposes 9 tools, read directly from the server on our last check. Among them: cancel_run, get_project, get_run, get_run_status, get_scenario, list_projects and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Hydrata - ANUGA Flood Simulation working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 584 ms. The bar chart above shows every period we have measured.

How do I connect Hydrata - ANUGA Flood Simulation?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Hydrata - ANUGA Flood Simulation need an API key?

No. Hydrata - ANUGA Flood Simulation completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Hydrata - ANUGA Flood Simulation?

It answers our handshake in 584 ms on average, which is faster than 17% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Hydrata - ANUGA Flood Simulation open source?

Yes — it is published under the MIT licence, written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.