Koskamo

Hydrata MCP MCP server

An official MCP server by Hydrata that allows AI assistants to interact with the Hydrata Cloud platform for ANUGA flood modeling. It enables users to list projects, create scenarios, upload terrain data, start simulation runs, and monitor their status directly through tool calls.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Hydrata
MCP endpoint (Streamable HTTP)
https://hydrata.com/mcp/
Vendor documentation

What you can do with it

  • List ANUGA simulation projects
  • Create and build flood scenarios
  • Start and monitor simulation runs
  • Upload terrain data via presigned URLs
Tools advertised by the last live check:
  • list_projects
  • get_project
  • get_scenario
  • start_simulation
  • get_run_status
  • get_run
  • cancel_run
  • retry_run
  • list_runs
  • create_project
  • presign_terrain_upload
  • finalize_terrain_upload
  • get_terrain
  • create_time_series
  • attach_input_layer
  • create_scenario
  • build_scenario

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http hydrata-mcp https://hydrata.com/mcp/

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add hydrata-mcp --url https://hydrata.com/mcp/

Cursor

Merge this server into .cursor/mcp.json in your project, then enable hydrata-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "hydrata-mcp": {
      "url": "https://hydrata.com/mcp/"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "hydrata-mcp": {
      "type": "streamableHttp",
      "url": "https://hydrata.com/mcp/",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start hydrata-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "hydrata-mcp": {
      "type": "http",
      "url": "https://hydrata.com/mcp/"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http hydrata-mcp https://hydrata.com/mcp/

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "hydrata-mcp": {
      "url": "https://hydrata.com/mcp/"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "hydrata-mcp": {
      "serverUrl": "https://hydrata.com/mcp/"
    }
  }
}

Do you run Hydrata MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing