Skip to main content
Glama

Related Servers

Alternatives to mcp-room

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      B
      maintenance
      Enables 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.
      4
      2
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Ephemeral 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      8
      4
      MIT

    TDQS

    A4.4/5.0

    Scored across 11 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues