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