@svpino: MCP is not dead. For the people who keep saying "bUt McP pUts GaRbaGe iN yOuR cOntExT", that's an outdated complaint: N…

X AI KOLs Following News

Summary

A defense of MCP (Model Context Protocol) against criticism that it puts garbage in context, noting that modern tools like Claude Code, Codex, and Cursor implement progressive disclosure and load MCP tools on demand, making the complaint outdated. The author argues MCP is best for cloud-hosted platforms requiring authentication and discoverability.

MCP is not dead. For the people who keep saying "bUt McP pUts GaRbaGe iN yOuR cOntExT", that's an outdated complaint: None of the tools you use suffer from that. Check Claude Code, Codex, or Cursor: They all implement progressive disclosure and load MCP tools on demand. In 2026, MCP barely touches your context. For local agents, a CLI wins as long as there's a filesystem and a shell. But if you need to reach a cloud-hosted platform that requires authentication and discoverability, nothing beats MCP. I had to record a video about this.
Original Article

Similar Articles

MCP is dead?

Hacker News Top

A technical critique of the Model Context Protocol (MCP) arguing that it consumes excessive context window tokens, has low operational reliability, and overlaps with existing CLI/API approaches, with measurements from Quandri's stack showing 10.5% context usage.

Pi.dev: You Said No MCP

Hacker News Top

Earendil explains why Pi reversed its earlier 'no MCP' stance and brought Model Context Protocol support into the core, arguing modern MCP plus Codemode-style JavaScript sandboxing solves longstanding tool composition problems. The post also details how the changes improve tool metadata, deferred tool loading, and Jev integration.

Ask HN: Who is using MCP in production?

Hacker News Top

A Hacker News user asks about production usage of Model Context Protocol (MCP), with comments discussing its advantages and examples from real-world applications like UI updates and open data initiatives.