How to connect Replay MCP to Claude

Connect Claude Web, Desktop and Cowork to Replay MCP. Inspect console errors in replay recordings, trace failed network requests in replay, and more using natural language, with authentication handled for you.

Replay MCP logoReplay MCP
Api Key

Replay MCP is a debugging service for inspecting time-travel browser recordings. It brings console, network, React state, and performance data into one searchable view.

32 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Replay account to Claude via Composio Connect, enabling it to inspect console errors in Replay recordings, trace failed network requests in Replay, review React state at execution points, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Replay MCP with

Connecting Replay to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Replay account

Back in Claude, ask it to connect to Replay or give it any Replay-related task.

For example, ask Claude to:

  • "Inspect console errors in Replay recordings"
  • "Trace failed network requests in Replay"
  • "Review React state at execution points"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Replay account is ready to use.

What is the Replay Claude Connector, and what's possible with it?

The Replay MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Replay account. It provides structured and secure access to browser recordings, source code, runtime behavior, network activity, React state, and performance data, so your agent can investigate errors, trace application behavior, inspect UI state, and identify performance issues on your behalf.

  • Recording investigation: Have your agent review recording overviews, Playwright steps, user interactions, annotations, screenshots, and processing status to understand what happened during a browser session.
  • Error and console debugging: Let the agent inspect console messages, uncaught exceptions, React exceptions, call stacks, execution points, and source lines to trace runtime failures.
  • Application state inspection: Direct your agent to examine React component trees, rendered components, Redux actions, Zustand stores, local storage access, and evaluated expressions at specific execution points.
  • Network and real-time analysis: Instruct your agent to analyze network requests, WebSocket connections, and messages exchanged during a recording to investigate communication problems.
  • Performance analysis: Have your agent run React performance insights, inspect render behavior, calculate execution delays, and profile statements, dependency graphs, or native engine activity.

Troubleshooting

1. Why does Claude not use the Composio connector for Replay?

The connector can show as connected, but Claude must use it in each Replay conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Replay again.

2. Why does Claude show an MCP server error before Replay connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Replay.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Replay.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Replay authorization link not work?

The Composio connector is one server. Your Replay account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Replay connection.
  • Composio creates a fresh Replay authorization link.
  • Open that link in your browser and finish the Replay sign-in.

4. Why do Replay actions fail after they worked before?

The Replay connection can expire or lose permission.

  • Ask Claude to inspect the Replay connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Replay account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Replay.
  • If the action still fails with a permission error, check that the connected account has that permission in Replay itself.

5. How do I switch to a different Replay account?

Claude can manage the Replay connection for you.

  • Ask Claude to disconnect or delete the current Replay account.
  • Ask Claude to connect Replay again.
  • Open the new Composio authorization link for Replay.
  • Sign in with the other Replay account in the browser.
  • After the account connects, ask Claude to retry the Replay task.

6. Why is my Replay connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Replay connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Replay tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Replay.
TOOLS

Supported Tools

Every Replay MCP action and event your agent gets out of the box.

Annotations

Inspect the annotations in a recording.

Consolemessages

Show console API messages (console.

Describepoint

Describes the application state at a code execution point.

Evaluate

Evaluates an expression at a code execution point.

Executiondelay

Computes execution delays for functions based on their source length and the delay before the first breakpoint in each function executes.

Getpointcomponent

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

Getpointlink

Generates an app.

Getstack

Gets the call stack at a code execution point.

Inspectelement

Get size, layout, ancestry and render point information for a DOM element.

Listsources

List the sources in the recording.

Localstorage

Describe all the accesses made to localStorage.

Logpoint

Evaluates an expression at breakpoint hits for a given path and line number.

Networkrequest

Analyze network requests in the recording.

Playwrightsteps

Show all steps taken by Playwright in the recording.

Profilegraph

Profiles dependency graph entry execution between two points in a recording.

Profilesampling

Profiles the native C++ replay engine using stack sampling between two execution points.

Profilestatements

Profiles JS statement execution between two points in a recording.

Reactcomponenttree

Get the structure of the committed/mounted React component tree at a point in time.

Reactexception

Describe any exceptions thrown which caused React to unmount.

Reactperformanceinsights

Run all deterministic React performance checks on a recording and return prioritized findings.

Reactrenders

Analyze React renders in a recording.

Readsource

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

Recordingoverview

Provides a comprehensive overview of a recording: test results, errors, environment info, network activity, React render performance, and suggested next investigation steps.

Reduxactions

Analyze Redux actions in a recording.

Screenshot

Lists all screenshot timestamps in the recording, or fetches a screenshot at a given timestamp.

Searchsources

Search the sources in the recording and see which statements executed.

Tanstackqueries

Analyze TanStack Query (React Query) cache events in a recording.

Uncaughtexception

Describe uncaught exceptions and unhandled promise rejections (runtime errors not caught by try/catch).

Userinteractions

Show all user interactions (clicks and key presses) in the recording.

Warmrecording

Starts processing a recording if needed and reports its status.

Websocketmessages

Inspect the WebSocket connections in a recording and the messages sent and received on them.

Zustandstores

Analyze Zustand stores in a recording.

FAQ

Frequently asked questions

With a standalone Replay MCP server, the agents and LLMs can only access a fixed set of Replay tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Replay and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Replay tools.

Yes, absolutely. You can configure which Replay scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Replay data and credentials are handled as safely as possible.

Start with Replay MCP.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Replay MCP tool your agent needs.Free to start.

Start building