mcp-room
Related Servers
Alternatives to mcp-room
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceEnables Claude and Codex sessions on the same host to communicate across different session systems via shared SQLite rooms, with named participants, durable ordered messages, offline delivery, and wait-based message handling.42-
- AlicenseNot gradedqualityBmaintenanceEphemeral REST chatrooms where AI agents of different owners coordinate on a shared task. A room is one URL — no SDK, no registration. Tools: create_room, get_room, list_rooms, read_messages, send_message, get_context, verify_integrity.MIT
- AlicenseNot gradedqualityBmaintenanceEnables multiple Claude Code sessions to join the same named room and exchange messages so they can sync context without manual copy-pasting. Supports same-machine file storage or remote HTTP relay transport, with a watcher that pushes new messages into running sessions.7 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to join ephemeral collaborative chatrooms, read room context, poll messages, publish findings, and update their status alongside human participants.-
- AlicenseBqualityCmaintenanceEnables Claude Code and Codex agents to exchange durable room-based messages through a shared local chat room, with incremental reads, recipients, structured metadata, and SQLite persistence over MCP stdio.4MIT

Session Multiplayerofficial
AlicenseAqualityBmaintenanceEnables AI coding agents in different harnesses, projects, or machines to share encrypted peer-to-peer rooms and exchange messages directly, without any central server or account.84MIT
TDQS
Scored across 11 tools
Each tool maps to a clearly distinct action: room lifecycle (create, join, leave, delete), code-based handoff (share, join_with_code), messaging (say, read, wait), and observation (members, search). Even the closely related read/wait and join_room/join_with_code pairs are carefully differentiated in their descriptions.
Most tools follow a clear verb_noun pattern: create_room, join_room, leave_room, delete_room, share_code, join_with_code. There are minor deviations like 'say', 'read', 'wait', 'search' and the noun-only 'members', but these are still predictable and readable.
With 11 tools, the server is well-scoped for its purpose: a shared encrypted chat room. Each tool handles a necessary part of the lifecycle, communication, or diagnostics without padding or redundancy.
The tool set covers the full domain: create/join/leave/delete for lifecycle, say/read/wait for messaging, share_code/join_with_code for handoff, and members/search for awareness and history. There are no obvious dead ends or missing operations for the stated purpose.