React DevTools for agents - This feature is available in the latest Experimental version of React

Experimental Feature

react-devtools-cdt-mcp is experimental. It is built on the experimental third-party developer tools API in Chrome DevTools MCP, and both its tools and their output may change between releases.

react-devtools-cdt-mcp gives AI coding agents the same view of your app that React DevTools gives you: the component tree, props, hooks, owners, source locations, and render timing.

import 'react-devtools-cdt-mcp/register';

Overview

Coding agents that drive a browser through Chrome DevTools MCP can click, take snapshots, and read the DOM, but the DOM doesn’t tell them which component rendered a button, what state it holds, or why an interaction was slow.

react-devtools-cdt-mcp is a small browser library that you import into the page you’re debugging. It registers a group of React tools with the page. When Chrome DevTools MCP connects to that page, it discovers the tools automatically, and your agent can call them like any other MCP tool.

Note

react-devtools-cdt-mcp is not an MCP server, and it doesn’t go in your MCP client config. It runs inside your page. The only MCP server you configure is Chrome DevTools MCP.


Setup

Install the package

Terminal
npm install --save-dev react-devtools-cdt-mcp

Import it before React

Import the register entry point at the very top of your app’s entry file, before anything imports react-dom:

import 'react-devtools-cdt-mcp/register';

import { createRoot } from 'react-dom/client';
import App from './App';

createRoot(document.getElementById('root')).render(<App />);

react-devtools-cdt-mcp has to load before React does. If you import it after React, the tools won’t see your components.

Pitfall

react-devtools-cdt-mcp connects to React the same way the React DevTools extension does, and makes React report every commit to it. This slows down your app, so only include it in development builds.

Set up Chrome DevTools MCP

Your agent needs Chrome DevTools MCP with third-party developer tools enabled. Follow the Chrome DevTools MCP docs to set it up. Once your agent opens a page that imports react-devtools-cdt-mcp/register, it can list and call the React tools.


Try it

You don’t need an agent to see what the tools return. The sandbox below imports react-devtools-cdt-mcp/register exactly as you would in your app, and adds a small tool console under the app. The console discovers the React tools the same way Chrome DevTools MCP does, by dispatching the devtoolstooldiscovery event, and lets you call them by hand.

Pick a tool, edit the JSON parameters, and press Run tool. Here’s a debugging session to follow, playing the agent’s part:

  1. Find a component. Run react_find_components with {"name": "Row"}. Each result has a uid, like "r12", that the other tools accept.
  2. Inspect it. Run react_get_component_by_uid with one of those uids and "includeHooks": true to see its props and hooks.
  3. Start from the screen. Choose react_get_component_by_dom_element, press Pick element, and click a product in the list to get the host component that rendered it.
  4. Profile an interaction. Run react_start_profiling, click Add to cart in the app, then run react_stop_profiling.
  5. See what rendered. Run react_get_trace_overview, then react_get_commit_report for commit 0 to see which components rendered in that commit and how long each one took.
import { useState } from 'react';

const PRODUCTS = Array.from({ length: 20 }, (_, i) =>