mcp-audit — Claude Code command: what it does, how to install
Audits active MCP servers, estimates token overhead from tool schemas, and flags unused integrations to disable.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat mcp-audit does
Each active MCP server attaches all its tool descriptions to every API request. A server with 20 tools consumes around 2K-4K tokens per prompt regardless of whether those tools run.
Running /mcp-audit inspects configured servers, tallies their tools, and highlights unused integrations. It compares your setup against target thresholds: fewer than 10 servers and under 80 tools are considered optimal. If you run more than 15 servers or over 120 total tools, the command flags candidates to remove. Individual servers with over 30 tools are flagged to split or turn off.
What it helps with
- find unused MCP servers in active sessions
- cut token overhead caused by tool definitions
- measure token usage per API request across MCP servers
- identify MCP servers carrying more than 30 tools
Example prompts for the agent
- /mcp-audit
- Run
/mcp-auditto inspect token usage from connected tools
How to install mcp-audit
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflow2Manually: put the files in place
.claude/commands/mcp-audit.mdCall it with /mcp-audit. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/mcp-audit.mdCall it with /prompts:mcp-audit. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/mcp-audit.prompt.mdManually: put the files in place
.gemini/commands/mcp-audit.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about mcp-audit
How to install mcp-audit in Claude Code?
Run /plugin marketplace add rohitg00/pro-workflow followed by /plugin install pro-workflow@pro-workflow. Alternatively, place the command file at .claude/commands/mcp-audit.md.
What does mcp-audit do?
It lists active MCP servers with their tool counts, calculates per-request token overhead, and points out servers you can disable.
What thresholds does mcp-audit follow?
The command targets fewer than 10 servers and under 80 total tools. It advises reducing integrations once you cross 15 servers, 120 total tools, or 30 tools on a single server.
Source text
mcp-audit.md · MIT
--- description: Audit MCP servers for token overhead, redundancy, and usage — recommend servers to disable for faster sessions --- # /mcp-audit - MCP Server Optimization Audit your MCP servers and reduce token overhead. ## Quick Start Run to see: - Active MCP servers and their tool counts - Estimated token overhead per request - Servers you haven't used recently - Recommendations for disabling/keeping ## Key Insight Every MCP server adds ALL its tool descriptions to EVERY API request. A server with 20 tools adds ~2K-4K tokens per request whether you use it or not. ## Thresholds - Servers: <10 ideal, >15 reduce - Total tools: <80 ideal, >120 reduce - Per server: <15 ok, >30 split or disable ## Usage ``` /mcp-audit ```
© Rohit Ghumare · MIT · rohitg00/pro-workflow