Skip to main content
Glama
songzhifei512

multi-agent-bridge

by songzhifei512
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to multi-agent-bridge

No user-submitted related servers found.

    Related Servers

    • ATMcp

      MidCheck
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables multiple LLM agents across devices to form teams, share knowledge, memory, and tasks with live status via a web dashboard and distributed-systems reliability.
      Apache 2.0

    • Agent Squad Bridge

      kagtgi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple AI coding CLIs (Claude Code, Gemini/Antigravity, Codex, and OpenCode) to collaborate as a coordinated team by routing cross-agent prompts, sharing messages and review tickets, tracking tasks on a shared store, and isolating each agent in its own Git worktree with turn-budget safeguards—all inspectable and steerable from a local web dashboard.
      MIT

    • PeerBridge MCP

      Hoylon
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects multiple AI agents (Codex, Claude Code, Grok, etc.) into a coordinated, auditable team with shared memory, task ownership, and human oversight, enabling parallel collaboration without conflicts.
      238
      Apache 2.0

    • JustClone Coordination MCP

      Hazgar2111
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      A production-grade coordination hub that enables AI agents and human teams to work as a single organism by sharing tasks, context, decisions, and persistent memory across projects. It features two-tier agentic memory with per-agent hot caches, inter-agent messaging, and multi-agent authorship tracking for seamless collaboration.
      2
      -

    • agent-pool-mcp

      rnd-pro
      A
      license
      A
      quality
      D
      maintenance
      Multi-agent orchestration server that enables parallel task delegation, sequential pipelines, cron scheduling, and cross-model peer review via CLI providers like Codex, Antigravity, OpenCode, and Claude Code.
      42
      16 npm
      5
      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

    B3.1/5.0

    Scored across 57 tools

    Disambiguation3/5

    Most tools are distinct and well-described, but there are notable overlaps: bus_send and agent_send_message appear nearly identical, and the run_* family (run_codex, run_claude, etc.) overlaps with the generic agent_invoke. The detailed descriptions help, but the sheer number of similar lifecycle and transition tools adds selection risk.

    Naming Consistency4/5

    Tool names are consistently snake_case and frequently grouped by domain prefix (task_*, memory_*, shared_memory_*), which aids recognition. However, verb ordering is inconsistent: some tools follow verb_noun (read_file, run_codex) while others follow noun_verb (task_create, memory_add, inbox_read), creating a minor pattern break.

    Tool Count1/5

    With 57 tools, this server far exceeds the 25+ 'too many' threshold and is above the 50+ extreme mismatch mark. Even considering the broad multi-agent orchestration domain, this number of tools is likely to overwhelm an agent's selection ability and would be better split into separate focused MCP servers.

    Completeness4/5

    The task lifecycle is extensively covered (create, claim, complete, fail, approve, decide, interrupt, resume, supersede, reassign, depend, fork, sediment), and workflow, messaging, and memory systems have comprehensive operations. Minor gaps exist such as no shared_memory_delete and no direct file write, but these are workable through the agent execution tools, so the surface remains largely complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources