MCP Audit Skill for Claude

Audit connected MCP servers for token overhead, redundancy, and security. Use when sessions feel slow or before adding new MCPs.

629 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

2755

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/rohitg00/pro-workflow --skill mcp-audit

The instruction itself

11 sections, as written by the author

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:

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?

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

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)

Thresholds

Total servers: <10 (ideal), 10-15 (monitor), >15 (reduce)
Total tools: <80 (ideal), 80-120 (monitor), >120 (reduce)
Per-server: <15 tools (ok), 15-30 (filter), >30 (split or disable)

Rules

Never disable servers without user confirmation
Estimate token savings for each recommendation
Consider task context — a server might be unused today but critical tomorrow
Check for disabledMcpjsonServers to avoid re-recommending already-disabled servers

Other skills for the same job

different authors, same section of the catalogue

Skill Creator

by anthropics

vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Replace with description of the skill and when Claude should use it.

35 tokens

Dispatching Parallel Agents

by ZhanlinCui

×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts