mcpgawkdocs ← Site

client

claude-desktop-extension

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

Where its servers are configured

platformwhere mcpgawk looksshape it reads
macOSLibrary/Application Support/Claude/Claude Extensions/*/manifest.jsondxt_manifest
WindowsAppData/Roaming/Claude/Claude Extensions/*/manifest.jsondxt_manifest

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

Refusing 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 this client

mcpgawk scan

scan takes a config file only in the plain mcpServers JSON shape, which this client does not use. Run with no file, it reads this client's config from the paths above along with every other agent's on this machine, and lists each server with what each tool costs and what it can reach.

Every client

amp · antigravity · claude-code · claude-desktop · cline · codex · continue · cursor · gemini-cli · goose · junie · kimi · kiro · lmstudio · opencode · roo · vscode · warp · windsurf · zed