MCP Is Dead
3 hours ago
- #developer tools
- #LLM efficiency
- #MCP critique
- MCP consumes significant context; tool definitions alone consumed 10.5% of the context window in tests, with Linear's definitions using over 12,800 tokens for 42 tools.
- Performance overhead is architectural; MCP adds a process layer, making calls slower (e.g., 3x slower per call and 9.4x slower on first call compared to REST API).
- Token efficiency is low; MCP used ~65x more tokens than a CLI approach for the same Linear issue lookup (CLI: ~200 tokens, MCP: ~12,957 tokens).
- Alternatives like CLI-first strategies and Skills (embedding CLI instructions) reduce context bloat by loading only needed tools on-demand.
- MCP is overkill for most developer workflows but may be justified for services lacking CLIs, requiring uniform auth, or enhancing database safety.
- Update: Claude Code's Tool Search with Deferred Loading has reduced context usage by 85%+, addressing earlier bloat, but performance and architectural issues remain.
- The rise of 'MCP supported' marketing parallels past trends like 'AI-powered,' often prioritizing features over stability, leading to tool bloat and crashes.