mcp-auditlisted

# 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) - 30+ tools: ~3000+ tokens (excessive — consider tool filtering) ### Step 3: Check Usage Questions to ask: - Which servers were actually used this session? - Which servers haven't been used in 7+ days? - Are there servers with overlapping functionality? - Are there servers only needed for specific tasks? ### Step 4: Recommend Actions **Disable** servers that: - Haven't been used in 7+ days - Overlap with another active server - Are project-specific but you're in a different project **Keep** servers that: - Are used every session (filesystem, git) - Provide unique capabilities needed for current work - Have low tool count (<5 tools) ## Output ```text MCP AUDIT Acti