Skip to main content
Glama
Anjos2

mcp-android-emulator

by Anjos2

Related Servers

Alternatives to mcp-android-emulator

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to read and control a connected Android device over adb or a local root shell, with tools for screen inspection, tapping, typing, swiping, launching apps, and system commands.
      18
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Android devices and emulators through ADB, allowing control actions like tapping, text input, screenshots, UI inspection, and app launching through natural language.
      9 npm
      8
      ISC
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      12
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to see and control Android devices through ADB and screen mirroring, supporting screen capture, touch input, app management, UI element finding, file transfer, shell commands, clipboard access, and audio/video streaming.
      151 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 42 tools

    Disambiguation2/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues