Bug reports with the full context already attached — console errors, network requests, interactions, and the screen recording — read straight from your agent, without opening the dashboard. Point it at a domain you've claimed in Session Replay and it can search the reports filed against it, read one in full, pull a still from the recording at the exact moment something failed, and move the report through triage. **Tools** - `list_domains` — the domains this account can rea
Session Replay
Bug reports with the full context already attached — console errors, network requests, interactions, and the screen recording — read straight from your agent, without opening the dashboard. Point it at a domain you've claimed in Session Replay and it can search the reports filed against it, read one in full, pull a still from the recording at the exact moment something failed, and move the report through triage. **Tools** - `list_domains` — the domains this account can read, and why any of them can't yet - `list_reports` — search a domain's reports by text, status, or date range, newest first - `get_report` — one report in full, with repeated console errors collapsed and counted - `get_frame` — a still from the recording at a given offset; the offsets worth asking for are already in the report, on every console error, failed request, and interaction - `set_status` — move a report through triage. The person who filed it is told, so `resolved` tells them their bug is fixed **Befo
| Type | MCP server |
| Section | MCP servers |
| Pricing | free |
| Platform | Command line |
| Systems | cli, api |
| Hosting | cloud |
| Install | mcp |
| Protocols | mcp |
| Site language | en |
| Vendor | info-0q2s |