Skip to main content
Glama
Sign In
skylarbarrera

react-devtools-mcp

by skylarbarrera
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to react-devtools-mcp

No user-submitted related servers found.

    Related Servers

    • agent-debug-mcp

      muhsinmozilor
      A
      license
      Not graded
      quality
      A
      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

    • React Context MCP

      uxfreak
      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.
      12 npm
      1
      Apache 2.0

    • react-native-eye

      fregggggo
      A
      license
      B
      quality
      A
      maintenance
      Connects AI agents to a running React Native app so they can see the screen, tap and type, and inspect logs, network traffic, and state without any SDK or code changes. Composite tools let an agent run a whole interaction flow in a single call instead of one round trip per tap.
      35
      5 npm
      2
      MIT

    • Curupira

      drzln
      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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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

    ActivityInactive
    ResponsivenessUnresponsive

    Resources