client
kimi
Config paths on every platform, whether calls can be blocked in place, and the commands to run.
Where its servers are configured
| platform | where mcpgawk looks | shape it reads |
|---|---|---|
| macOS | .kimi/mcp.json | mcpServers |
| Linux | .kimi/mcp.json | mcpServers |
| Windows | .kimi/mcp.json | mcpServers |
Paths are relative to your home directory. mcpgawk only reads them.
Blocking calls
Yes. One hook, installed once, checks every MCP tool call this client makes against the surface you approved — locally, in about 10ms, before the call runs. Free tier; nothing to sign in to.
mcpgawk guard install mcpgawk guard status
Scan just this client
mcpgawk scan ~/.kimi/mcp.json
Lists every server in that file with what each tool costs and what it can reach. To scan every
client at once instead, run mcpgawk with no arguments.
Every client
amp · antigravity · claude-code · claude-desktop · claude-desktop-extension · cline · codex · continue · cursor · gemini-cli · goose · junie · kiro · lmstudio · opencode · roo · vscode · warp · windsurf · zed