Nexus Relay
Related Servers
Alternatives to Nexus Relay
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceConnects Claude Desktop and Claude Code, enabling autonomous exchange of messages, files, and code while keeping their context windows separate.43 PyPI4MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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
- AlicenseAqualityCmaintenanceEnables 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.14MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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 npm3MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding sessions in different vendor clients, such as Claude Code and Codex, to exchange questions, reviews, and handoffs locally in either direction without a lead agent.518 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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 npm1MIT
TDQS
Scored across 17 tools
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.
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.
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.
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.