Skip to main content
Glama
Sign In
Android Control MCP

Android Control MCP

by Scofield81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Android Control MCP

No user-submitted related servers found.

    Related Servers

    • adb_mcp_server

      wolfcoming
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables remote control of Android devices via ADB, including screen operations, input, app management, file transfer, and advanced tools like UI testing and performance analysis.
      25
      MIT

    • android-mcp-server

      chldu2000
      A
      license
      B
      quality
      F
      maintenance
      Enables Android device control via ADB and scrcpy, including device management, app management, file operations, shell commands, input simulation, screen mirroring, and UI element inspection.
      25
      34 PyPI
      Apache 2.0

    • Android Mobile MCP

      erichung9060
      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
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 71 tools

    Disambiguation2/5

    Several tools form overlapping families—screen capture/UI dump/OCR, wait/condition helpers, element-based tap/type wrappers, and rescue diagnostics—so an agent must compare many near-duplicate options before acting. Although the descriptions are detailed and often cross-reference one another, the boundaries are not clear from the tool names alone and misselection is likely.

    Naming Consistency3/5

    Names are consistently lowercase snake_case, but the grammar is mixed: noun-first names like device_list and screen_record coexist with verb-first names like list_apps and list_files, while some tools are bare verbs like tap, swipe, and wait. Rescue tools also use their own prefix, making the set readable but not a uniform verb_noun convention.

    Tool Count2/5

    71 tools is far beyond the well-scoped 3-15 range, and many tools are convenience wrappers over other tools, such as observe_screen, tap_element, type_into, scroll, open_app_and_wait, and rescue_probe. The broad Android-control and rescue scope justifies some size, but the surface feels inflated and would be tighter with fewer, more composable tools.

    Completeness4/5

    The surface covers app lifecycle, UI automation, file operations, device/network info, notifications, logs, backup, and rescue workflows, with shell_run as an escape hatch. Minor gaps exist, such as no direct adb pair support, no clipboard read, and no direct recovery flashing, but agents can work around them.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources