Skip to main content
Glama
HadyAhmed00

Android-MCP

by HadyAhmed00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Android-MCP

No user-submitted related servers found.

    Related Servers

    • 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
      165 npm
      1
      MIT

    • Android MCP

      CursorTouch
      A
      license
      C
      quality
      B
      maintenance
      A lightweight bridge enabling AI agents to perform real-world tasks on Android devices such as app navigation, UI interaction, and automated QA testing without requiring computer-vision pipelines or preprogrammed scripts.
      14
      907
      MIT

    • mcp-android-emulator

      Anjos2
      A
      license
      B
      quality
      C
      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
      105 npm
      20
      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
      71 PyPI
      2
      -

    • scrcpy-mcp

      HuseyinTorres524
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to see and control Android devices, with fast input, screenshots, UI element discovery, app and file management, shell access, and audio/video streaming or recording.
      365 npm
      MIT
    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.4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target clearly distinct actions: tapping, swiping, typing, dragging, pressing buttons, notifications, waiting, and recording. The main ambiguity is between Click-Tool and Click-By-Label, which both perform taps, and Report-Bug-To-Azure vs Report-Bug-To-Azure-Direct, which are near-duplicates.

    Naming Consistency3/5

    There is a recognizable pattern of verb-noun with a -Tool suffix for many tools, but notable exceptions like Setup-Device, Export-Test-Script, Report-Bug-To-Azure, and Click-By-Label break the pattern. Notification-Tool is noun-first rather than verb-first, making the convention mixed but still generally readable.

    Tool Count4/5

    18 tools is slightly above the ideal 3-15 range, but the count is justified by the combination of core UI automation actions, device state access, and a test recording pipeline. The two bug-report tools are somewhat redundant and could be consolidated, but overall the scope is reasonable.

    Completeness4/5

    The toolset covers the core Android automation lifecycle well: screen state discovery, coordinate-based and label-based interaction, gestures, device buttons, notifications, waiting, and recording/exporting tests. Minor gaps exist, such as no explicit wait-for-element or direct assertion tool, but agents can work around these using the state and export features.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources