rn-device-mcp
Related Servers
Alternatives to rn-device-mcp
No user-submitted related servers found.
Related Servers
- 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.2252 npm5MIT
- AlicenseBqualityBmaintenanceEnables AI agents to automate Android and iOS devices, including emulators and physical devices, by capturing screenshots, reading UI accessibility trees, performing touch and text input, and managing app lifecycle and logs.184MIT
- AlicenseAqualityCmaintenanceEnables 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.992 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants and IDEs to drive real Android devices and emulators for cross-app UI automation, testing, and diagnostics, including collecting Logcat output and screenshots.Apache 2.0

Argentofficial
AlicenseAqualityBmaintenanceEnables AI assistants to interact with iOS Simulators and Android Emulators, allowing autonomous app development, UI interaction, profiling, and debugging through natural language.773,195Apache 2.0- AlicenseAqualityDmaintenanceEnables AI agents to build, deploy, drive, and debug Android apps — managing Gradle builds, emulators, adb deployment, logcat capture, and full UI automation.5376 npmMIT
TDQS
Scored across 20 tools
Tools are cleanly partitioned by platform prefix and a distinct action (boot, shutdown, install, launch, terminate, screenshot, logs), so an agent can pick correctly in almost all cases. The only mild overlaps are ios_launch_app vs ios_open_url (cold start vs deep link) and android_dev_menu vs android_input's KEYCODE_MENU keyevent, both of which the descriptions clarify.
A consistent platform_action scheme (ios_*, android_*) with snake_case throughout makes the surface predictable. Minor deviations: list tools use bare nouns (ios_simulators, ios_apps, android_devices, ios_logs, android_logcat) instead of a verb, and the platform sets are asymmetric (ios_boot/ios_shutdown exist, android counterparts do not).
20 tools is on the heavy side for a device-control server, though the count is partly explained by covering two platforms. Several tools are thin one-off wrappers (android_reverse_metro, android_dev_menu) that could arguably be folded into the input/log utilities.
The iOS lifecycle (boot, install, launch, terminate, screenshot, logs, apps) and the Android equivalents are broadly covered with no severe dead ends. Notable gaps: there is no iOS UI interaction tool (no tap/type equivalent to android_input), no way to start/boot an Android emulator, and no uninstall or clear-data operations on either platform.