Pi Worker MCP
io.github.zguiyangv0.1.1Updated Oct 8, 2026
A host-agnostic MCP worker runtime for supervising local Pi coding-agent processes.
Overview
Runs and supervises local Pi coding-agent worker processes through stdio MCP tools such as spawn, status, steer, continue, abort, and list.
- What it does
- A host-agnostic MCP worker runtime that supervises bounded local Pi coding-agent processes over local stdio MCP and Pi RPC. Its tools are pi_spawn, pi_status, pi_steer, pi_continue, pi_abort, and pi_list. It also provides setup, doctor, update, and uninstall commands that pin launch configuration for Codex, Zed, and OpenCode hosts. It does not manage Pi credentials, providers, or default models.
- When to use it
- Use it when an assistant should start, monitor, steer, and stop local Pi coding-agent workers, including isolated implementation work in Git worktrees. It suits users who already run Pi locally and want a supervising agent to coordinate bounded worker tasks.
- Requirements
- Node.js 20+, a locally installed and configured pi executable, and Git when using isolated worktrees. Runs as a local stdio process, typically via npx. Optional environment variables include PI_WORKER_COMMAND, PI_WORKER_MAX_WORKERS, PI_WORKER_RPC_TIMEOUT_MS, PI_WORKER_IDLE_TIMEOUT_MS, PI_WORKER_TASK_TIMEOUT_MS, and PI_WORKER_ALLOWED_ROOTS. Pi reads its own local authentication configuration.
Installation
In SourceWeft
- Open Pi Worker MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@zguiyang/pi-worker-mcp
A host-agnostic MCP worker runtime for supervising local Pi coding-agent processes. It uses local stdio MCP and Pi RPC; it is not a hosted service and does not manage Pi credentials, providers, or default models.
Quick start
Prerequisites: Node.js 20+, a locally installed and configured pi executable, and Git when using isolated worktrees.
The setup command selects supported hosts and pins their launch configuration to the exact CLI version. A host never silently drifts to a new release.
Supported hosts and scope
Project scope is relative to the directory where setup runs. Zed starts project-defined MCP servers only after the worktree is trusted. Existing configuration is minimally merged; uninstall removes only this server’s entry.
Manual / generic MCP configuration
Any stdio MCP client can launch:
This is the release configuration. Do not point user installations at a checkout’s dist/ directory.
Commands
doctor checks Node, the local Pi executable, and selected host configuration without starting a model task or exposing credentials. update is not a package manager: run a newer CLI via npm/npx and it updates only selected configuration pins. uninstall never removes a whole host config, Pi config, Skills, or npm cache.
Model ownership and host independence
Pi owns provider authentication, available models, and its default model. The worker runtime can validate an optional per-worker override and report the effective model, but never configures credentials. Core runtime behavior—Pi RPC, lifecycle, model semantics, concurrency, and permissions—is independent of Codex, Zed, and OpenCode. Host adapters only read, merge, and remove launch configuration.
MCP tools
pi_spawn, pi_status, pi_steer, pi_continue, pi_abort, and pi_list supervise bounded local workers. Successful spawn/continuation means Pi accepted work, not that it is correct; the supervising agent must inspect results and integrate changes. Use worktree mode for isolated implementation work.
Runtime configuration
No secret environment variable is required; Pi reads its own local authentication configuration.
Development from source
Source mode is only for contributors:
For release-equivalent testing, use npm pack and execute the resulting .tgz from a clean temporary directory. npm link is not package acceptance.
Registry metadata
server.json follows the official MCP Registry schema and declares an npm stdio package representation. npm and Registry publication remain separate, explicit actions.
License
Source: README.md at commit 64590c3
Tools
0Version history
1- v0.1.1LatestOct 8, 2026
More servers like Pi Worker MCP
Agent Link
io.github.mikusnuz
Lets an AI coding agent spawn other agent CLIs as subprocesses, exchange questions and answers, and collect their results.
Notemend
io.github.zharkodv-cmd
Lets a coding agent pull a queue of comments pinned on a website, fix the issues, and resolve them.
Solhint Mcp
io.github.vschernoff
Lets an assistant lint and autofix Solidity smart contracts in a project using Solhint, with rule explanations and config lookup.