Skip to main content
Glama

Related Servers

Alternatives to Nexus Relay

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude Desktop and Claude Code, enabling autonomous exchange of messages, files, and code while keeping their context windows separate.
      58 PyPI
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple Claude sessions on the same PC — Claude Desktop chats, Cowork tasks and Claude Code — to coordinate as siblings, sharing full context, splitting work and handing tasks to each other. Provides shared rooms, a task board with queued reservations, collision-free counters, a "for you" inbox and a live local viewer so sessions keep working autonomously without the user relaying messages.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code, Codex, and other coding-agent sessions on the same machine to message each other, exchange tracked tasks with owners and states, and coordinate through channels, broadcasts, and multi-session asks without typing into terminals. Messages are routed by what the receiver is doing — next tool call, end of turn, or a held-back digest — so a flood of traffic doesn't interrupt active work.
      254
      14
      56 npm
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 20 tools

    Disambiguation3/5

    The core messaging tools are mostly distinct, but reserve and file_reservation_paths are exact aliases, as are release and release_file_reservations; reservations is also a closely related listing tool. The descriptions explicitly label the aliases, so an agent can choose, but the duplication still creates avoidable selection ambiguity.

    Naming Consistency3/5

    Most names are lower snake_case and readable, but conventions are mixed: verb-first commands like send, read, reply, reserve, and release sit beside noun-style tools like inbox, reservations, summary, and status. The alias pairs also use inconsistent naming patterns, such as reserve vs. file_reservation_paths and release vs. release_file_reservations.

    Tool Count3/5

    Twenty tools is at the heavy end for a relay/coordination server. The compatibility aliases for file reservations add redundancy, and the administrative/UI-mapping tools expand the surface, making the count borderline rather than tightly scoped.

    Completeness4/5

    The messaging lifecycle is well covered: send, inbox, read, reply, progress, cancel, wait_reply, track, close, search, and summary cover the main workflow, and file reservations plus relay/UI diagnostics are included. Minor gaps remain, such as no explicit topic-listing operation, but there are no major dead ends.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data