get_sound_speed_profile — Clairwave MCP Tool Read-only
get_sound_speed_profile
(get sound speed profile) is one of 13 tools on the
Clairwave
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_sound_speed_profile from your client
- Claude Code Clairwave get_sound_speed_profile run in your project directory
- Claude Desktop Clairwave get_sound_speed_profile ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Clairwave get_sound_speed_profile ~/.cursor/mcp.json
- VS Code Clairwave get_sound_speed_profile .vscode/mcp.json
- Zed Clairwave get_sound_speed_profile ~/.config/zed/settings.json
- Windsurf Clairwave get_sound_speed_profile ~/.codeium/windsurf/mcp_config.json
- Cline Clairwave get_sound_speed_profile ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Clairwave get_sound_speed_profile ~/.gemini/settings.json
- Grok Clairwave get_sound_speed_profile .mcp.json (in your project root)
- ChatGPT Clairwave get_sound_speed_profile Settings → Connectors → Advanced → Developer mode
- Claude.ai Clairwave get_sound_speed_profile Settings → Connectors → Add custom connector
- LangChain Clairwave get_sound_speed_profile pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http clairwave https://www.clairwave.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.