Skip to main content
Glama
minmax

pi-cli-mcp

Related Servers

Alternatives to pi-cli-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      658 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Delegates coding tasks to the locally installed Kimi Code CLI, reusing its auth, models, and configuration while adding tools for sessions, replies, model discovery, live turn steering, and history access.
      7
      12 npm
      MIT
    • 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
    • A
      license
      A
      quality
      C
      maintenance
      Enables any MCP client to browse, triage, search, read, and drive pi coding agent sessions through Pi Web's HTTP API via 25 tools. Supports listing and filtering sessions, reading transcripts, flagging conversations awaiting input, sending messages and waiting for replies, inspecting project diffs, and forking, renaming, or deleting sessions over either stdio or Streamable HTTP.
      25
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables delegation of coding tasks to a locally installed MiniMax Code CLI, leveraging user's existing login, models, and configuration.
      7
      38 npm
      MIT

    TDQS

    A4.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool maps to a distinct lifecycle stage: starting a session, messaging a running session, messaging an idle/finished one, listing running sessions, listing all sessions, and listing models. pi_reply and pi_send both send messages, but their descriptions clearly separate them by execution state and transport, so an agent should not confuse them.

    Naming Consistency4/5

    Tool names are consistently lowercase snake_case with a pi_ prefix, which makes the namespace predictable. The slight inconsistency is that pi is a bare root command, and pi_running/pi_sessions/pi_models are noun-style list commands rather than verb-style names, but the pattern is still easy to follow.

    Tool Count5/5

    Six tools is well-scoped for a server that manages an external CLI agent. Each tool handles a necessary interaction point—start, continue, interrupt, list live sessions, list historical sessions, and inspect available models—without redundancy or bloat.

    Completeness4/5

    The core session lifecycle is covered: create, resume, message mid-run, list running, list all, and check models. There is no explicit cancel/stop tool or read-only session history viewer, but pi_reply can resume any non-running session, so agents are not blocked by the omissions.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues