← Back to Skills Marketplace
abhinas90

MCP Token Auditor

by abhinas90 · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
41
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install mcp-token-audit
Description
Analyze your MCP server config to estimate token consumption per tool. Identify which tools are blowing up your context window, get per-role groupings to kee...
README (SKILL.md)

MCP Token Auditor

Stop your subagents from silently failing due to tool schema bloat.

If you have 20+ MCP servers, your tool schemas alone can hit 209k tokens — exceeding Claude's context window before your subagent even starts working. The subagent dies. Silently. Zero error in the UI.

This tool audits your MCP config and gives you an exact breakdown.

What it does

  1. Reads your mcp.json (or any MCP config)
  2. Estimates token consumption per tool based on schema complexity
  3. Groups tools into logical roles (code-analysis, deployment, testing, data, communication, file-system)
  4. Calculates total token footprint vs your target limit
  5. Outputs per-role groupings you can copy directly into role-specific MCP configs

Quick start

# Basic audit
python3 mcp-token-audit.py --config ~/.claude/mcp.json

# With custom token target (default: 60,000)
python3 mcp-token-audit.py --max-tokens 50000

# JSON output for scripting
python3 mcp-token-audit.py --json

Example output

═══════════════════════════════════════════
  MCP TOKEN AUDIT REPORT
═══════════════════════════════════════════
  Config: ~/.claude/mcp.json
  Servers: 34
  Total tools: 566
  Total estimated tokens: 209,412
  Target limit: 60,000
  Utilization: 349.0%

───────────────────────────────────────────
  PER-ROLE BREAKDOWN
───────────────────────────────────────────
  communication      42,891 tokens  █████████████████████
  deployment         38,221 tokens  ███████████████████
  code-analysis      35,120 tokens  █████████████████
  data               28,450 tokens  ██████████████
  testing            24,310 tokens  ████████████
  general            40,420 tokens  ████████████████████

  🔴 Total tool schema tokens exceed target by 149,412 tokens
     Fix: Split MCP servers into per-role configs

───────────────────────────────────────────
  SUGGESTED ROLE GROUPINGS
───────────────────────────────────────────
  communication (mcp-communication.json) — 42,891 tokens ✅
  deployment (mcp-deployment.json) — 38,221 tokens ✅
  code-analysis (mcp-code-analysis.json) — 35,120 tokens ✅
  ...

Why this matters

The #1 silent failure mode in multi-agent Claude Code setups isn't model quality. It's tool schema bloat. When your subagent's context window is 60% full before it even processes your prompt, you get: silent hangs, partial completions, and "prompt too long" errors with no diagnostic.

This tool catches the problem before your subagent crashes.

Prerequisites

  • Python 3.8+
  • An MCP config file (works with any MCP-compatible format)
  • No API keys required — runs entirely locally

Files

  • scripts/mcp-token-audit.py — Main audit script
  • SKILL.md — This file
Usage Guidance
Reasonable to install if you want local MCP token-footprint reporting. Run it only on MCP config files you intend to inspect, and treat saved reports as potentially sensitive because they can disclose your MCP server and tool layout.
Capability Assessment
Purpose & Capability
The skill says it reads an MCP config, estimates per-tool schema token usage, groups tools by role, and reports optimization suggestions; the Python script implements that local analysis.
Instruction Scope
Runtime instructions are explicit CLI examples with a disclosed default config path and optional output path; no prompt override, hidden role change, or automatic high-impact action was found.
Install Mechanism
The artifact contains SKILL.md and one Python script with no declared dependencies, install hooks, package-manager scripts, or startup behavior.
Credentials
Reading ~/.claude/mcp.json or a user-specified MCP config is proportionate, but generated reports can reveal local MCP server and tool names.
Persistence & Privilege
No network access, subprocess execution, privilege escalation, background worker, credential use, or persistence was found; the only write behavior is saving a report when the user supplies --output.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install mcp-token-audit
  3. After installation, invoke the skill by name or use /mcp-token-audit
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: Analyze MCP config token consumption, get per-role groupings to prevent subagent context window failures
Metadata
Slug mcp-token-audit
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is MCP Token Auditor?

Analyze your MCP server config to estimate token consumption per tool. Identify which tools are blowing up your context window, get per-role groupings to kee... It is an AI Agent Skill for Claude Code / OpenClaw, with 41 downloads so far.

How do I install MCP Token Auditor?

Run "/install mcp-token-audit" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is MCP Token Auditor free?

Yes, MCP Token Auditor is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does MCP Token Auditor support?

MCP Token Auditor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created MCP Token Auditor?

It is built and maintained by abhinas90 (@abhinas90); the current version is v1.0.0.

💬 Comments