Skip to main content
Glama
playwright-react-debug-mcp

playwright-react-debug-mcp

Related Servers

Alternatives to playwright-react-debug-mcp

No user-submitted related servers found.

    Related 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
      C
      maintenance
      Enables AI agents to inspect a running React application’s live Redux state, browser storage, current route, and recent HTTP activity through a local, read-only connection.
      272 npm
      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.
      17 npm
      1
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to inspect and control a live Chromium browser for frontend debugging, providing console logs, network requests, DOM snapshots, and accessibility analysis.
      19
      3 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time debugging, code quality monitoring, and performance insights for React/Next.js applications with features including Chrome DevTools integration, breakpoint management, complexity analysis, and live error streaming.
      17 npm
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 39 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with browser actions, network/console inspection, and React state inspection well separated. However, similar tools like find_component and collect_component_instances, or get_dom and get_react_tree, could cause some misselection despite descriptive help.

    Naming Consistency5/5

    All tool names use snake_case and follow a consistent verb_noun pattern, with action verbs like navigate, click, fill, and get_* for inspections, clear_* for resets, and find_*/collect_*/detect_* for specific operations. No mixing of conventions.

    Tool Count2/5

    39 tools is well beyond the typical well-scoped range and even exceeds the 25+ threshold for 'too many'. While the broad scope of a Playwright and React debugger justifies some depth, this many tools feels heavy and could overwhelm an agent.

    Completeness5/5

    The tool set covers the full debugging lifecycle: navigation, interaction, DOM inspection, React component state and tree, multiple state management libraries (Zustand, Redux, React Query), performance monitoring, error detection, hydration mismatch, and accessibility audits. No obvious dead ends or missing critical operations for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues