session-relay
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RELAY_TOKEN | No | Personal access token (srk_...) from Settings → Tokens. Optional, used with RELAY_SERVER. | |
| RELAY_SERVER | No | URL of your team's Session Relay server, e.g. https://relay.your-team.com. Optional. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sessionsA | List sessions teammates have shared. Defaults to the current repo; pass all_repos to see everything. for_me lists handoffs assigned to you (from any repo). |
| search_sessionsA | Full-text search over shared sessions (titles, summaries, messages). The query can include "file:" and "branch:" filters. |
| get_sessionA | Load a shared session as a handoff: summary, decisions, next steps, files and conversation. mode "tail" (default) = summary + recent messages; "summary" = summary only; "full" = full transcript, paged with offset. |
| share_current_sessionA | Share the session you are in right now with the team. Write the summary yourself from the conversation: it is what teammates read first. Never include secrets. |
| get_session_diffA | The uncommitted changes a teammate attached to a shared session, as a unified diff. Use it to see exact code state; to apply it, write it to a file and run |
| share_templateA | The handoff template for the current repo: extra sections (some required) and instructions to follow when sharing. Call it before share_current_session. |
| team_activityB | What the team did recently: new shares by repo, handoffs for you, who picked up what, and new comments. |
| comment_on_sessionA | Leave a short note on a shared session for the team: a question, a finding, or that you picked it up. Never include secrets. |
| update_sessionA | Change a share you made (or any share, if you're an admin): title, summary fields, who it's for, the PR link or visibility. Summary lists you pass replace the old ones; use add_next to append next steps. |
| start_liveA | Start working live in this repo: teammates see what you're working on and which files you touch, and their messages reach you between steps. Lists who else is live here. |
| live_statusA | Who is working live right now: repo, branch, what they're doing, files they touched recently, and whether this session is live. |
| send_live_messageA | Send a short message to a teammate who is working live: it reaches their agent between steps. Use it to tell them about a change that affects them, ask a question, or answer theirs. Never include secrets. |
| check_live_inboxA | Take new messages from teammates sent to this live session (they are marked as read). |
| update_liveA | Change what teammates see about this live session (title, current status), or whether this agent may act on their messages without asking. |
| stop_liveA | End this session's live session: teammates stop seeing it and messages stop arriving. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
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.
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.
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.
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.