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.
      43 PyPI
      4
      MIT
    • A
      license
      Not graded
      quality
      A
      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.
      14
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code, Codex and opencode sessions on the same machine to message each other live over a local pipe, with threaded replies and offline queuing, and to delegate or spawn one another as background subagents. Messages persist in SQLite and any running server can take over as broker, so peers stay reachable without a daemon.
      84 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code and Codex sessions in the same project to discover each other, coordinate status and file ownership, exchange signed end-to-end encrypted messages, and delegate desktop-app tasks to Codex Computer Use.
      84 npm
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 17 tools

    Disambiguation4/5

    The tools are functionally distinct, addressing message flow (send/reply), system status, and resource management (reservations). There is minimal ambiguity, though functions like 'track' and 'status' overlap in their focus on agent activity.

    Naming Consistency3/5

    The naming convention is readable but lacks strict consistency. It mixes pure verbs ('send', 'read'), nouns acting as functions ('inbox', 'reservations'), and compound names ('wait_reply', 'selftest'), making the pattern slightly unpredictable.

    Tool Count5/5

    The server performs a highly complex coordination role across multiple agents and manages resource locking, requiring a comprehensive set of tools. With 17 tools, the surface is well-scoped and appropriately dense for its purpose.

    Completeness5/5

    The tool set is extremely comprehensive, covering the full lifecycle of a message (send, reply, track, wait) along with resource management (reserve/release) and agent self-assessment (survey/selftest). There are no obvious functional dead ends within the relay domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues