mcp-android-emulator
Related Servers
Alternatives to mcp-android-emulator
No user-submitted related servers found.
Related Servers
- FlicenseBqualityCmaintenanceEnables AI assistants to observe, reason about, and control connected Android devices via ADB, providing tools for screenshots, UI hierarchy parsing, semantic element clicking, gestures, text input, and app lifecycle management.13-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Android devices and emulators through ADB, allowing control actions like tapping, text input, screenshots, UI inspection, and app launching through natural language.13 npm8ISC
- AlicenseAqualityCmaintenanceEnables AI agents to control, inspect, and automate Android devices, Waydroid containers, and AVD emulators over ADB. Provides tools for screenshots, UI-hierarchy text-based tapping, gestures, key presses, text input, app management, and raw shell commands.12MIT
- AlicenseAqualityDmaintenanceEnables AI models to control Android devices via ADB through natural language commands, supporting screen analysis and automated actions.331 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to control Android TV/Android devices through ADB, including screen capture, remote control, app management, and more.245 npm1MIT
- AlicenseBqualityCmaintenanceEnables AI agents to control the Android Emulator through adb, including booting AVDs, installing and managing apps, interacting with the UI, taking screenshots, reading logs, and more.37MIT
TDQS
Scored across 42 tools
There is heavy overlap among tap-related tools (tap, tap_text, tap_safe, tap_element, double_tap, multi_tap, long_press) and gesture tools (swipe, scroll, drag, scroll_to_text), making it easy for an agent to select the wrong one. UI inspection tools like get_ui_tree, get_clickable_elements, and get_all_text also have unclear boundaries despite their descriptions.
The vast majority of tools follow a clear snake_case verb_noun pattern such as get_ui_tree, launch_app, and force_stop. A few exceptions like screenshot and device_info break the pattern, but the overall convention is still predictable and readable.
42 tools is well above the threshold for a cohesive tool set. Many tools are minor variations of core actions—especially taps, gestures, and UI querying—so the count feels bloated rather than carefully scoped.
The tool set covers the core Android emulator workflow well: app lifecycle management, UI interaction, waiting/assertions, clipboard, logs, orientation, and keyboard handling. It is missing a few obvious operations like uninstalling an app, but agents can generally complete common automation tasks without dead ends.