get_coverage_stats — Warmth Engine Observatory MCP Tool Read-only
get_coverage_stats
(get coverage stats) is one of 18 tools on the
Warmth Engine Observatory
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_coverage_stats from your client
- Claude Code Warmth Engine Observatory get_coverage_stats run in your project directory
- Claude Desktop Warmth Engine Observatory get_coverage_stats ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Warmth Engine Observatory get_coverage_stats ~/.cursor/mcp.json
- VS Code Warmth Engine Observatory get_coverage_stats .vscode/mcp.json
- Zed Warmth Engine Observatory get_coverage_stats ~/.config/zed/settings.json
- Windsurf Warmth Engine Observatory get_coverage_stats ~/.codeium/windsurf/mcp_config.json
- Cline Warmth Engine Observatory get_coverage_stats ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Warmth Engine Observatory get_coverage_stats ~/.gemini/settings.json
- Grok Warmth Engine Observatory get_coverage_stats .mcp.json (in your project root)
- ChatGPT Warmth Engine Observatory get_coverage_stats Settings → Connectors → Advanced → Developer mode
- Claude.ai Warmth Engine Observatory get_coverage_stats Settings → Connectors → Add custom connector
- LangChain Warmth Engine Observatory get_coverage_stats pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http observatory https://warmthengine.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.