worker-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKER_MCP_PI_PATH | No | Absolute path to the `pi` coding-agent binary (defaults to searching PATH for `pi`). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
}
}
} |
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| spawn_pi_sessionB | Spawn a new pi coding agent session in the specified workspace directory. |
| send_pi_commandB | Send a prompt or slash command to a running session. |
| cancel_pi_commandA | Abort the currently running command in a session. Sends abort to the agent; force-terminates after 2s if it doesn't settle. |
| terminate_pi_sessionA | Stop a session and remove it, freeing its id for reuse. Use this to clear a session that has crashed, wedged, or is no longer needed. |
| list_pi_sessionsA | List all active sessions and their status. |
| get_pending_actionsA | Retrieve details of a tool call or action currently awaiting approval. |
| approve_actionC | Approve an intercepted tool execution. |
| reject_actionA | Deny an intercepted tool execution and feed feedback/refusal back to the agent. |
| set_risk_policyA | Update the risk-based auto-approval policy for a session at runtime. Controls which actions are auto-approved based on risk level. |
| get_auto_approved_logA | Retrieve the audit log of actions that were auto-approved by the risk policy. Useful for reviewing what the worker did without coordinator intervention. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct operation: session lifecycle, command control, action approval, or policy/audit. There is no meaningful overlap between send/cancel, approve/reject, or session management tools.
All tools use lowercase snake_case verb-first names with clear objects. Session and command tools consistently use the 'pi' prefix, while approval and policy tools use simple verb_noun names, creating a predictable and readable pattern.
Ten tools cover the full session lifecycle plus approval and risk-policy management without redundancy. Each tool addresses a concrete need and earns its place in the server.
The set covers spawning, commanding, cancelling, listing, terminating, approving/rejecting actions, and auditing auto-approved actions. A minor gap is the lack of an explicit tool for retrieving session transcripts or command output if send_pi_command is non-blocking.