Skip to main content
Glama
lunati228

CLI Subagents MCP Server

by lunati228
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to CLI Subagents MCP Server

No user-submitted related servers found.

    Related Servers

    • agentmux

      seaweedsoup98
      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
      12 npm
      Apache 2.0

    • subturn

      eshatalov
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables any MCP client to launch and manage subagent sessions in installed coding agents like Codex, Claude Code, Grok, and OpenCode, using your existing logins and chosen models.
      179 npm
      MIT

    • Sub-Agents MCP Server

      rorato10720
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets any MCP-compatible client run reusable Markdown-defined coding agents through a chosen backend CLI, returning their results to the same conversation. It enables delegation of coding tasks, shared agent definitions, permission modes, and cross-call session continuation.
      294 npm
      MIT

    • AgentNave

      TimWongUp
      A
      license
      A
      quality
      A
      maintenance
      Enables agent managers to launch and supervise Antigravity CLI, Claude Code, CodeBuddy Code, or Grok CLI as subagents through local MCP tools for starting, waiting on, and cancelling invocations.
      16
      1
      MIT

    • OpenCode MCP Orchestrator

      Mesya82
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-capable coding assistants to delegate repository investigation, bounded implementation work, and noisy command runs (tests, builds, linters) to sandboxed OpenCode agents. Each role can use an independently selected model, and only concise results are returned to the parent agent, which keeps responsibility for architecture and high-risk operations.
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.1/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: start, cancel, list, and accounts are unambiguous. However, wait, status, and result all relate to monitoring a job and could be confused—wait blocks for completion/messages, status is a snapshot, result is final output—but descriptions clarify intended usage.

    Naming Consistency5/5

    All tools use the consistent subagent_ prefix with snake_case and clear action verbs. No deviations in style or convention.

    Tool Count5/5

    8 tools is well-scoped for a subagent orchestration server, covering the full job lifecycle without redundancy. Each tool earns its place.

    Completeness4/5

    The surface covers starting, monitoring (wait/status/list), interacting (message), retrieving results, cancelling, and account management. A minor gap is the lack of a tool to retrieve full transcript/logs or delete jobs, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources