Skip to main content
Glama

Related Servers

Alternatives to subagent-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that gives orchestrator agents fine-grained control over interactive Claude Code sessions running inside tmux, enabling mid-session steering, interruption, and token-efficient result extraction.
      15
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Persistent tmux-backed MCP server that lets Claude Code control Codex CLI's interactive TUI, including slash commands and $imagegen. Run local shells, SSH, Docker, WSL, REPLs, and supported coding agents through durable PTY sessions.
      19
      5,268 npm
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Terminal multiplexer MCP server for orchestrating parallel AI agents. Manages workspaces, panes, surfaces with send_input/read_screen/spawn_agent/stop_agent tools. Supports Claude Code, Codex, Gemini, Cursor CLI agents with lifecycle management, browser automation, and agent status push via Claude --channels.
      10
      30
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that manages interactive CLI agent pools using tmux, enabling creation, control, and communication with agents like Claude and Codex.
      7
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A standalone MCP server that lets AI coding agents running in separate tmux panes read each other's output, send messages and keystrokes, and coordinate multi-agent workflows through standard MCP tool calls. It shells out directly to tmux, so no external dependencies beyond tmux itself are required.
      52 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: launch creates a subagent, check retrieves output, list enumerates subagents, send_to delivers messages, and stop terminates. No two tools overlap in function.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, using common operational verbs (launch, check, list, send_to, stop). This creates a predictable and easy-to-navigate API.

    Tool Count5/5

    With five tools, the set is well-scoped for subagent lifecycle management. Each tool covers a necessary operation without redundancy, making the count feel intentional and complete.

    Completeness5/5

    The set provides full lifecycle coverage for subagents: create (launch), read (check/list), update (send_to), and delete (stop). There are no obvious missing operations for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues