Replay MCP

Endpoint

Hosted endpoint · transport http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

Tools

• ListSources — List all source files in the recording. Supports glob filtering to narrow results.
• ReadSource — Read source code centered on a specific line, annotated with which statements actually executed during the recording.
• SearchSources — Regex search across all source files, with results annotated to show which matches are in code that actually ran.
• ConsoleMessages — View all console log, warn, and error messages from the recording.
• Screenshot — List available screenshot timestamps, or fetch a screenshot at a specific moment showing visual state, mouse position, and recent mouse movements.
• DescribePoint — Describe application state at a specific execution point — variables in scope, code context, and optionally the full dependency chain.
• Evaluate — Evaluate any JavaScript expression at a specific execution point, like running code in the DevTools console at any moment in the recording.
• GetStack — Get the call stack at an execution point — see which functions called which to reach that moment.
• Logpoint — Set a virtual breakpoint at a source location and evaluate an expression at every hit.
• InspectElement — Get size, layout, DOM ancestry, and render information for a DOM element, identified by CSS selector or element reference.
• UncaughtException — Find all uncaught JavaScript exceptions in the recording, with stack traces and execution points.
• ReactException — Find exceptions that caused React to unmount — error boundary triggers, fatal render errors, and similar React-specific crashes.
• NetworkRequest — List all HTTP requests, or get detailed information about a specific request including headers, body, status, and timing.
• LocalStorage — View all localStorage read and write operations that occurred during the recording.
• ReactComponentTree — View the React component hierarchy at any point in the recording.
• GetPointComponent — Identify which React component was being rendered at a specific execution point.
• DescribeComponent — Get the full render history of a named component — every render, its props, and what triggered each render.
• ReactRenders — Multi-mode render analysis tool for understanding React component render behavior and performance.
• DescribeReactRender — Trace a specific render trigger back through the dependency chain to find the root cause, with component render counts.
• PlaywrightSteps — List all steps from a Playwright test with timestamps, stack traces, and error information.
• ProfileStatements — Profile JavaScript statement execution between two points with flat profile and call tree analysis.
• ProfileGraph — Profile dependency graph entries (React fiber renders, effect calls) between two points.
• ExecutionDelay — Analyze per-function execution delays in a source file based on source length and breakpoint timing.
• ProfileSampling — Low-level native engine stack sampling for profiling the Replay runtime itself.
• GetPointLink — Generate a shareable app.replay.io URL for a specific execution point.

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.