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