Pi.dev Integrates MCP Support into Core Functionality

MCP Integration into Pi.dev Core

Pi.dev has announced the integration of Multi-Call Protocol (MCP) into its core functionality. This marks a significant shift from the platform's previous position, which explicitly stated non-support for MCP. Users upgrading to Pi will now find MCP as a supported feature.

Reasons for the Change

The decision to incorporate MCP was influenced by the evolution of the protocol itself, which has seen improvements over the past year. While MCP could have been implemented as an extension, the development team re-evaluated its approach, leading to its inclusion in the core. The changes required for MCP integration were also found to be generally useful for other aspects of Pi, such as enabling easier use of Jev.

Architectural Alignment

Both Pi and MCP require a sandbox environment, specifically an interpreter, to function effectively. This shared need for a sandbox facilitated the integration. The current implementation of MCP in Pi exposes tools to a JavaScript sandbox, similar to how other harnesses like Codex operate.

Ongoing MCP Challenges

Despite the integration, the composability of MCP remains a challenge. Many MCP servers are still designed for harnesses that simply dump tools into context and prioritize token efficiency by returning text. Pi.dev's perspective on modern MCP aligns more with OpenAPI, advocating for intelligent tool discovery, structured data returns, and discoverable documentation for tools.