- Earendil reversed its public stance and added native MCP support to Pi after previously dismissing it.
- The decision came after developers realized modern MCP improvements enabled useful core architecture updates, including better Jev integration.
- Earendil introduced ‘Codemode,’ a JavaScript-based sandbox running on the harness side to orchestrate and coordinate tool calls flexibly.
If you have been following the discourse around the developer tool Pi, you likely remember a very proud, very public stance: Pi does not support MCP. Earendil Engineering made no secret of its skepticism, even publishing dismissive statements about the protocol across blogs and podcasts. That is why users upgrading their systems this week experienced total whiplash upon discovering that MCP is now a fully supported, core piece of functionality.
Announced via a candid engineering update titled ‘You Said No MCP!’, the team acknowledged their abrupt about-face. According to Earendil, the primary driver for the change is simple: the world is not static, and the MCP of today is drastically different from the protocol they originally critiqued. While the feature could have remained a third-party extension, the engineering team realized that incorporating it directly into the core unlocked broader architectural benefits, such as significantly streamlining the use of Jev within Pi.
Key Details
Despite warming up to the protocol, Earendil remains clear-eyed about its flaws. The team noted that many existing MCP servers are still built for legacy harnesses that dump tools blindly into context windows, struggling with token efficiency. To fix this, Earendil envisions MCP functioning much closer to OpenAPI, featuring intelligent tool discovery, structured data returns, and robust integration with a JavaScript sandbox.
To bridge the gap between old limitations and modern LLM capabilities, Earendil also pulled back the curtain on ‘Codemode.’ Operating on the trusted harness side rather than an isolated tool environment, Codemode acts as a JavaScript-powered sandbox. It gives agents the flexibility to orchestrate, sequence, and combine tool calls dynamically, maintaining state directly within the session transcript. By moving past initial skepticism and embracing the protocol, Earendil aims to actively shape the future of MCP from the inside.
Source: Original Coverage
Leave a Reply