Skip to main content
Glama

Related Servers

Alternatives to react-native-eye

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables an AI to see and operate an Expo / React Native app without an emulator, phone, or browser using real screenshots, taps, typing, scrolling, and automated bug hunting, with optional Android and iOS device control.
      9
      376 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables coding assistants to drive iOS Simulators and Android emulators or USB devices for React Native and Expo work, including taking screenshots, reading app and device logs, opening deep links, installing builds, and launching or relaunching apps. It also supports Android-specific actions such as adb reverse for Metro, opening the dev menu, and tapping or typing on screen.
      20
      MIT
    • A
      license
      C
      quality
      F
      maintenance
      Provides AI agents with visibility into React applications by exposing tools to inspect component state, props, and performance metrics. It enables debugging and state analysis for both web and React Native applications through the Model Context Protocol.
      45
      4 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables agents and LLMs to automate, inspect, and scrape native iOS and Android apps across simulators, emulators, and real devices through a platform-agnostic interface using accessibility snapshots or screenshot-based coordinates. It provides device, app, screen, input, log, and crash management tools, including optional cloud device reservation.
      34
      55,275 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets MCP-capable AI agents control an Expo / React Native app running live in Expo Go on a real phone, reading a compact token-cheap outline of the visible screen and performing taps, text entry, scrolling, toggles and navigation. Also exposes screenshots, layout, console logs, network requests and hardware keys, and attaches new JS errors and failed requests to the action that caused them.
      107 npm
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 35 tools

    Disambiguation4/5

    Most tools target distinct resources or actions, but several composite tools intentionally overlap with atomic tools: observe vs screenshot/get_layout/get_logs, check_state vs get_state/navigate, and run_flow vs tap/type_text/swipe/eval_js. Descriptions explicitly recommend the composite tools, which keeps selection mostly clear, though press_key 'back' and navigate 'back' also overlap.

    Naming Consistency4/5

    Names consistently use snake_case and are mostly verb-first (list_devices, get_logs, type_text, profile_js). Minor deviations are single-word operational verbs such as tap, swipe, connect, and navigate, plus the noun 'screenshot', but the overall convention remains readable.

    Tool Count2/5

    With 35 tools, the surface is well beyond a tightly scoped 3–15 range and past the 16–25 'heavy' bracket. Although the server spans many React Native debugging domains, the large number of atomic plus composite tools makes the selection surface excessive for an agent.

    Completeness4/5

    Coverage is broad: device/app management, targets, logs/errors/network, eval and background jobs, state/component tree, OCR/layout/tap/type/swipe, navigation/flows, recording, and performance profiling. Minor gaps remain around explicit app terminate/uninstall and standalone wait/assert helpers, but launch_app terminate_running and run_flow provide workarounds.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing