From pro-workflow
Audits connected MCP servers for token overhead, redundancy, and security. Use when sessions feel slow or before adding new MCPs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pro-workflow:mcp-auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze MCP server overhead and recommend cleanup.
Analyze MCP server overhead and recommend cleanup.
Use when:
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.
Check all MCP configurations:
cat .claude/settings.json 2>/dev/null | grep -A 50 "mcpServers"
cat ~/.claude/settings.json 2>/dev/null | grep -A 50 "mcpServers"
For each server, estimate token overhead:
Questions to ask:
Disable servers that:
Keep servers that:
MCP AUDIT
Active servers: [N]
Total tools: [N]
Estimated overhead: ~[N]K tokens per request
Server Analysis:
[name] — [N] tools, ~[N] tokens
Status: KEEP / DISABLE / REVIEW
Reason: [why]
Recommendations:
Disable: [list]
Keep: [list]
Review: [list]
Projected savings: ~[N]K tokens per request (~$X.XX per session)
disabledMcpjsonServers to avoid re-recommending already-disabled serversnpx claudepluginhub rohitg00/pro-workflow --plugin pro-workflowAudits MCP server configs across project/user/plugin scopes for JSON validity, security, compliance using claude mcp CLI and file inspections.
Manages Model Context Protocol (MCP) servers for Claude Code projects: installs/configures .mcp.json, OAuth remotes, runtime enable/disable, troubleshooting connections.
Checks and configures MCP servers in .mcp.json for project integration. Use for setup, status checks, adding core servers like context7 and sequential-thinking, or specific ones like playwright.