Why Developer Agents Still Need MCP: Simon Willison Responds to Criticism

Simon Willison has pushed back against a recent Hacker News discussion framing the Model Context Protocol (MCP) as an unnecessary detour. The critics' premise is straightforward: if you are already running a full-blown terminal agent like Claude Code, Codex, or Meta Muse, it already has access to the file system and local tools. A middleware layer like MCP thus looks like an artificial bottleneck on the model's capabilities.

Why Raw Access Doesn't Equal Better Integration

The point missing from the debate lies beyond raw capability. Willison points out that MCP's value today isn't about whether an agent can read a file. It's about having a standardized, isolated, and auditable way to expose specific data (like an internal database or a third-party API) to the agent without handing it a blank check over the entire system context. For developers, this is the difference between a structured interface and dumping entire repositories into a prompt hoping the model figures it out.

Context Isolation Changes the Model's Role

This distinction is crucial for teams deploying agents beyond their own local machines. A terminal agent with unfettered access is great for fast local iteration but non-transferable to pipelines or production environments that require granular access control. MCP acts as a contract: the agent knows exactly what tools and data are available, and the system knows exactly what the agent is touching.

Limits of Raw Access Hit Hard in Practice

Removing this layer means stepping backward into opaque integrations. The agent might see everything, but the team loses the ability to compartmentalize what the model should and shouldn't see. Without a protocol, control shrinks to banning directories via prompts, which is a security patch, not a systemic solution.

Enterprise Adoption Will Settle the Debate

The deciding factor for MCP's survival won't be enthusiasm from local hackers, but adoption within teams facing stricter security and governance requirements. If integrations into existing platforms and data sources shift away from custom webhooks toward standardized MCP servers, the protocol will secure its role as a fundamental building block.

Lilith's verdict

The access debate misses the point entirely. Production reality breaks down to who holds the keys to the audit log when the agent breaks loose and starts browsing the entire company.