mcpgawkdocs ← Site

client

roo

Config paths on every platform, whether calls can be blocked in place, and the commands to run.

Where its servers are configured

platformwhere mcpgawk looksshape it reads
macOSLibrary/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/mcp_settings.jsonmcpServers
Linux.config/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/mcp_settings.jsonmcpServers
WindowsAppData/Roaming/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/mcp_settings.jsonmcpServers

Paths are relative to your home directory. mcpgawk only reads them.

Blocking calls

Not in place. This client exposes no hook point, so nothing can sit between it and its servers on this machine. Its servers are still discovered, scanned and verified.

To check its calls, point it at the gateway instead — same approved baseline, checked at the endpoint: set up the gateway (paid). 15 of the 21 supported clients work this way.

Scan just this client

mcpgawk scan ~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/mcp_settings.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 · kimi · kiro · lmstudio · opencode · vscode · warp · windsurf · zed