MCP Sprawl Audit

Audit MCP server sprawl on this machine for Claude Code, Codex CLI and Grok CLI. Counts how many copies of each MCP server the running agent sessions hold, what they cost in memory, which ones are duplicates, unused, unpinned or bundled in plugins, and which can run as one shared HTTP copy instead. Use when the machine is slow with many agent sessions open, when someone asks how much memory MCP servers use, or before adding more MCP servers. Read-only; it writes a plan and changes nothing.

5 stars 4 forksAI, LLMs & Agents

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add karanb192/mcp-sprawl-audit --skill mcp-sprawl-audit
Manual install
git clone --depth 1 https://github.com/karanb192/mcp-sprawl-audit.git /tmp/mcp-sprawl-audit
mkdir -p ~/.claude/skills
cp -r /tmp/mcp-sprawl-audit/. ~/.claude/skills/mcp-sprawl-audit

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# MCP sprawl audit

Each agent session starts its own copy of every local (stdio) MCP server in its config.
Fifty sessions means fifty copies, plus an idle npx or uvx launcher above each one. This
skill measures that and proposes a plan. It never edits a config, starts or stops a
process, or prints a secret value. From a command line it prints only a package name or a
script's file name.

## 1. Run the audit

```sh
python3 <this skill's folder>/scripts/audit.py          # Markdown report
python3 <this skill's folder>/scripts/audit.py --json   # the same data, structured
```

Python 3.11 or newer reads every config. On older Python, Codex and Grok servers that
exist only in their `config.toml` are missed, and the script says so. Reading 30 days of
session logs takes a few seconds; `--no-usage` skips it, `--days N` changes the window.

What it reads, all locally:

| Agent | Config | Usage (tool calls per session) |
|---|---|---|
| Claude Code | `~/.claude.json` (user and local scope), each project's `.mcp.json`, enabled plugins, managed-mcp.json | `~/.claude/projects/**/*.jsonl` |
| Codex CLI | `codex mcp list --json` (includes plugin servers), else `~/.codex/config.toml` | `~/.codex/sessions/**/*.jsonl` |
| Grok CLI | `~/.grok/config.toml` and project ones, then Claude's, Cursor's and the project `.mcp.json`, which Grok loads by default | `~/.grok/sessions/**/updates.jsonl` |

Processes come from `ps`. A copy is a process an agent started that matches a configured
Read the full skill on GitHub

Details

Skill name
mcp-sprawl-audit
License
MIT
Repo updated
19 October 2026

FAQ

What does the MCP Sprawl Audit skill do?

Audit MCP server sprawl on this machine for Claude Code, Codex CLI and Grok CLI. Counts how many copies of each MCP server the running agent sessions hold, what they cost in memory, which ones are duplicates, unused, unpinned or bundled in plugins, and which can run as one shared HTTP copy instead. Use when the machine is slow with many agent sessions open, when someone asks how much memory MCP servers use, or before adding more MCP servers. Read-only; it writes a plan and changes nothing.

How do I install the MCP Sprawl Audit skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add karanb192/mcp-sprawl-audit --skill mcp-sprawl-audit. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is MCP Sprawl Audit popular?

It lives in karanb192/mcp-sprawl-audit, which has 5 GitHub stars and 4 forks.

Related skills

Polis Protocol

5

ymxlx/polis-protocol

Set up and run a self-improving, multi-vendor AI agent team with the Polis Protocol — a markdown `_polis/` folder where each agent is a citizen with a capability card, tasks are contracts routed to whoever has the best track record by a learning router, settled work files lessons that compound into team memory, and citizens can amend the protocol itself. Use whenever several AI agents (any vendor) share one project and "who should do this" is a real question: founding a polis, registering as a citizen, opening/claiming/settling a contract, filing a lesson, running a chavruta review before a hi

AI, LLMs & Agents

Tomorrowdao Agent Skills

6

TomorrowDAOProject/tomorrowDAO-skill

TomorrowDAO governance, BP, and resource operations for agents.

AI, LLMs & Agents

Engineering Intelligence

5

devravik/engineering-intelligence

Senior engineering quality control for Antigravity agents (detect, attribute, prioritize, repair, verify).

AI, LLMs & Agents

Staff Engineer

6

johngbl/staff-engineer

Pragmatic Senior Engineering Skill. Transforms coding agents into Staff-level pragmatic engineers via evidence-based verified loops (TDD + linter + review), anti-guessing discipline, greppable Clean Code, and workspace sandboxing. XP with AI — simple by default, ceremony only when earned. Self-contained, no external files required.

AI, LLMs & Agents

AI Citation Auditor

5

madrank8/ai-citation-auditor

Audit any page to predict whether AI search engines (Google AI Overviews and AI Mode, ChatGPT, Perplexity, Gemini, Claude) will cite it, then return a prioritized fix list. Scores 6 dependency-free layers gated by a retrieval-rank prerequisite: answer-first extractability, evidence corroboration, consensus alignment, source-quality fingerprint, SEO-slop detection, and machine structure. Runs on native web fetch and search or on pasted content, with no paid APIs, connectors, or crawlers required. Two modes: AUDIT (URL or draft in, scored scorecard plus fixes out) and REWRITE (turn one section i

AI, LLMs & Agents

Skills Builder

6

jaystarz1/Claude-Skill-Builder

Creates world-class agent Skills following Anthropic's official specifications and best practices. Use when building custom Skills for web, desktop, or API - handles validation, generation, and packaging.

AI, LLMs & Agents

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.