/mcp-audit
Audit connected MCP servers for token overhead, redundancy, and security. Use when sessions feel slow or before adding new MCPs.
One skill from pro-workflow.
shell
$ npx -y skills add rohitg00/pro-workflow --skill mcp-audit --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/mcp-audit
Context preview
The summary Claude sees to decide when to auto-load this skill.
Audit connected MCP servers for token overhead, redundancy, and security. Use when sessions feel slow or before adding new MCPs.
Stats
Stars2,638
Forks255
LanguageJavaScript
SKILL.md
mcp-audit.SKILL.md
--- name: mcp-audit description: Audit connected MCP servers for token overhead, redundancy, and security. Use when sessions feel slow or before adding new MCPs. user-invocable: true --- # MCP Audit Analyze MCP server overhead and recommend cleanup. ## Trigger Use when: - Sessions feel slow or expensive - Adding a new MCP server - Context fills up quickly - Reviewing project configuration ## Key Insight Each MCP server adds ALL its tool descriptions to every API request. A server with 20 tools adds ~2K-4K tokens per request, regardless of whether you use those tools. ## Audit Steps ### Step 1: List Active Servers Check all MCP configurations: ```bash cat .claude/settings.json 2>/dev/null | grep -A 50 "mcpServers" cat ~/.claude/settings.json 2>/dev/null | grep -A 50 "mcpServers" ``` ### Step 2: Count Tools Per Server For each server, estimate token overhead: - 1-5 tools: ~200-500 tokens (low overhead) - 6-15 tools: ~500-1500 tokens (moderate) - 16-30 tools: ~1500-3000 tokens (high)