habitat_received_level — Clairwave MCP Tool
habitat_received_level
(habitat received level) 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 habitat_received_level from your client
- Claude Code Clairwave habitat_received_level run in your project directory
- Claude Desktop Clairwave habitat_received_level ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Clairwave habitat_received_level ~/.cursor/mcp.json
- VS Code Clairwave habitat_received_level .vscode/mcp.json
- Zed Clairwave habitat_received_level ~/.config/zed/settings.json
- Windsurf Clairwave habitat_received_level ~/.codeium/windsurf/mcp_config.json
- Cline Clairwave habitat_received_level ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Clairwave habitat_received_level ~/.gemini/settings.json
- Grok Clairwave habitat_received_level .mcp.json (in your project root)
- ChatGPT Clairwave habitat_received_level Settings → Connectors → Advanced → Developer mode
- Claude.ai Clairwave habitat_received_level Settings → Connectors → Add custom connector
- LangChain Clairwave habitat_received_level 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.