Skip to main content

Replay MCP integration

AI utilities connector, available on Zeplik

Replay MCP is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect Replay MCP and Zeplik can act on your AI for you: Replay MCP lets agents inspect time-travel browser recordings, including console output, exceptions, network activity, source code, React state,. You stay in the conversation while the assistant does the work in Replay MCP directly.

Zeplik exposes 7 read actions and 25 write actions for Replay MCP. Read actions run automatically; write actions stay off until you enable write access in Settings, so nothing is changed in Replay MCP without your consent.

Try Replay MCP on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

What Zeplik can do with Replay MCP

Read from Replay MCP (7)

Runs automatically in any conversation.

  • Describe point

    Describes the application state at a code execution point. Shows the containing function with executed/not-executed annotations, variable values, and timestamps. Use dependencyChain=true to trace the full causal chain back to the origin event. Get execution points from other tools (ConsoleMessages, ReactRenders, ReduxActions, Logpoint, etc.).

  • Get point component

    Gets the React component being rendered at a code execution point.

  • Get point link

    Generates an app.replay.io link for users to inspect a given execution point.

  • Get stack

    Gets the call stack at a code execution point. Use to understand execution context. Pair with DescribePoint for full state.

  • List sources

    List the sources in the recording.

  • Read source

    Read up to 50 lines of code centered around the given line and see what statements executed.

  • Search sources

    Search the sources in the recording and see which statements executed. Note: Playwright test runner code runs in Node outside the browser recording and won't appear here. Use PlaywrightSteps(mode: test-source) for Playwright test source.

Act in Replay MCP (25)

Runs only after you enable write access.

  • Annotations

    Inspect the annotations in a recording. Annotations are timestamped records attached by the runtime and integrations (e.g. Cypress, Playwright, React DevTools, network, localStorage). Call with no arguments to list all annotation kinds in the recording with their counts. Pass a 'kind' to return the annotation data for that kind (paginated, optionally filtered by text). For WebSocket traffic (DOMWebSocket annotations), use the WebSocketMessages tool instead.

  • Console messages

    Show console API messages (console.log, console.warn, console.error, etc.). Note: console errors are distinct from runtime exceptions — use UncaughtException and ReactException for those. Start with mode 'summary' for an overview with message counts and the last errors/warnings. Use 'messages' to browse the full paginated list (filter by level, text, node_modules visibility). Use 'message-detail' with a point reference for full detail on a single message including stack trace. Call RecordingOverview first for broader context.

  • Evaluate

    Evaluates an expression at a code execution point. Use for ad-hoc value inspection beyond what DescribePoint shows. Expressions must be synchronous and immediately inspectable. Do not use async functions or promises; replay cannot inspect their eventual results. Defaults to frame scope; use global scope explicitly when needed. String results are returned in full up to maxStringLength characters (default 100000); longer strings end with a truncation notice giving the stringOffset to read the next part. String results longer than about 8,000 characters are read by evaluating the expression a second time, so use a single, side-effect-free expression to get the full text.

  • Execution delay

    Computes execution delays for functions based on their source length and the delay before the first breakpoint in each function executes. Each breakpoint is attributed to the innermost function covering it, and each function's weight is computed as its source length minus the sum of its children's lengths.

  • Inspect element

    Get size, layout, ancestry and render point information for a DOM element. Find relevant code before inspecting elements. Only use this tool sparingly — expensive, requires full DOM layout computation. Prefer ReactComponentTree for component structure.

  • Local storage

    Describe all the accesses made to localStorage. Start with mode 'summary' (default) for a grouped overview: keys with access counts, final values, and timing. Use 'operations' to browse the full chronological access list with pagination. Use keyFilter to narrow by key name (substring match). For large apps, consider filtering by key pattern in results.

  • Logpoint

    Evaluates an expression at breakpoint hits for a given path and line number. Returns up to 20 hits with their expression evaluation results. Use beginPoint/endPoint to narrow the range. Use column to target a specific statement on the line. Find source paths with ListSources or SearchSources first.

  • Network request

    Analyze network requests in the recording. Start with mode 'summary' (default) for high-level stats: total count, failed/slow counts, status code distribution, and top domains. Use 'requests' to browse a paginated table of all requests (filterable by urlFilter, startTime, endTime). Use 'detail' with requestId (from the ID column in the 'requests' table) for full request/response headers, body content, event timeline, and backend function analysis. RECOMMENDED workflow: summary → requests → detail. Call RecordingOverview first for broader context about the recording.

  • Playwright steps

    Show all steps taken by Playwright in the recording. Start with mode 'summary' for a test overview with pass/fail status and duration. Use 'steps' with testIndex to see the step list for a specific test (get indices from 'summary'). Use 'step-detail' with stepNumber for inspector protocol commands of a single step (get step numbers from 'steps'). Use 'test-source' with testIndex to read the test source code. For failed tests, use failedOnly=true in 'steps' mode to focus on failures. Call RecordingOverview first for broader context.

  • Profile graph

    Profiles dependency graph entry execution between two points in a recording. Enumerates all dependency graph entries including React fiber renders and effect calls, computes the execution associated with each by progress counter differences, traces each entry back to its source via the dependency chain, and groups results by source ordered by execution amount.

  • Profile sampling

    Profiles the native C++ replay engine using stack sampling between two execution points. Runs the replay engine from the begin point to the end point while collecting periodic stack samples, then analyzes the samples to produce a flat profile of where time is spent in native code.

  • Profile statements

    Profiles JS statement execution between two points in a recording. Fetches all breakpoint hits between the points, breaks them down by function, resolves function names, and computes a flat profile and call tree showing statement hits per function and its callees.

and 13 more.

How to connect Replay MCP

  1. Sign in to Zeplik

    Create a free Zeplik account or sign in. New accounts start with free credits, so you can try Replay MCP immediately.

  2. Connect Replay MCP

    Open Settings and go to Connectors, then press Connect on Replay MCP. You can also connect from the Replay MCP page in the app.

  3. Add your Replay MCP API key

    Paste your Replay MCP API key when prompted. Zeplik stores it securely on the server and starts working with Replay MCP right away.

Frequently asked questions

Can I use Replay MCP with Zeplik?
Yes. Replay MCP is available as an integration on Zeplik. Connect it once and the AI assistant can work with your Replay MCP account inside any conversation.
What can Zeplik do with Replay MCP?
Once connected, Zeplik has 7 read and 25 write actions for Replay MCP. Replay MCP lets agents inspect time-travel browser recordings, including console output, exceptions, network activity, source code, React state,.
How do I connect Replay MCP to Zeplik?
You connect Replay MCP by pasting your own Replay MCP API key in Settings under Connectors. There is no separate app to install.
Does Zeplik change things in Replay MCP without asking?
No. Zeplik reads from Replay MCP by default. Any action that changes data in Replay MCP requires write access, which stays off until you enable it in Settings under Connectors.
How much does connecting Replay MCP cost?
Connecting Replay MCP is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.

Related ai utilities integrations

More on Zeplik

Connect Replay MCP to your AI assistant

Every model, one chat. Bring Replay MCP into Zeplik and let the assistant do the work.