Skip to main content
Glama
react-devtools-mcp

react-devtools-mcp

react-devtools-bridge

Give AI agents eyes into your React app.

Setup

1. Add MCP server to Claude Code

.mcp.json:

{
  "mcpServers": {
    "react-devtools": {
      "command": "npx",
      "args": ["react-devtools-bridge"]
    }
  }
}

2. Connect your React app

Web - Add to your HTML (before your app bundle):

<script src="http://localhost:8097"></script>

React Native - DevTools is built-in. No extra setup needed.

3. (Optional) Install the skill

Teach Claude when to use these tools:

npx add-skill skylarbarrera/react-devtools-mcp

Or manually:

cp node_modules/react-devtools-bridge/SKILL.md ~/.claude/skills/react-devtools/SKILL.md

Related MCP server: playwright-react-debug-mcp

Usage

With your React app running, ask Claude things like:

  • "What's the current state of the Counter component?"

  • "Why doesn't clicking this button update the UI?"

  • "Which components are re-rendering too often?"

Docs

License

MIT

Available Tools

45 tools
capture_screenshotC

Capture screenshot of an element (if supported)

Inputs: id (required).

clear_errors_and_warningsC

Clear all or specific element's errors/warnings

Inputs: id, clearErrors, clearWarnings.

clear_highlightB

Clear any active element highlight

Inputs: no named parameters.

connectC

Connect to React DevTools backend via WebSocket

Inputs: host, port, timeout.

delete_pathC

Delete a path from props/state/hooks/context

Inputs: id (required), target (required), path (required), hookIndex.

disconnectB

Disconnect from React DevTools backend

Inputs: no named parameters.

get_capabilitiesB

Get negotiated protocol capabilities (features supported by backend)

Inputs: no named parameters.

get_component_filtersC

Get current component filters

Inputs: no named parameters.

get_component_treeC

Get the React component tree for all roots

Inputs: rootID, maxDepth.

get_connection_statusC

Get current connection status

Inputs: no named parameters.

get_element_by_idC

Get basic element info by ID

Inputs: id (required).

get_elements_by_rendererC

Get all elements for a specific renderer

Inputs: rendererID (required).

get_element_sourceC

Get source location for an element

Inputs: id (required).

get_errors_and_warningsC

Get all errors and warnings from components

Inputs: no named parameters.

get_inspecting_native_statusB

Check if native inspection mode is active

Inputs: no named parameters.

get_native_styleC

Get native style and layout info (React Native only)

Inputs: id (required).

get_owners_listC

Get the chain of components that rendered this element

Inputs: id (required).

get_profiling_dataC

Get profiling data without stopping

Inputs: no named parameters.

get_profiling_statusB

Check if profiling is active

Inputs: no named parameters.

get_rendererC

Get a specific renderer by ID

Inputs: id (required).

get_renderersB

Get all connected React renderers (for multi-renderer apps)

Inputs: no named parameters.

health_checkB

Get server and connection health status

Inputs: no named parameters.

highlight_elementC

Highlight an element in the app UI

Inputs: id (required), duration.

inspect_elementB

Get full inspection data for a component including props, state, hooks

Inputs: id (required), paths.

log_to_consoleC

Log an element to the browser/app console as $r

Inputs: id (required).

override_contextC

Override a context value

Inputs: id (required), path (required), value (required).

override_hooksC

Override a hook value on a function component

Inputs: id (required), hookIndex (required), path (required), value (required).

override_propsC

Override a prop value on a component

Inputs: id (required), path (required), value (required).

override_stateC

Override a state value on a class component

Inputs: id (required), path (required), value (required).

rename_pathC

Rename a key in props/state/hooks/context

Inputs: id (required), target (required), path (required), oldKey (required), +2 more.

save_to_clipboardC

Save content to system clipboard

Inputs: value (required).

scroll_to_elementC

Scroll the app to show an element

Inputs: id (required).

search_componentsC

Search for components by name

Inputs: query (required), caseSensitive, isRegex.

set_component_filtersC

Set component filters (hide certain components)

Inputs: filters (required).

set_native_styleC

Set a native style property (React Native only)

Inputs: id (required), property (required), value (required).

set_trace_updates_enabledC

Enable/disable visual update highlighting

Inputs: enabled (required).

start_inspecting_nativeB

Start native element inspection mode (tap-to-select)

Inputs: no named parameters.

start_profilingC

Start profiling React renders

Inputs: recordTimeline, recordChangeDescriptions.

stop_inspecting_nativeC

Stop native element inspection mode

Inputs: selectNextElement.

stop_profilingC

Stop profiling and get data

Inputs: no named parameters.

store_as_globalC

Store a value as a global variable for console access

Inputs: id (required), path (required), globalName (required).

toggle_errorC

Toggle error boundary state for testing

Inputs: id (required), isErrored (required).

toggle_suspenseC

Toggle suspense state for testing

Inputs: id (required), isSuspended (required).

view_attribute_sourceC

Get source location for a specific attribute path

Inputs: id (required), path (required).

view_sourceC

Open element source in IDE (if supported)

Inputs: id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 45 tools

    Disambiguation3/5

    The tools cover distinct operations like connection management, inspection, and overrides, but there is some overlap in purpose. For example, 'get_element_by_id' and 'inspect_element' both retrieve element info, and 'get_profiling_data' vs 'stop_profiling' could cause confusion. Descriptions help differentiate, but the high count increases ambiguity.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (e.g., 'capture_screenshot', 'clear_errors_and_warnings'), with consistent snake_case throughout. Minor deviations exist, such as 'log_to_console' using 'to' instead of a direct verb, but overall naming is predictable and readable.

    Tool Count2/5

    With 45 tools, the count is excessive for a React DevTools server, making it heavy and potentially overwhelming. While the domain is broad, many tools could be consolidated or omitted without losing functionality, indicating poor scoping.

    Completeness5/5

    The tool set provides comprehensive coverage for React DevTools operations, including connection management, component inspection, profiling, overrides, and debugging features. There are no obvious gaps; it supports full CRUD-like actions and lifecycle management for the domain.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to debug frontend applications by providing direct access to browser DevTools, React state, DOM inspection, and runtime debugging capabilities. Bridges the gap between AI and complex web applications for autonomous debugging and issue resolution.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to inspect React component trees, props, state, and source locations in Chrome, facilitating UI debugging and analysis.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes the React DevTools and TanStack Query/Router state of a Chrome tab to coding agents as MCP tools, enabling inspection, profiling, and mutation of components, queries, and routes from any MCP client.
      1
      MIT