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