Agent Cross-Session MCP
Related Servers
Alternatives to Agent Cross-Session MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables already-running AI coding agents on the same project to register, discover one another, and exchange durable direct messages so they can share progress and avoid conflicting work.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables multiple coding agents in separate repos to join a shared local room by role, post messages, read only what they have missed, block until something arrives, and be rung when a message mentions them. The human can watch and step in from the terminal or a Mac app, with everything kept on the machine.1MIT
- AlicenseAqualityCmaintenanceEnables local messaging between Claude Code, Codex, Pi, and other coding-agent sessions on the same machine, allowing them to discover each other, send updates, ask questions, and reply.820 npm2AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables peer-to-peer communication, discovery, shared state, and file coordination between AI coding agents across machines and sessions.21 npm18Elastic 2.0
- AlicenseNot gradedqualityBmaintenanceLets independent Claude Code and Codex sessions running in different tools and projects discover each other and exchange questions, coordination messages, and replies that arrive back in the conversation that asked. Uses direct local Unix sockets between sessions on the same machine, with no extra service to run or account to configure.19 npmMIT
- AlicenseAqualityBmaintenanceEnables multiple AI agents and humans working in the same project to share status, exchange messages, and claim files through a local collaboration board. It supports project-specific enablement, conflict-aware file claims, and shared state via SQLite.7MIT
TDQS
Scored across 6 tools
Each tool targets a distinct slice of cross-session awareness: peers (all sessions at a glance), session_detail (one session's timeline), whoami (self), overlaps (collision risk), announce/board (write/read notes). The descriptions explicitly cross-reference each other ('Use it after peers', 'Other sessions read it with board'), making selection unambiguous.
Names are readable but follow no single convention: session_detail uses snake_case while peers, overlaps, announce, board, and whoami are bare single words mixing nouns (peers, board) with verbs (announce) and a question-style identifier (whoami). Predictable enough to navigate, but not a consistent verb_noun pattern.
Six tools is well-scoped for a cross-session coordination server: three read/awareness tools, two messaging tools, and one identity tool. Every tool earns its place with no redundant surface.
The surface covers the core lifecycle — discover sessions, inspect activity, detect collisions, broadcast notes, read notes, and identify self. Minor gaps exist: no targeted messaging to a specific session, no reply/threading on the board, and no way to clear or expire notes.