Disable unused MCP servers to reclaim startup tokens

MCP / Agents·14 hours ago·verified 14 hours ago·easy·~5 min setup·verified

Turn off MCP servers unrelated to the current project—their tool schemas still consume context at session start.

#mcp #tokens #cost #context

The problem

A kitchen-sink MCP config loads GitHub, DBs, browsers, and SaaS tools into every session whether you need them or not.

The hack

Keep a minimal default MCP set; enable project-scoped servers only where needed; audit with `/mcp` and `/context`.

Why it works

MCP tool schemas are part of startup context. Disabling unused servers is one of the highest-ROI cost cuts.

Setup

1. Run `/mcp` and `/context` to see per-server cost. 2. Remove or disable servers you have not used this week. 3. Prefer project-local MCP config for repo-specific tools. 4. Re-measure context after the trim.

Additional details

Start with official GitHub (or Context7) before adding niche servers.

Source

anthropic·View original →·by Anthropic Docs

Does this still work?

Discussion

No comments yet. Be the first to say whether this worked for you.