Skip to main content
Glama
turbin

pi-subagent-mcp

by turbin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to pi-subagent-mcp

No user-submitted related servers found.

    Related Servers

    • OMP Tandem

      Flyozzzz
      A
      license
      B
      quality
      A
      maintenance
      Enables coding agents to consult, design, implement, and review with an independent AI peer via Oh My Pi, using persistent project-isolated conversations and structured MCP tools for thinking, analysis, and authorized work.
      21
      2
      MIT

    • pi-delegate

      LarryStanley
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to delegate coding implementation and testing to a local pi agent via MCP tools, including dispatching task books, monitoring status, steering or aborting runs mid-execution, and retrieving results and transcripts.
      45 npm
      4
      MIT

    • pi-subagent

      guyiicn
      A
      license
      C
      quality
      B
      maintenance
      Enables MCP hosts to delegate coding tasks to Pi CLI as a programmable sub-agent with session tracking and process management.
      7
      3
      MIT

    • pi-agent-mcp

      a809384377
      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
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    pi_status, pi_read, and pi_wait all concern state but are clearly differentiated as snapshot, event stream, and blocking wait respectively. pi_dispatch and pi_send are also distinct (create new vs. message existing). No two tools appear to do the same thing.

    Naming Consistency5/5

    All nine tools are prefixed with pi_ and use lowercase imperative-style names (dispatch, send, read, wait, respond, abort, close, list). The only mild outlier is pi_status, which uses a noun rather than a verb, but it still fits the established pattern and creates no confusion.

    Tool Count5/5

    With nine tools, the server is in the ideal range for its purpose. Each tool addresses a specific aspect of the subagent lifecycle without redundancy or bloat.

    Completeness5/5

    The set covers the full workflow: dispatch to create, send to communicate, status/read/wait to observe, respond to handle dialogs, abort to interrupt, close to clean up, and list to enumerate. There are no missing operations that would trap an agent mid-workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources