sessions-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SESSIONS_MCP_URL | No | Optional URL for a custom backend. Point it at a different backend if you run your own. |
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_recent_sessionsA | List the user's recent agent sessions (Claude Code, Codex) from their private session corpus. Syncs local session logs first, so the list is current. |
| search_my_sessionsA | Semantic search over the user's own agent sessions — matches by MEANING, not just keywords (a query about 'retries' finds a session about 'exponential backoff'), ranked by relevance with a one-line |
| share_sessionA | Mint a public share link for ONE of the user's sessions. Anyone with the link can view it AND pull the full session content into their own agent (it is not just a read-only view) — so this shares the whole transcript. ONLY call this when the user has explicitly asked to share a session (e.g. 'share this with…', 'give me a link'). Never call it proactively; offering is fine, minting requires their yes. The link is revocable via unshare_session. |
| unshare_sessionA | Revoke a session's share link — the link stops working immediately. |
| pull_sessionA | Pull a shared agent session (by share link or token) into the current conversation to continue or build on it. A SHORT session comes back as the full transcript automatically. A LONGER session comes back as a summary + its most recent turns (full=false); when that happens you MUST ask the user whether they want the full transcript before proceeding — do not silently continue on just the summary. If they say yes, call pull_session again with full=true. |
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 5 tools
Each tool targets a distinct operation: listing recent sessions, semantic search, sharing, unsharing, and pulling a shared session. There is no overlap or potential for confusion between them.
All tools follow a consistent verb_noun pattern in snake_case (list_recent_sessions, search_my_sessions, share_session, unshare_session, pull_session). The naming is uniform and predictable.
With only 5 tools, the server is well-scoped and each tool serves a clear purpose within the session management domain. This is within the ideal range.
The tool set covers the full lifecycle of session management: discovering recent sessions, searching them, sharing a session, revoking a share, and pulling a shared session into the current context. There are no obvious gaps for the stated purpose.