Clients
Discovery reads 21 client configurations. 6 of them expose a pre-execution hook point, so a call can be blocked before it runs; the other 15 have none, and their calls are checked by routing them through the gateway instead. Click a client for its config paths and the exact commands.
| Client | Call-time checking | Project config it reads |
|---|---|---|
| amp | via gateway | .amp/settings.json |
| antigravity | via gateway | user-level config |
| claude-code | blocks calls | .mcp.json |
| claude-desktop | via gateway | user-level config |
| claude-desktop-extension | via gateway | user-level config |
| cline | via gateway | user-level config |
| codex | blocks calls | user-level config |
| continue | via gateway | user-level config |
| cursor | blocks calls | .cursor/mcp.json |
| gemini-cli | blocks calls | user-level config |
| goose | via gateway | user-level config |
| junie | via gateway | .junie/mcp/mcp.json |
| kimi | blocks calls | user-level config |
| kiro | via gateway | user-level config |
| lmstudio | via gateway | user-level config |
| opencode | via gateway | opencode.json |
| roo | via gateway | .roo/mcp.json |
| vscode | via gateway | .vscode/mcp.json |
| warp | via gateway | .warp/.mcp.json |
| windsurf | blocks calls | user-level config |
| zed | via gateway | user-level config |
Not supported yet:
trae, jetbrains-ai-assistant — we could not
confirm where they store MCP servers, so mcpgawk does not look for them. If you use one, tell us
where its config lives.
When a config cannot be used
Discovery reports why, rather than skipping quietly.
| Reported | Means |
|---|---|
absent | No config at that path. Normal if you do not use that client. |
unreadable | The file exists but permissions stopped us reading it. |
unparsable | It exists and is readable, but is not valid JSON/TOML/YAML. |
too-large | Past the size ceiling, so it was not parsed. A guard against a pathological file. |
no-yaml-parser | A YAML config was found and no YAML parser is installed. |