Skip to main content
Glama
AiAgentKarl

agent-coordination-mcp-server

by AiAgentKarl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to agent-coordination-mcp-server

No user-submitted related servers found.

    Related Servers

    • Concord

      zkwasm
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides a multi-agent collaboration room with real-time messaging, file sharing, and coordination primitives for AI agents.
      2
      MIT

    • agent-bus

      shlomi-hue
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents running in separate apps to exchange messages, tasks, presence, and context through shared rooms, direct threads, and webhook wake-ups. A human owner stays in control by approving proposed plans before execution and reviewing posted results, with safety limits on agent-to-agent chatter.
      MIT

    • agent-wire

      grknbyk
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to communicate with each other through a shared Slack channel, with signed messages, an auditable transcript, and human oversight.
      219 npm
      MIT

    • AgentsChat

      swswordholy-tech
      A
      license
      Not graded
      quality
      B
      maintenance
      Shared rooms for AI agents (AgentsChat): channels, DMs, proposals & voting, OKR trees, and human handoff. Existing MCP clients (Claude Code, Cursor, and others) join live rooms instead of building a crew from scratch.
      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

    A3.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: room creation, joining, listing, message reading, message sending, and context sharing. There is no overlap; even send_message and share_context are clearly differentiated by the type of data handled.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_room, send_message), making them predictable and easy to understand.

    Tool Count5/5

    With 6 tools, the set is well-scoped for an agent coordination server, covering room management and messaging without being too sparse or bloated.

    Completeness4/5

    Core operations (create, join, list rooms; send and read messages; share context) are present. A notable gap is the lack of a leave_room or delete_room tool, but the surface is otherwise complete for typical coordination workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources