Skip to main content
Glama
twodoorsdev

React Native Debugger MCP

by twodoorsdev

Related Servers

Alternatives to React Native Debugger MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A plugin-based MCP server for React Native runtime debugging, inspection, and automation via Chrome DevTools Protocol. Works with Expo, bare React Native, and any Metro + Hermes project without app code changes.
      665 npm
      81
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables real-time debugging and inspection of running React Native apps, providing access to console logs, errors, network requests, navigation state, storage, and performance profiling.
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      An MCP server that gives AI agents hands-on control of a live React Native app, enabling UI taps, screenshots, UI/component trees, native logs, and JS/React profiling to debug, verify fixes, and diagnose performance issues.
      16
      2 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for Android's Tasker automation app
      50
      MIT

    TDQS

    B3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one retrieves a list of connected apps, while the other reads console logs from a specific app. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the task.

    Naming Consistency4/5

    The tool names follow a consistent verb_noun pattern (getConnectedApps, readConsoleLogsFromApp), with both using camelCase. However, the second tool name is quite long and descriptive, which slightly deviates from the simplicity of the first, but the overall naming convention is clear and predictable.

    Tool Count2/5

    With only two tools, the server feels thin for a React Native debugger domain, which typically involves more operations like inspecting elements, setting breakpoints, or managing app state. This limited set may not cover essential debugging workflows, indicating an under-scoped tool surface.

    Completeness2/5

    The tool set is severely incomplete for a debugger server. It lacks basic debugging operations such as inspecting app components, setting breakpoints, evaluating expressions, or controlling app execution. This creates significant gaps that will likely cause agent failures in comprehensive debugging tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues