MCP Is Dead; Long Live MCP
a day ago
- #CLI
- #AgenticEngineering
- #MCP
- The industry discourse has shifted from MCP (Model Context Protocol) to CLIs (Command Line Interfaces) as the current trend, influenced by social media and industry hype cycles.
- Token savings with CLIs exist, especially for well-known tools in the LLM's training dataset, but custom CLI tools require additional context and instructions, similar to MCP.
- MCP over HTTP (as opposed to stdio) offers significant advantages for enterprise use, including centralized capabilities, better auth and security, telemetry, and dynamic content delivery.
- Centralized MCP servers enable richer capabilities, easier management of stateful workloads in ephemeral environments, and improved observability and telemetry for organizational tool use.
- MCP resources and prompts allow for dynamic, server-delivered content that is always up-to-date, facilitating org-wide knowledge sharing and consistent updates without manual syncs.
- The article critiques the influencer-driven hype cycle in AI, comparing it to past trends like Ivermectin or anti-vax conspiracies, and emphasizes the need for engineering discipline in agentic engineering.
- For organizations moving beyond individual 'vibe-coding' to structured agentic engineering, MCP provides the necessary architecture for consistency, quality, and correctness in AI-produced software.