MCP Schema Tax: GitHub MCP Server Injects ~55,000 Tokens Before Your First Message

Every MCP tool definition consumes 550–1,400 tokens of context. The official GitHub MCP server exposes 93 tools, injecting roughly 55,000 tokens into every conversation before a single user character is typed. Source

This isn't theoretical overhead. Perplexity CTO Denis Yarats stated that MCP tool schema overhead consumes up to 72% of available context window space at scale. A formal protocol change proposal (SEP-1576) is now open in the MCP GitHub repo proposing schema redundancy reduction and dynamic tool selection — validating the problem at the protocol level.

The community is already building around the problem. mcp2cli replaces full schema injection with lightweight CLI-based tool discovery, achieving 96–99% token cost reduction in benchmarks. The pattern: for many agentic use cases, thin CLI wrappers outperform full MCP servers on both cost and latency. opencli (3,992 stars) takes this further, converting any website, Electron app, or local binary into an AI-agent-ready CLI interface.

Practitioners are confirming this in the field. A community thread tracking real MCP daily-driver stacks found that after 3 months, everyone converges on 3-4 daily servers regardless of initial install count. More than 6 active MCP servers produces context noise without proportional capability gain. And a separate r/ClaudeAI analysis benchmarked the overhead at 37% input token inflation at scale.

The strategic implication: as context windows hit 1M tokens and paddo.dev argues that context scarcity is ending, the schema tax becomes a cost problem rather than a capacity problem. But at current API pricing, 55K wasted tokens per conversation adds up fast. The fix needs to come at the protocol level, not just through clever workarounds.