Skip to main content
Glama
TouHousand-Years

pi-subagent

by TouHousand-Years
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to pi-subagent

No user-submitted related servers found.

    Related Servers

    • 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
      4
      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.
      36 npm
      4
      MIT

    • Pi Session MCP

      plagor44-ux
      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
    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

    C2.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: pi_delegate initiates a task delegation, while pi_status retrieves the result of a run. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    Both tools follow a consistent pi_ prefix and use a verb_noun pattern (delegate, status). The naming is predictable, though the set is too small to fully demonstrate a broader convention.

    Tool Count3/5

    Two tools is on the thin side for a subagent delegation server, but it may be sufficient for a minimal async task lifecycle. The count is borderline but not unreasonable.

    Completeness3/5

    The pair covers the basic delegate-and-poll lifecycle, but there is no explicit cancel, list, or error-handling tool. Agents can work around this by waiting for status, but the surface feels minimal.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources