No user-submitted related servers found.
Scored across 12 tools
Each tool targets a distinct phase of the delegate lifecycle: starting (spawn, run, spawn_batch), monitoring (status, sessions), interacting (steer, answer, follow_up), and cleanup (abort, forget). Descriptions clearly differentiate async vs sync and running vs finished states, so misselection is unlikely.
Most tools use imperative single-word verbs (spawn, steer, abort) or compound verbs (spawn_batch, follow_up), but two are bare nouns (sessions, models) instead of list-style verbs like list_sessions. This is a minor deviation from an otherwise predictable, straightforward naming scheme.
At 12 tools, the server is well-scoped for its purpose—managing delegated pi agents. Each tool covers a necessary operation without redundancy, and the count falls comfortably within the 3–15 ideal range for a focused MCP server.
The tool surface provides full lifecycle coverage: launch, monitor, interact, redirect, follow-up, abort, clean up, and list. It also includes init and models for setup and model selection. There are no obvious gaps that would cause agent dead-ends.