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.58 PyPI4MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseAqualityBmaintenanceEnables AI agents to discover and exchange text messages between existing, locally authenticated Claude Code and Codex sessions on the same machine, using installed clients without API keys.420MIT
- 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.2541456 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Desktop, Claude Code, and Codex to send approved coding tasks to separate Oh My Pi sessions on Windows, monitor their progress, and wake the assistant when work finishes.MIT
- AlicenseAqualityBmaintenanceSelf-hosted daemon connecting Claude Code, Codex, and other coding agents across machines via MCP + A2A: delegate tasks, ask questions, share results, and wake sessions.131Apache 2.0
TDQS
Scored across 20 tools
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.
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.
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.
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.