Run ANUGA flood simulations, track progress, and retrieve results on Hydrata Cloud.
Hydrata MCP server exists for a simple reason — assistants are far more useful when they can act on Hydrata directly instead of describing what you should do. Run ANUGA flood simulations, track progress, and retrieve results on Hydrata Cloud.
Add to your .mcp.json (Claude Code, Cursor, Windsurf, etc.):
Once Hydrata is connected, these are the calls the assistant has available:
list_projects — List ANUGA simulation projects (paginated)get_project — Get project details including scenariosget_scenario — Get scenario status and latest runstart_simulation — Start a flood simulation (local/EC2/Batch backends)get_run_status — Lightweight status poll (<50ms)get_run — Full run details with timing and resultscancel_run — Cancel an in-flight simulationretry_run — Retry a failed simulationlist_runs — List runs across a project (with status filter)Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Hydrata's toolset — list_projects, get_project, get_scenario and 6 more — is a fair guide to whether it matches your workflow. It is maintained by com.hydrata; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| list_projects | List ANUGA simulation projects (paginated) |
| get_project | Get project details including scenarios |
| get_scenario | Get scenario status and latest run |
| start_simulation | Start a flood simulation (local/EC2/Batch backends) |
| get_run_status | Lightweight status poll (<50ms) |
| get_run | Full run details with timing and results |
| cancel_run | Cancel an in-flight simulation |
| retry_run | Retry a failed simulation |
| list_runs | List runs across a project (with status filter) |
{
"mcpServers": {
"hydrata": {
"type": "streamable-http",
"url": "https://hydrata.com/mcp/"
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.