expo-headless-mcp
Related Servers
Alternatives to expo-headless-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLets 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 npm1MIT
- AlicenseBqualityDmaintenanceEnables AI agents to inspect, log, and control React Native apps on Android emulators or iOS simulators, including UI tree, tap, scroll, and hot reload.2291 npm5MIT
- AlicenseBqualityCmaintenanceEnables 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.20MIT
- AlicenseBqualityBmaintenanceConnects 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.357 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables automated testing and development of Expo/React Native apps through session-based Expo dev server management and Maestro UI automation tools for tapping, text input, screenshots, and flow execution.257,722 npm5MIT
- AlicenseBqualityBmaintenanceEnables agents and LLMs to automate and develop native iOS and Android apps across simulators, emulators, and real devices through a single platform-agnostic, accessibility-first interface. Provides taps, swipes, text input, app install/launch, screenshots, screen recording, device logs, and crash reports without requiring any iOS- or Android-specific expertise.3549,881 npmApache 2.0
TDQS
Scored across 9 tools
Each tool targets a distinct action: refresh (bundled screenshot), click, type, scroll, describe, press_key, auto_test, use_target, device_list. The only mild overlap is between auto_test and refresh_screen (both reload and capture) and between device_list and use_target (both deal with devices), but descriptions clearly delineate the read-only listing vs. target selection and the exhaustive automated pass vs. manual re-capture.
Eight of nine names use a verb_noun pattern with predictable suffixes (_screen, _text, _key) and a clear action-first style (refresh_screen, click_screen, scroll_screen, describe_screen). The outlier is device_list, which inverts to noun_verb and breaks the otherwise uniform convention.
Nine tools is well within the ideal 3-15 range and each earns its place: a coherent interaction loop (refresh/describe/click/type/scroll/press_key) plus higher-level automation (auto_test) and environment setup (use_target, device_list). No redundancy or padding.
The surface covers the essential test lifecycle: render, inspect, interact (tap/type/scroll/key), automate, and choose headless vs. device targets. Minor gaps remain—no drag/swipe/pinch gesture tool, no standalone console-log retrieval outside auto_test, and no explicit wait/idle primitive—but these are workaroundable.