Skip to main content
Glama

Related Servers

Alternatives to android-phone-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with Android devices and emulators via ADB, providing tools for screenshots, UI inspection, touch and text input, app management, and device control.
      42
      204 npm
      21
      MIT
    • 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
      2
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact with Android devices through UI manipulation, screen capture, touch gestures, text input, and app management via ADB. Provides comprehensive mobile automation capabilities including element detection, navigation, and application control for Android device testing and interaction.
      9
      56 PyPI
      2
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to drive a connected Android phone over ADB with 28 tools covering screenshots and UI inspection, taps/swipes/typing, app install and launch, file transfer, wireless pairing, and one-call scripted flows like tap-by-text and wait-for-text.
      MIT

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation4/5

    Each tool has a distinct purpose: connect/select, list-only, observe tree, screenshot, apps, tap, swipe, type, key, launch. The only overlap is phone_back and phone_home being explicit convenience wrappers around phone_key, and connect vs devices both listing ADB devices, but descriptions clarify these boundaries well.

    Naming Consistency5/5

    All 12 tools use a uniform phone_ prefix followed by a clear action or resource noun (connect, devices, observe, screenshot, tap, swipe, type, key, launch). The pattern is predictable and fully consistent throughout.

    Tool Count5/5

    12 tools is well within the ideal range and each earns its place by covering a distinct step in the phone-interaction loop (discover, observe, act, launch). Nothing feels padded or redundant at the set level.

    Completeness4/5

    The core lifecycle of connect, observe, interact (tap/swipe/type/key), launch, and capture is fully covered with no dead ends. Minor gaps exist for out-of-band operations like installing/uninstalling apps or retrieving device state, but agents can accomplish the primary automation workflows.