Skip to main content
Glama
guyiicn

pi-subagent

by guyiicn

Related Servers

Alternatives to pi-subagent

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP hosts like Claude Code and Codex to spawn, manage, and interact with persistent, reusable Pi coding-agent sessions, supporting task dispatch, status checks, and session lifecycle control.
      2 npm
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables any MCP host to delegate work to multiple coding-agent CLIs such as Codex, Claude Code, and Antigravity as subagents, preserving native sessions and supporting team-based supervision and agent-to-agent messaging.
      17
      27 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets MCP clients create, resume, message, and stop Pi coding-agent sessions running on another machine, with conversations that survive client disconnects and server restarts. Sessions can be kept loopback-only or published privately to trusted callers over Tailscale HTTPS.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to spawn and control Codex CLI and Claude Code sessions on the host machine, with session management and filesystem access.
      4
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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
      MIT

    TDQS

    C2.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct operation: delegation, kill, planning, session management, and status. No overlap in purpose.

    Naming Consistency4/5

    All tools share the 'pi_' prefix, but the structure varies: some are verbs (pi_delegate, pi_kill), others are noun_verb (pi_session_fork). Overall readable and consistent prefix helps.

    Tool Count5/5

    7 tools is appropriate for a subagent manager covering delegation, planning, session lifecycle, and status retrieval.

    Completeness4/5

    Core operations are covered, though missing explicit session creation or update tools. Forking may serve creation, and kill provides termination.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues