Skip to main content
Glama
Ryrahul

session-relay

by Ryrahul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to session-relay

  • OpenHuddle

    nika110
    A
    license
    A
    quality
    A
    maintenance
    Connects multiple AI coding agents on a team through a shared hub, giving each agent live teammate status, a versioned master prompt, a shared task board, questions and answers, and file claims so agents don't overwrite each other's work. Works across Claude Code, Codex, and Cursor while code itself continues to flow through git.
    10
    1,771 npm
    5
    MIT

Related Servers

  • Agent Cowork Memory

    rxthlessbeats
    A
    license
    Not graded
    quality
    A
    maintenance
    Lets coding agents like Codex, Cursor, and Claude Code share and resume each other's chats, and attach to a common task with saved notes that can be searched later. This keeps task state and decisions in sync no matter which agent you switch to.
    76 npm
    2
    MIT

  • agent-session

    anaknegeri
    A
    license
    A
    quality
    A
    maintenance
    Universal session & handoff layer for AI coding agents: shared task, decision, blocker and test state, checkpoints, and deterministic handoff between Claude Code, Codex, OpenCode, Cursor, Cline, pi and omp. Local SQLite, git-aware, 25 tools + 7 resources over stdio or streamable-http.
    26
    MIT

  • chat-across

    VictorZhang01
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI coding agents to collaborate on the same project by sharing session briefs and reading each other's native transcripts, memories, and instructions in place, with zero-copy, across different agent tools.
    58 npm
    MIT

  • Relay

    worklab-studio
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables separate Claude Code sessions across a team to see teammates' live presence, warn before editing a file someone else is editing, route shared-contract changes to the developers whose code depends on them, and produce structured handoffs when a session ends.
    304 npm
    1
    MIT
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A3.7/5.0

Scored across 15 tools

Disambiguation4/5

Most tools split cleanly between live-session coordination and shared-session handoffs, and descriptions clarify their targets. A few boundaries are softer: live_status vs. team_activity both summarize activity, and update_live vs. update_session both mutate metadata, though their scopes differ.

Naming Consistency4/5

Most names are verb-first and use recognizable live/session domain prefixes, such as start_live, get_session, and list_sessions. live_status and team_activity are noun phrases, and comment_on_session uses a preposition, which are minor deviations from the dominant pattern.

Tool Count4/5

The 15 tools cover two related workflows—live collaboration and shared-session handoffs—and each has a plausible role, including helper tools like share_template and get_session_diff. The count sits at the high end of the ideal range, with a couple of status/update tools that could potentially be merged, but it is not excessive.

Completeness4/5

Live-session lifecycle is fully covered: start, status, messaging, inbox, update, and stop. Shared sessions cover sharing, listing, searching, loading, commenting, updating, and diff retrieval, but there is no explicit delete/unshare operation and no obvious tool for attaching a diff to a share.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources