claude-replay
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_REPLAY_DB | No | Location of the SQLite store. | ~/.claude-replay/sessions.db |
| CLAUDE_SESSION_ID | No | Session identity, falls back to CLAUDE_CODE_SESSION_ID or hash of project directory. | |
| CLAUDE_CODE_SESSION_ID | No | Alternative session identity env var. | |
| CLAUDE_REPLAY_CORS_ORIGIN | No | Comma-separated extra CORS origins for the server. | localhost only |
| CLAUDE_REPLAY_NO_DASHBOARD | No | Set to disable the static dashboard mount (MCP/JSON only). |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| replay_statusA | Current session summary: objective, status, checkpoint/event counts, last activity. |
| replay_checkpointC | Force a checkpoint of the current session right now, with an optional note. |
| replay_resumeA | Generate a structured resume brief for a session (default: the most recent). Paste the result into a new Claude Code session to continue where it left off. |
| replay_sessionsB | List recent sessions with status, model, duration, and checkpoint count. |
| replay_exportA | Render a session as a self-contained trace (html, json, or md) and return the output path. |
| replay_searchA | Full-text search across recorded sessions (event payloads, objective, name, and tags), with optional filters. Ranked by match count. Omit the query to browse by filters alone. |
| replay_tagB | Name or tag a session for later retrieval. Sets a name and/or adds/removes tags on a session (default: the most recent). |
| replay_insightsC | Per-session insight metrics: how it ended, duration, tool-call count, error count/rate, files touched, and the most-used tools. |
| replay_diffA | Compare two sessions side by side: metric deltas (tool calls, errors, duration, files) and which files each touched. |
| replay_statsA | Cross-session analytics across all recorded sessions: total tool calls, overall error rate, why sessions end (death-cause breakdown), the tool mix, and per-project rollups. Optional limit / project filter. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/constripacity/Claude-Replay'
If you have feedback or need assistance with the MCP directory API, please join our Discord server