Session Replay
Bug reports with the full context already attached — console errors, network requests, interactions, and the screen recording — read straight from your agent…
What it can do
- List Domains: Every domain this account has claimed, with the team it belongs to and whether it has been verified. A domain that cannot be read yet is listed and says why.
- List Reports: Bug reports filed against a domain this account has claimed and verified, newest first. One page at a time: the answer says how many matched in total, how many it carries, and the offset
- Get Report: One report in full: what page it was filed on, how long the capture ran, where it stands, and the console, network and interaction logs, with repeated console errors collapsed into one ent
What data it sees
Do you need an account
No: the server works without sign-in
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 yetlist_reports— search a domain's reports by text, status, or date range, newest firstget_report— one report in full, with repeated console errors collapsed and countedget_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 interactionset_status— move a report through triage. The person who filed it is told, soresolvedtells them their bug is fixed
Before you connect
You'll need a Session Replay account with the domain claimed and verified, and a Professional plan — the server refuses tools on lower tiers and names the plan in the refusal. Sign-in is OAuth; nothing to paste, no API key.
Server tool list (5)
Raw names from tools/list. Only developers need these.
| list_domains | Every domain this account has claimed, with the team it belongs to and whether it has been verified. A domain that cannot be read yet is listed and says why. |
| list_reports | Bug reports filed against a domain this account has claimed and verified, newest first. One page at a time: the answer says how many matched in total, how many it carries, and the offset that reaches the next page. Each row is a summary - enough to choose one; get_report has the rest of it. |
| get_report | One report in full: what page it was filed on, how long the capture ran, where it stands, and the console, network and interaction logs, with repeated console errors collapsed into one entry carrying a count. |
| get_frame | A single frame from the screen recording at a moment you name. The offsets worth asking for are in the report already: console errors, failed requests and interactions all carry one. |
| set_status | Set where a report stands. The person who filed it sees every status change, so resolved tells them their bug is fixed. Answers with the token, where the report now stands and when it was resolved - not the report itself, which get_report has. |