Agents and MCP

Reel exposes an MCP server at /mcp on your deployment. Its three tools let a coding agent search recording sessions, read a session's privacy-filtered content, and hand you a link to watch it. All three are read-only: an agent cannot protect, delete or erase anything through MCP.

Reaching the tools

Reel's MCP server uses delegated access: your agent reaches it through the Scalpels MCP server, as you, with your role on the team. Install the Scalpels MCP server and create a token with the Call installed apps ability, as described in Use Scalpels from your agent. Your agent can then list the MCP-enabled products your team runs, pick your Reel deployment, and call its tools.

The call and its answer pass through Scalpels on the way, which means replay content you ask for passes through Scalpels' memory. See What passes through Scalpels for what Scalpels does and does not keep.

Every tool takes application, the application ID shown on the application's settings page in Reel.

sessions

Searches one application's sessions with the same filters as the Sessions screen. Results are newest first.

Optional arguments: started_from, started_to, ended_from, ended_to (dates), duration_min, duration_max (seconds), path, session_id, user_id, release, status, marker, protected and watched (yes or no), limit (1 to 100, default 25) and cursor.

Each session in the answer includes its ID, start and end, duration, first and latest path, application user ID, release ID, status, whether it is protected and complete, and up to ten error markers with method, path and status. When there are more results, pass the returned next_cursor back as cursor.

session_content

Reads the recorded events of one session, in pages. Arguments: application, session_id, types (any of dom, click, scroll and error; all four by default), limit (1 to 100 events, default 25) and cursor.

The content is the same sanitised data the player uses: DOM snapshots and changes, clicks, scrolls and 5xx markers. A single large event, such as a full page snapshot, may come back split into base64 fragments across several pages. If the replay cannot be read, for example because the session is not yet Ready, the answer carries a diagnostic instead of events.

session_deep_link

Creates a signed link to the replay player for one session, optionally starting at start milliseconds. The link expires after five minutes, and opening it still requires signing in to Reel. Use it when you want the agent to point you at the exact moment to watch.

Example prompts

Find sessions in the checkout app from the last hour that hit a server error, and tell me what the user clicked just before it.

Give me a link to watch the session where /orders returned a 500 this morning.