{
  "id": 3440419,
  "title": "How MCP Wastes 4-32x More Tokens Than CLI (and How to Fix It)",
  "url": "https://urgent.news/2026/08/26/how-mcp-wastes-4-32x-more-tokens-than-cli-and-how-to-fix-it",
  "topic": "ai",
  "section": "AI",
  "published": "2026-08-26T05:58:03.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/mcptokensaver/how-mcp-wastes-4-32x-more-tokens-than-cli-and-how-to-fix-it-441m"
  },
  "original_language": "en",
  "account": "Here are the key facts from the story about MCP wasting more tokens than CLI, and how to fix it:\n\n- 71,929 tokens are used by MCP to load 255 tools from 50 servers as raw JSON schemas into context window, compared to just 123 tokens when using a CLI.\n- This represents a massive 300-page book worth of token usage vs. a sticky note, before the agent even answers a single question.\n- When an agent connects to an MCP server, the full tool catalog is sent, including descriptions, input schemas, required parameters, etc. This schema information is only needed twice per session.\n- Most of the time, the 71K-token schema just occupies space in the context window while the actual code, conversation and diffs fight for limited tokens.\n- Benchmark studies have found that MCP can cost 4-32 times more tokens than CLI for the same work. On a 128K context window, tool definitions alone consume ~56% of the space.\n- This context overhead makes it impossible to fit the agent's codebase, conversation history and reasoning chains on a 64K window. The agent will degrade, forget earlier instructions, or truncate context sooner.\n- The wasted tokens represent real money spent on redundancy like punctuation and curly braces. It adds up to significant costs, especially on cheaper models.\n- The problem of schema redundancy was acknowledged by the official MCP proposal and confirmed by multiple independent benchmarks.\n- To fix it, the solution is to only pass a names-only listing of tools to the model, and fetch the full schemas only when needed. A CLI called mcptoon implements this approach by compressing the schemas out of the context window.\n- This dial approach keeps the tool listing to just 123 tokens for 255 tools, instead of the massive 71K+ tokens currently sent. The model can then retrieve schema details selectively.\n- Independent experts from Anthropic, Firecrawl, Scalekit, Scale, Microsoft, and ProMCP all agree that eager schema injection is inefficient and the current approach doesn't scale. The fix is to pay for the names, not the full schemas.",
  "summary": "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…",
  "key_points": [
    "MCP uses 71,929 tokens to load 255 tools, compared to CLI's 123 tokens.",
    "Sending the full tool catalog wastes 56% of a 128K context window.",
    "Fix involves sending only tool names, fetching schemas only when needed."
  ],
  "editors_take": "MCP's inefficient use of tokens, wasting 4-32 times more than CLI, stems from transmitting unnecessary schema information, a redundancy that inflates costs and limits context window capacity.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}