Pi.dev: You Said No MCP
Points and comments are a snapshot, not live.
Pi adds MCP support after initially rejecting it, driven by Codemode integration.
Pi.dev, which previously declared it does not support MCP (Model Context Protocol), now includes MCP in its core. The decision was driven by changes in MCP over the past year and Pi's new Codemode feature. Codemode is a JavaScript sandbox that runs on the harness side for orchestrating and coordinating tool calls, enabling composition and deferred tool loading. It works with MCP to allow agents to combine tools flexibly, reducing context waste. Pi believes embracing MCP will help shape it for small harnesses, despite MCP's ongoing composition challenges.
What commenters are saying
Several commenters note the post assumes reader knowledge of MCP, with one linking the protocol for connecting LLMs to APIs. Two camps emerge: those who see MCP as pragmatically useful despite flaws (akin to USB-C or HDMI), and those who find the argument for Codemode weak since LLMs already have bash for tool composition. A commenter suggests MCP's value is broad compatibility over optimal design. Others discuss workarounds for MCP file uploads, including out-of-band handovers and inline base64. One commenter recommends the alternative harness hax for users who feel Pi has drifted from its original minimal vision.