Back to Devoured - November 12, 2026
DEVOURED
MCP vs CLI vs Skills: What Each Costs in Context

MCP vs CLI vs Skills: What Each Costs in Context

AI OpenRouter
Using MCP servers for AI agents can balloon token costs by thousands; deferring tool definitions via Tool Search is a necessary optimization.
What: The GitHub MCP server with 46 default tools adds ~19,000 input tokens per request. Using OpenRouter's Tool Search to defer definitions can reduce upfront costs to under 600 tokens.
Why it matters: High token overhead in MCP tool-calling limits agent efficiency; moving to scoped toolsets or lazy loading is essential for cost-effective production AI agents.
Takeaway: Add "defer_loading": true to your MCP tool configurations and implement "openrouter:tool_search" to minimize context window bloat.
Deep dive
  • MCP servers load all tool schemas into the model context by default
  • A simple GitHub task used 59,417 tokens with MCP compared to 1,421 with a direct CLI
  • Tool results (e.g., large JSON objects) often cost more than the definitions themselves
  • Tool Search allows models to search and load only required tools on demand
  • CLI tools remain the most efficient if the model is well-trained on them; MCP is best when auth/permissions are required
Decoder
  • MCP (Model Context Protocol): An open standard for connecting AI assistants to data and tools.
  • Token inflation: The phenomenon where providing extensive tool definitions consumes a large percentage of an LLM's available context window.
Original article

Full article content is not available for inline reading.

Read the original article →

Explore all 61 articles in today's digest

Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi