Skip to main content
Glama

Related Servers

Alternatives to Cross-Agent Teams (xats)

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that connects AI coding agents (Claude Code, Codex, Cursor, etc.) on the same machine via a shared message bus, enabling them to chat, delegate tasks, and collaborate privately without cloud or internet.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP central server that lets multiple AI agents (e.g., Claude Code, kimi-code) exchange private messages, shared channel broadcasts, and unified message streams via MCP tools, with SQLite persistence and per-connection identity binding.
      97 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 17 tools

    Disambiguation3/5

    Messaging tools (send_message, send_message_by_id, broadcast, broadcast_to_role, get_inbox, get_delivery_status) are clearly differentiated by target and fan-out semantics. However, the identity layer is crowded: xats_bind, register_agent, reconnect, bind_channel, bind_runtime_identity, pre_register_codex_pane, and detect_tmux_pane all orbit the same 'who am I / which pane' problem, and only the very long descriptions keep them apart. Two tools (subscribe_channel_wake, pre_register_codex_pane) are reserved for internal proxies/launchers, adding further noise for a normal agent.

    Naming Consistency4/5

    Consistent snake_case verb_noun pattern throughout (send_message, get_inbox, list_agents, register_agent, unregister_self, bind_channel, detect_tmux_pane), with suffixes like _by_id and _to_role used predictably. Minor deviations: the xats_ prefix on a single tool (xats_bind), a bare noun-verb verb (reconnect, echo) that break the pattern.

    Tool Count3/5

    17 tools is at the heavy end for a messaging/identity server, and the count is inflated by arguably non-core entries: echo is a trivial filler and subscribe_channel_wake plus pre_register_codex_pane are internal-only paths. The remaining surface is roughly commensurate with the domain, so it's borderline rather than wildly oversized.

    Completeness4/5

    Strong lifecycle coverage: registration, reconnect, unregister, channel/pane binding, private and broadcast messaging, inbox read with cursor semantics, and delivery status. Gaps are minor-to-moderate: no cross-team agent discovery, no agent-detail lookup, no message deletion or acknowledgement, and no team management operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues