Skip to main content
Glama
nishimoto265

Agent Collaboration MCP Server

by nishimoto265
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Agent Collaboration MCP Server

No user-submitted related servers found.

    Related Servers

    • tmux-agents

      woonyong-choi
      A
      license
      A
      quality
      B
      maintenance
      Enables an AI agent to launch, monitor, and steer multiple coding agents running in tmux panes, including sending keystrokes, waiting for idle or output patterns, and managing sessions.
      9
      MIT

    • Multi-Agent MCP

      davidzong1
      A
      license
      Not graded
      quality
      B
      maintenance
      Creates and manages multi-agent teams of AI coding assistants (Claude Code, Codex CLI) that collaborate in tmux terminal sessions. Enables a leader agent to assign sub-tasks to team members for coordinated development.
      ISC

    • Terminal MCP Server

      Mohamedmagdy21
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create and interact with isolated tmux terminal sessions in real time, supporting command execution, output capture, and session management.
      -

    • ddx-term-mcp

      Dudoxx
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to execute commands in a shared tmux session that is simultaneously visible to a human via a web-based terminal UI.
      1
      MIT

    • wezterm-agent-mcp

      multiagentcognition
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables orchestration of multiple AI coding agents (Claude Code, Gemini CLI, etc.) in isolated Wezterm panes, allowing one agent to spawn, monitor, and communicate with others across projects.
      15 npm
      1
      -
    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

    B3.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have distinct purposes: screen capture, agent status, parallel status, parallel implementation, messaging, and agent starting. However, 'get_agent_status' and 'get_parallel_status' could be slightly confused as both retrieve status information, though they target different entities (agents vs. parallel sessions). The descriptions clarify this distinction, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case: capture_screen, get_agent_status, get_parallel_status, parallel_implement, send_message, and start_agent. The verbs are clear and appropriate (e.g., 'capture', 'get', 'parallel_implement', 'send', 'start'), with no deviations or mixed conventions.

    Tool Count5/5

    With 6 tools, the count is well-scoped for an agent collaboration server. Each tool serves a specific role in managing agents, parallel sessions, and tmux interactions, and none appear redundant or unnecessary. This is a typical range (3-15 tools) that supports the server's purpose without being overwhelming.

    Completeness3/5

    The tool set covers core operations like starting agents, checking status, sending messages, and screen capture, but has notable gaps. For example, there are no tools to stop or manage agents beyond starting them (e.g., stop_agent, restart_agent), and parallel sessions lack update or termination capabilities. This may cause agents to work around limitations, but basic workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources