Session Relay
Related Servers
Alternatives to Session Relay
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for inter-agent communication. Gives multiple Claude Code sessions a shared message board, agent registry, and orchestration layer — backed by a cloud relay so agents can coordinate across machines, repos, and teams.837 npmMIT
- AlicenseAqualityAmaintenanceEnables MCP-capable coding agents to discover peers, send messages, and read inboxes through a small self-hosted relay on your LAN or VPN, including role-based fan-out to teams. Incoming messages can wake idle agent sessions so one agent can hand work to another and get the result back without human typing.246Apache 2.0
- AlicenseAqualityAmaintenanceSelf-hosted MCP + REST continuity hub for coding agents. Tracks unfinished work, progress, overlap, reminders, and project context across Cursor, Codex, Claude Code, and other MCP clients.74235MIT
- AlicenseBqualityAmaintenanceEnables AI coding agents on different machines and accounts to work one repository as a team by declaring file and symbol claims before editing, so collisions are refused up front rather than discovered at merge. It also supports delegating tasks between teammates' agents, which do the work with their own tokens and commit, with replies, commit shas, claims and messages landing on one shared board.202MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents in different editors and MCP clients to share messages, project context, notes, task ownership, handoffs, and advisory file claims through a local SQLite-backed coordination server. Supports MCP stdio, MCP Streamable HTTP, a JSON HTTP API, and a local CLI for multi-project agent collaboration.MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for shared file state, overlap warnings, and messaging between AI coding agents working in parallel on one GitHub repo. Works with Claude Code, Cursor, Codex, VS Code, Kiro, Windsurf and Perplexity; hosted service by Crews with a free solo tier.-
TDQS
Scored across 9 tools
Each tool targets a distinct operation: identity, session listing, registration lifecycle, conflict checking, and messaging. The messaging tools (send, ask, answer, inbox) form a clear workflow with no real overlap. Agents can reliably pick the right tool based on purpose.
All names are lowercase single tokens with no separators, which is readable. However, the set mixes nouns (board, inbox) and verbs (register, send, ask) along with the phrase 'whoami', so it lacks a strict verb_noun pattern.
Nine tools is well-scoped for a session relay: presence, team awareness, conflict checks, and messaging are all covered without redundancy. Each tool earns its place.
Core lifecycle and coordination operations are present: register/unregister, heartbeat via register/inbox, board visibility, check, and send/ask/answer/inbox. Minor gaps exist, such as explicit read-marking or richer team management, but agents can work around them.