mcpgawk — see every MCP server your agents can reach, and what changed since you approved it

gawk-dev

12 installs

The panel into mcpgawk. See every MCP server configured across your AI tools, grouped by the tool it lives in, what each one can reach, and which need attention. The CLI it drives catches a server that changed after you approved it, shows exactly what changed, and can put one gateway in front of you

Installation

Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.

Copied to clipboard

More Info

mcpgawk — see every MCP server your agents can reach

Your agents call MCP servers you have never inspected. This extension is the panel for mcpgawk: it shows every server configured across your AI tools, grouped by the tool it lives in, what each one can reach, and which ones need attention. The rest of mcpgawk lives in the CLI it drives — it blocks a tool that changed after you approved a server, shows you exactly what changed (mcpgawk changes), verifies what a server actually does in a sandbox (no Docker needed), and can put one gateway in front of your whole fleet.

Local-first. The extension runs the mcpgawk CLI on your machine and renders what it returns. Nothing about your servers, tools or credentials is uploaded anywhere.

Watch: mcpgawk in 64 seconds. A tool you approved changes in an update; mcpgawk refuses the call until you decide.

mcpgawk scanning an MCP server: it flags a poisoned tool description and a write-capable tool that appeared after approval — locally, nothing uploaded

The engine in action: a server is measured, approved, then rug-pulls — mcpgawk catches the drift and the guard blocks the tool that appeared afterwards. All local, nothing uploaded.

The mcpgawk view in the sidebar: MCP servers grouped by the AI tool they are configured in, each with its state and what it costs

Every server your agents can reach, grouped by the tool it lives in. Servers shown are the ones mcpgawk demo creates — your own fleet never leaves your machine.

Requirements

The engine is a separate CLI:

uv tool install --force mcpgawk      # or: pipx install mcpgawk

If it lives somewhere unusual (a virtualenv, a pyenv shim), set mcpgawk.path in settings.

What you get

A panel grouped by tool — Claude Code, Cursor, Codex, Claude Desktop (including extensions), Kiro, Gemini CLI. A server configured in two tools is scanned once and listed under both, because removing it from one leaves it running in the other.
Honest states — REVIEW / INCOMPLETE / CLEAN for servers we measured; AUTH, UNREACHABLE, NOT-MCP (it answered, but not in MCP), SKIPPED for ones we could not; NOT-SCANNABLE for account-hosted connectors that run outside your machine and cannot be inspected at all. Nothing we failed to see is hidden.
Sign in from the list — one click per server that needs credentials; the sign-in runs in a visible terminal and opens your system browser.
Local servers are never launched silently. Scanning a stdio server runs its code, so it happens only when you explicitly ask, with the consequence stated.

Which editors

One build covers the VS Code family, which all share this extension API: VS Code · Cursor · Windsurf · Kiro · Antigravity.

Not covered: JetBrains IDEs (IntelliJ Platform, a separate plugin ecosystem) and Zed (Rust/WASM extensions). Those need their own builds — the CLI works fine in all of them today.

One source of truth

The extension does no scanning of its own. It calls the mcpgawk CLI and renders exactly what the engine returns — the same rows the terminal prints — so the view can never disagree with the tool.