Audit the token cost

Build-along · ~8 min at your own keyboard

Installed servers can add their tool descriptions to your context before you type — how much depends on your version and settings (some versions load tool details only when needed). One course author found a CRM server costing more context than his whole skill library. Don't assume either way: measure. Run /context with the server on and off, and weigh what it costs against how often you use it.

The long version: Auditing MCP cost ↗

Do this

0/4

Checkpoints

▸You should now see each MCP's token cost in /context.
▸You should now see a keep or evict verdict for each.
▸You should now see a lower overhead number after eviction.

The three ways this goes wrong

MCP lines are not shown, or show near zero. — Start a fresh session after the install, then run /context. If they're still tiny, your version may load tools on demand — record that; it's a valid finding.
You are unsure which to evict. — Evict any server you have not used in a week. You can reinstall it.
The number does not drop. — Remove the server from .mcp.json or with the remove command, then restart.

Share what happened

Paste each server's token cost, your verdicts, and the after number if you evicted.

Strip API keys, passwords, and tokens before you paste. Swap them for [KEY].

🔒 Don't paste confidential, personal-health, or payment info.