Skip to content- Sources: post, HN discussion
- Summary: Earendil states it has reversed an earlier public position against MCP and now ships MCP support in the core of its Pi agent. The stated mechanism exposes MCP tools to a JavaScript sandbox that runs on the trusted harness side rather than in the environment where bash runs. The post also states what did not improve: MCP is still hard to compose, and Earendil attributes that to the servers and harnesses rather than to the protocol.
- Why it matters: Codex exposes MCP tools through the same mechanism, so sandbox-side tool exposure is a converging pattern rather than one vendor's preference.
- Follow-up: Re-read the Model Context Protocol specification at its next revision for a composition mechanism, which would move the problem off the servers and harnesses Earendil blames.