Run ANUGA flood simulations, track progress, and retrieve results on Hydrata Cloud.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Remote HTTPChoose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Capabilities & Tool Schemas (17)
Inspect callable tools, capabilities, and parameters exposed to AI agents by Hydrata ANUGA Flood Simulation.
list_projectsList ANUGA simulation projects (paginated)
get_projectGet project details including scenarios
get_scenarioGet a scenario's `computed_status`, mesh-triangle estimate and latest run
start_simulationStart a flood simulation (local/EC2/Batch backends)
get_run_statusLightweight status poll (<50ms)
get_runFull run details with timing and results
Documentation Overview
hydrata-mcp-server
MCP server for Hydrata Cloud — build ANUGA flood models from terrain and input layers, run simulations, track progress, and retrieve results through the Model Context Protocol.
Connect and authenticate
Endpoint: https://hydrata.com/mcp/ — Transport: Streamable HTTP.
Every tool call needs the caller's own hydrata.com credential. The server holds no identity of its own: a tools/call must carry the caller's Authorization header (HTTP Basic for a hydrata.com account), which the server forwards verbatim to the Hydrata REST API — so results are scoped by the real user's project permissions and the audit trail names them. A tools/call without it is answered with 401 and WWW-Authenticate: Basic realm="hydrata.com" before any tool runs. initialize, tools/list and ping answer anonymously, so the tool catalog is browsable without an account and the MCP registry's liveness check stays true.
The server is not yet open to external accounts: there is no self-serve way to connect your own hydrata.com login to it today, and this README deliberately carries no client-side credential recipe. If you would like to use it, contact us at hydrata.com.
Tools
Version 0.2.0 exposes seventeen tools: nine that read projects and scenarios and drive a run, and eight that build a model from terrain and input layers the agent has already uploaded.
| Tool | Description |
|---|---|
list_projects | List ANUGA simulation projects (paginated) |
get_project | Get project details including scenarios |
get_scenario | Get a scenario's computed_status, mesh-triangle estimate 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) |
create_project | Create an ANUGA project with a name and EPSG projection |
presign_terrain_upload | Return a presigned URL + key so the agent PUTs the terrain GeoTIFF itself (no file bytes pass through MCP) |
finalize_terrain_upload | Register the uploaded terrain; the import chain seeds the project's six default boundary/friction/inflow/rainfall/structure/mesh-region rows |
get_terrain | Poll the terrain until it is ready (bounded; timed_out means call again) |
create_time_series | Create a time series (rain gauge, hydrograph or tide/stage — series_type and units are top-level fields) from {"rowData": [...]}; a rainfall polygon binds to its gauge by the series name |
attach_input_layer | Attach a GeoJSON dataset the agent already uploaded as the project's boundary/friction/inflow/rainfall/structure or mesh-region layer; breakline and culvert are refused (culvert flow is not conveyed) |
create_scenario | Create a draft scenario and return its mesh-triangle estimate (resolution is a length in metres) |
build_scenario | Build the scenario package; shows the estimate first and needs confirm=true above 100,000 triangles; polls computed_status to built; never re-posts a build that is in flight or already built (rebuild=true to force one); surfaces the server's 422 MESH_TOO_LARGE verbatim |
No tool accepts file contents inline. The agent moves the bytes itself — the terrain GeoTIFF to the presigned URL, a GeoJSON layer to the REST API upload endpoint — and hands the server the resulting key or upload id.
Typical workflow
Run a scenario that already exists:
Import a model and run it:
What is Hydrata?
Hydrata is a geospatial hydraulic modeling platform. It runs ANUGA flood simulations in the cloud — upload terrain data, configure scenarios, run simulations on managed compute (Celery, EC2, or AWS Batch), and visualise results on interactive maps.
ANUGA is an open-source hydrodynamic model developed by Geoscience Australia and the Australian National University. It solves the shallow water wave equations using finite volumes on an unstructured triangular mesh.
Development
Contributions welcome — see issues.
License
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
Last commit
4d ago
Most recent push to the default branch.
Tools exposed
17
Callable tools this server registers over MCP.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Hydrata ANUGA Flood Simulation
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/hydrata-anuga-flood-simulation)HTML Embed
<a href="https://allmcps.com/mcp/hydrata-anuga-flood-simulation"><img src="https://allmcps.com/api/badge/hydrata-anuga-flood-simulation?style=directory" alt="Hydrata ANUGA Flood Simulation on AllMCPs" /></a>