How MCP Wastes 4-32x More Tokens Than CLI (and How to Fix It)

Here are two numbers that should ruin your morning coffee:

71,929 tokens versus 123 tokens. Same 255 tools. Same machine. Same day.

The first number is what your agent pays — every single session — when 255 tools from 50 MCP servers load as raw JSON schemas into its context window. The second is what the same tool listing costs when discovery happens through a CLI instead.

That's a 300-page book vs. a sticky note, every single session, before your agent has answered a single question. If you're running multiple MCP servers in Claude Code, Cursor, or anything similar, you're paying the book price right now and probably don't know it.

I didn't believe it either, so I measured it with tiktoken (OpenAI's tokenizer) and built a tool around the result. Let me show you the receipts.

How MCP Wastes 4-32x More Tokens Than CLI (and How to Fix It)

Related reading

The MCP Tax Hit 42,000 Tokens on a Single Server. Here's What I Did About It.

Your MCP Servers Are Burning Tokens Before You Type a Word

MCP tool discovery eats 10,000 tokens. I got it down to 350.

Real Token Cost of MCP: 91K Tokens of JSON

I Measured MCP vs CLI for Agent Tool Use — MCP Used 17x More Tokens Per Call

Tools vs Raw Commands - The Token Cost Theory - Part 1