Skip to main content
Glama
jerfowler

Agent Communication MCP Server

by jerfowler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Agent Communication MCP Server

No user-submitted related servers found.

    Related Servers

    • Claude Swarm MCP Server

      Mayank1805
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables multi-agent orchestration and coordination using specialized, persistent Claude agents for complex workflows like financial analysis and research. It supports intelligent agent handoffs, local storage, and pre-built team templates through Claude Desktop.
      MIT

    • Symphony of One MCP

      ai-wes
      A
      license
      A
      quality
      F
      maintenance
      A multi-agent orchestration system that enables multiple Claude instances to collaborate through a centralized hub with a shared workspace and real-time communication. It features integrated task management, role assignment, and persistent memory to facilitate complex, synchronized agent workflows.
      12
      3 npm
      4
      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
    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.4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Tools have generally distinct purposes (e.g., create_task vs. read_task), but some overlap exists (archive_completed_tasks vs. archive_tasks). Descriptions help disambiguate most cases.

    Naming Consistency5/5

    Nearly all tools follow a consistent verb_noun pattern (e.g., create_task, list_agents, report_progress). The few exceptions like protocol_config still fit the pattern.

    Tool Count4/5

    18 tools cover a broad range of task lifecycle and communication features. The count is slightly high but justified by the domain scope.

    Completeness4/5

    Covers task creation, reading, progress updates, completion, archiving, restoration, and diagnostics. Minor gap: no explicit task deletion, but archiving handles cleanup.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources