Clairwave MCP MCP server

An official MCP server for predictive underwater acoustics that allows AI assistants to run physics-based sonar performance models, transmission loss calculations, and source-level estimations. It integrates live AIS vessel tracking, real bathymetry, and forecast sound-speed fields to simulate acoustic environments up to 10 days ahead.

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 Clairwave

MCP endpoint (Streamable HTTP)

https://www.clairwave.com/mcp

Vendor documentation

What you can do with it

Retrieve sound speed profiles and seabed parameters for specific locations
Estimate vessel noise levels using live AIS data and source models
Run 3D transmission loss volumes for acoustic propagation scenarios
Calculate sonobuoy detection footprints over real bathymetry

Tools advertised by the last live check:

resolve_place
get_bathymetry
get_sound_speed_profile
run_transmission_loss
estimate_detection_range
run_bellhop_volume
search_vessels
vessels_near
get_vessel
vessel_source_level
get_vessel_photo
habitat_received_level
about

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 clairwave-mcp https://www.clairwave.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 clairwave-mcp --url https://www.clairwave.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable clairwave-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "clairwave-mcp": {
      "url": "https://www.clairwave.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": {
    "clairwave-mcp": {
      "type": "streamableHttp",
      "url": "https://www.clairwave.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start clairwave-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "clairwave-mcp": {
      "type": "http",
      "url": "https://www.clairwave.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 clairwave-mcp https://www.clairwave.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": {
    "clairwave-mcp": {
      "url": "https://www.clairwave.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": {
    "clairwave-mcp": {
      "serverUrl": "https://www.clairwave.com/mcp"
    }
  }
}

See all 782

Do you run Clairwave 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