Cross-Agent Teams (xats)
Related Servers
Alternatives to Cross-Agent Teams (xats)
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceLocal stdio MCP server for discovering teammates’ coding-agent sessions, exchanging messages and small text files, and checking delivery status across computers. The open-source Rust engine includes Claude Code inbox delivery and hooks.1,789Apache 2.0
- AlicenseAqualityBmaintenanceSelf-hosted daemon connecting Claude Code, Codex, and other coding agents across machines via MCP + A2A: delegate tasks, ask questions, share results, and wake sessions.132Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA 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
- AlicenseNot gradedqualityBmaintenanceEnables local discovery, reading, and messaging between running Codex and Claude Code sessions through MCP.216 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn 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 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to discover and exchange text messages between existing, locally authenticated Claude Code and Codex sessions on the same machine, using installed clients without API keys.420MIT
TDQS
Scored across 17 tools
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.
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.
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.
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.