Skip to main content
Glama
wybe-labs

Session Multiplayer

Official
by wybe-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Session Multiplayer

No user-submitted related servers found.

    Related Servers

    • crosstalk by epode-studio

      crosstalkofficial

      epode-studio
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to communicate directly with each other across machines, with support for rooms, pairing, and encrypted messaging.
      2 npm
      6
      MIT

    • agent-link

      Riccardo8888
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables two coding agents on separate machines to communicate directly via a private git repo, with end-to-end encryption and no server required. Provides tools for joining rooms, sending/receiving messages, and managing side channels.
      56
      MIT

    • slm-mesh

      qualixar
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables peer-to-peer communication, discovery, shared state, and file coordination between AI coding agents across machines and sessions.
      49 npm
      19
      Elastic 2.0

    • pillowfort

      slee1996
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create and manage ephemeral private chat rooms with end-to-end encryption, invite people or other agents via private links, and approve device fingerprints for real-time chat, drawing, and mini-games.
      MIT

    • Multiplayer MCP Server

      yukakust
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to join a secure agent-to-agent network for team collaboration, with tools for direct messaging, shared rooms, and approval-gated file/command requests.
      MIT
    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

    A4.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool maps to a distinct action: invite creation, joining, sending, checking unread messages, reading history, status, display name, and leaving. The closest pair, check_messages and show_history, is clearly separated by clearing versus non-destructive reading.

    Naming Consistency4/5

    The tool set overwhelmingly follows a verb_noun pattern (create_invite, join_room, send_message, check_messages, show_history, set_display_name, leave_room). The single noun-only tool, status, is a minor deviation that could have been get_status.

    Tool Count5/5

    Eight tools is well-scoped for a session-multiplayer collaboration server. Each tool addresses a real user or agent need without redundant surface area.

    Completeness5/5

    The core workflow is fully covered: invite/join/leave room lifecycle, sending and receiving messages, non-destructive history, status visibility, and profile naming. There are no obvious dead ends or missing operations that would prevent the primary multiplayer session use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources