pi-delegate-mcp
Related Servers
Alternatives to pi-delegate-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables an assistant to run pi coding-agent tasks in the background: dispatching a task, polling its status and tool trace, reading the final result, and cancelling it when no longer needed, all without pulling the delegate's context into its own conversation.MIT
- AlicenseBqualityBmaintenanceEnables Claude Code to delegate narrow coding and research jobs to a pi coding agent backed by an Ollama model, with background execution, polling, sandboxed write jobs, and verification artifacts.9GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables a coding agent such as Codex or Claude Code to delegate work to a local Pi coding-agent session, including second-opinion reviews, bulk reading kept out of the main context, and follow-up turns that retain context. Operators control what is possible by defining workspace and execution-profile aliases in a local config file, so clients cannot choose directories, models, providers, or permission levels themselves.1,489 npm1MIT
- AlicenseAqualityBmaintenanceEnables a main agent to delegate tasks to reusable Pi agents with persistent sessions, question handoffs, bounded waiting, and in-run correction, while continuing other work. It supports named agents, context retention across MCP restarts, and result retrieval through MCP without repeated polling.117 npmMIT
- AlicenseCqualityBmaintenanceEnables a primary agent in Antigravity IDE to delegate coding tasks to background subagents across multiple model backends, with crash recovery, process cleanup, and human-in-the-loop approval for destructive actions.20MIT
- AlicenseBqualityBmaintenanceLets a coding agent delegate planning, coding, review, and research tasks to other headless coding agents on the machine, returning concise summaries and keeping code changes isolated until approved.15MIT
TDQS
Scored across 12 tools
Each tool targets a distinct state or action, and the three delegation entry points (spawn/run/spawn_batch) are explicitly differentiated by blocking behavior and fan-out. The message-sending trio (answer/steer/follow_up) is clearly disambiguated by delegate state, and descriptions even cross-reference each other (spawn vs steer vs follow_up).
Most names are concise lowercase verbs (spawn, run, steer, abort, forget, init) with a consistent compound pattern for spawn_batch/spawn variants. The deviation is noun-style list tools (sessions, models) and the short 'init', which break a strict verb convention but remain readable and predictable.
12 tools map cleanly onto the delegation lifecycle: launch (spawn/run/spawn_batch), monitor (status/sessions), interact (steer/follow_up/answer), stop (abort), and housekeeping (forget/models/init). Each earns its place with no redundant or filler tools.
The surface covers the full delegate lifecycle including batch fan-out, mid-task redirection, post-completion follow-up, Q&A unblocking, and cleanup. Minor gaps exist (e.g. no dedicated blocking wait-for-completion on a spawned session, no explicit per-provider model-filtering view), but agents can work around these via status/run.