Pi TaskExec MCP server

Pi TaskExec

Pi TaskExec is an MCP orchestration and control layer between a main Agent (the Supervisor) and a local Pi execution layer. It is not an independent agent. The Supervisor keeps requirement interpretation, architecture and risk decisions, authorization, task decomposition, integration, review, and final acceptance; Pi TaskExec creates, connects to, and supervises bounded Pi workers and returns structured status and results for independent verification.

The product is a host-agnostic stdio MCP server that supervises local Pi coding-agent processes over Pi RPC. It is not a hosted service and does not manage Pi credentials, providers, or default models.

The core flow is: Supervisor → Pi TaskExec MCP → Pi Worker → structured status/result → Supervisor review and acceptance. inspect/implement are tool capability profiles and direct/worktree are working-directory modes; neither is an operating-system security sandbox.

Pi TaskExec is distributed through npm and the MCP Registry, with GitHub tags and releases providing the matching Skill source. Version 0.2.2 makes confirmed updates fully replace the Pi TaskExec MCP entry and Skill files, without inheriting old settings. Interactive setup, connection diagnostics, Host-provided workspace Roots and all six pi_* tools remain supported. remove skill remains deferred.

For source development, build first and use --local-dev when installing a local launch entry. Published installations use the npm latest release.

CLI surface

mcp serve is the single service-start contract used by Host configuration and the MCP Registry entry. All six MCP tools (pispawn, pistatus, pisteer, picontinue, piabort, pilist) are preserved.

Shortened. The full README is on GitHub.