com.hydrata/hydrata-mcp-server

Official9 tools

by Hydrata · Python

Hydrata - ANUGA Flood Simulation

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

Run and track ANUGA flood simulations on Hydrata Cloud infrastructure.

Captured live from the server via tools/list.

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.

Parameters (2)

pageinteger
Page number (default 1)
page_sizeinteger
Results per page, max 100 (default 100)

get_project

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

Parameters (1)

project_idintegerrequired
The project ID

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.

Parameters (2)

project_idintegerrequired
The project ID
scenario_idintegerrequired
The scenario ID

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.

Parameters (2)

scenario_idintegerrequired
The scenario ID to run
compute_backendstring
Compute backend: 'local' (Celery), 'ec2' (dedicated instance), or 'batch' (AWS Batch spot, cheapest). Default: 'local'

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.

Parameters (1)

run_idintegerrequired
The run ID

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.

Parameters (1)

run_idintegerrequired
The run ID

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).

Parameters (1)

run_idintegerrequired
The run ID to cancel

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.

Parameters (1)

run_idintegerrequired
The run ID to retry

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.

Parameters (4)

project_idintegerrequired
The project ID
status_filterany
Filter by status: created, building, built, queued, computing, processing, complete, error, cancelled. Omit for all.
pageinteger
Page number (default 1)
page_sizeinteger
Results per page, max 100 (default 100)

README.md2 KBView on GitHub

hydrata-mcp-server

MCP server for Hydrata Cloud — run ANUGA flood simulations, track progress, and retrieve results through the Model Context Protocol.

Connect

Add to your .mcp.json (Claude Code, Cursor, Windsurf, etc.):

json

{
  "mcpServers": {
    "hydrata": {
      "type": "streamable-http",
      "url": "https://hydrata.com/mcp/"
    }
  }
}

A Hydrata Cloud account is required. Contact us at hydrata.com to get started.

Tools

Tool	Description
`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)

Typical workflow

code

list_projects → get_scenario → start_simulation → poll get_run_status → get_run

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

bash

git clone https://github.com/Hydrata/hydrata-mcp-server.git
cd hydrata-mcp-server
pip install -e ".[dev]"
pytest -v

Contributions welcome — see issues.

License

MIT

Install

claude_desktop_config.json

{
  "mcpServers": {
    "hydrata-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://hydrata.com/mcp/"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.