
Agent Replay MCP
- Updated April 24, 2026
- mdfifty50-boop/agent-replay-mcp
Agent Replay is an MCP server that records and replays AI agent execution so builders can debug tool workflows reproducibly.
About
Agent Replay is an MCP server that records and replays AI agent execution for debugging. developers shipping agent-driven features often cannot reproduce what went wrong: the model answered differently, tools returned new data, or the client dropped messages. Replay gives you a deterministic way to walk through a captured session again inside your MCP-aware workflow. That is especially valuable when you iterate on prompts, tool schemas, or multi-step automations in Claude Code or Cursor and need evidence, not screenshots. The server ships as agent-replay-mcp on npm at version 0.1.1 with stdio transport—typical for local MCP setups. It is a developer-tooling integration, not a hosted APM product; you still own storage and retention of recordings. Pair it with observability or security MCP servers when you need cost metrics or threat scans on the same runs.
- Record AI agent execution for later inspection
- Replay captured runs to reproduce bugs without guessing
- Stdio MCP server via npm package agent-replay-mcp v0.1.1
- Complements Agent Guard and Agent Security in the same maintainer suite
- Local stdio transport suited to dev-machine debugging
Agent Replay MCP by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
claude mcp add agent-replay-mcp -- npx -y agent-replay-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | agent-replay-mcp |
|---|---|
| Transport | STDIO |
| Auth | None |
| Last updated | April 24, 2026 |
| Repository | mdfifty50-boop/agent-replay-mcp ↗ |
What it does
Record and replay full agent execution traces so you can debug flaky tool chains without re-running expensive LLM steps blind.
Who is it for?
Best when you're debugging multi-step MCP tool chains and need session capture and replay machine.
Skip if: Skip if you only need aggregate metrics or security scans without step-level execution history.
What you get
After registering agent-replay-mcp, you can capture agent runs and replay them to isolate bugs without repeated full autonomous retries.
- MCP-accessible record and replay workflow for agent sessions
- Reproducible execution traces for local debugging
- npm-based install (agent-replay-mcp 0.1.1)
By the numbers
- Server version 0.1.1
- npm package identifier agent-replay-mcp
- stdio MCP transport
README.md
agent-replay-mcp
MCP server for agent session recording and replay — debug non-deterministic agent behavior with session comparison and divergence detection.
Record every action an agent takes, replay sessions step by step, diff two runs to find behavioral regressions, and pinpoint exactly where an agent diverged from expected output.
Install
npx agent-replay-mcp
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"agent-replay": {
"command": "npx",
"args": ["agent-replay-mcp"]
}
}
}
From source
git clone https://github.com/mdfifty50-boop/agent-replay-mcp.git
cd agent-replay-mcp
npm install
node src/index.js
Tools
record_session
Start recording all actions for an agent session.
| Param | Type | Default | Description |
|---|---|---|---|
agent_id |
string | required | Unique agent identifier |
metadata |
object | {} |
Optional metadata (task, model, environment) |
Returns a session_id for use with other tools.
stop_recording
Stop recording and return a session summary.
| Param | Type | Description |
|---|---|---|
session_id |
string | Session ID from record_session |
Returns: action count, total duration, action type breakdown.
log_action
Log a single action during a recording session.
| Param | Type | Default | Description |
|---|---|---|---|
session_id |
string | required | Active session ID |
action_type |
string | required | Type (tool_call, llm_response, decision, error) |
input |
any | required | Input to the action |
output |
any | required | Output from the action |
reasoning |
string | "" |
Agent reasoning for this step |
duration_ms |
number | 0 |
Action duration in milliseconds |
replay_session
Replay a recorded session step by step with full action detail.
| Param | Type | Description |
|---|---|---|
session_id |
string | Session ID to replay |
Returns: complete action sequence with timing, reasoning, inputs, and outputs.
compare_sessions
Behavioral diff between two sessions. Aligns actions by step index and highlights differences.
| Param | Type | Description |
|---|---|---|
session_id_1 |
string | First session |
session_id_2 |
string | Second session |
Returns: similarity ratio, identical/divergent step counts, first divergence step, and per-step diffs.
find_divergence_point
Find where an agent first deviated from expected output.
| Param | Type | Description |
|---|---|---|
session_id |
string | Session to analyze |
expected_output |
any | Expected final output, or array of per-step expected outputs |
If expected_output is an array, compares step by step. If a single value, finds the last matching output and flags the next step as the divergence point.
export_session
Export a session for sharing and offline analysis.
| Param | Type | Default | Description |
|---|---|---|---|
session_id |
string | required | Session to export |
format |
string | "json" |
"json" or "markdown" |
Markdown format produces a readable transcript with step headers, reasoning, and code blocks.
Resources
| URI | Description |
|---|---|
agent-replay://sessions |
All recorded sessions with status and action counts |
Usage Pattern
1. record_session — start recording at agent launch
2. For each agent action:
- log_action — capture input, output, reasoning, timing
3. stop_recording — finalize the session
4. Debug:
- replay_session — review what happened step by step
- compare_sessions — diff today's run vs yesterday's
- find_divergence_point — pinpoint where it went wrong
5. Share:
- export_session — JSON for tooling, markdown for humans
Tests
npm test
License
MIT
Recommended MCP Servers
How it compares
Session record-and-replay MCP tool, not a production metrics dashboard or guardrail enforcer.
FAQ
Who is Agent Replay MCP for?
Developers and developers using MCP agents who need to save and replay autonomous sessions when debugging integrations or flaky tools.
When should I use Agent Replay MCP?
Use it when an agent workflow fails intermittently, when you refactor tools, or when you want teammates to step through the same captured run.
How do I add Agent Replay MCP to my agent?
Install agent-replay-mcp (v0.1.1) from npm, add it as a stdio MCP server in your client configuration, and invoke record/replay tools from agent debugging sessions.