Skip to main content
Glama
AsmanovLev

android-mcp

by AsmanovLev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to android-mcp

No user-submitted related servers found.

    Related Servers

    • Android-MCP

      HadyAhmed00
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to control Android devices and emulators through direct UI interaction, allowing app navigation, automated testing, and real-world task execution via ADB without computer vision or scripts.
      18
      2
      MIT

    • Android MCP Server

      divineDev-dotcom
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to fully control Android devices through over 30 tools for app management, UI automation, and vision-based analysis via ADB. It supports multi-device management, action recording, and smart execution strategies ranging from UI hierarchy parsing to coordinate-based interaction.
      37
      190 npm
      1
      MIT

    • adb-tv-mcp

      mosesmrima
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to control Android TV/Android devices through ADB, including screen capture, remote control, app management, and more.
      24
      8 npm
      MIT

    • 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
      4
      -
    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.3/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct function: gestures, buttons, app management, F-Droid/RuStore search/download, password management, device state, etc. Even gesture tools are differentiated by single, combo, and macro operations.

    Naming Consistency2/5

    Naming is inconsistent: some tools have 'mobile_' prefix while others (fdroid_download, rustore_search) do not. Verb-noun combinations vary (e.g., 'mobile_power', 'mobile_activity_manager', 'mobile_device_list'), and some names are vague.

    Tool Count4/5

    19 tools is on the higher side but justified given the breadth of Android device control. A few tools (e.g., three gesture tools) could potentially be consolidated, but overall count is reasonable.

    Completeness4/5

    Covers core device interaction, app lifecycle, and app store search/download. Missing advanced debugging (logcat), file operations, or notification management, but sufficient for common automation tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources