# pi-subagent-bridge

Source: https://glimind.com/server/npm%2Fpi-subagent-bridge
Registry id: `npm/pi-subagent-bridge`
Status: unknown

## Install

```json
{
  "mcpServers": {
    "pi-subagent-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "pi-subagent-bridge"
      ]
    }
  }
}
```

Claude Code:

```sh
claude mcp add pi-subagent-bridge -- npx -y pi-subagent-bridge
```

## Tools (14)

- `pi_apply_changes`: Conflict-checks and applies a completed isolated run's patch to the coordinator checkout.
- `pi_discard_workspace`: Removes a completed run's isolated worktree and branch.
- `pi_doctor`: Checks the Pi executable, bridge state, allowed roots, and git availability.
- `pi_get_run`: Diagnostic state for recovery and debugging, including any Pi session_id.
- `pi_get_run_events`: Returns a sanitized cursor-based event feed when the status snapshot is insufficient.
- `pi_get_run_status`: Returns a bounded activity snapshot for deciding whether and how to steer a run.
- `pi_list_models`: Searches Pi's structured RPC model catalog.
- `pi_read_result`: Reads an already completed result after an interrupted wait connection, including any Pi session_id.
- `pi_recent_tool_calls`: Returns timestamped, ordered, sanitized tool_execution_start audit entries only.
- `pi_run`: Preferred one-call delegation API that starts Pi, waits internally, and returns structured result and workspace metadata.
- `pi_start`: Starts one Pi --mode rpc subprocess per run and returns a stable run_id immediately.
- `pi_steer`: Injects a follow-up instruction into a running Pi session.
- `pi_stop`: Sends Pi's RPC abort command, waits for the grace period, then terminates the child process group if needed.
- `pi_wait`: Waits for a run to reach a terminal state or returns a heartbeat with progress.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.