Skip to main content
Glama
PaboluManohar

Android Mobile MCP Server

by PaboluManohar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Android Mobile MCP Server

No user-submitted related servers found.

    Related Servers

    • phone-control

      sheear
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables controlling an Android device from an MCP client via ADB, including wireless debugging discovery, UI-tree inspection, and performing taps, swipes, typing, app actions, and shell commands without relying on screen coordinates.
      2 npm
      MIT

    • android-mcp-tools

      IMP4R
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and test runners to control Android devices via local ADB, including listing devices, tapping, swiping, typing, sending system keys, launching apps, and dumping UI hierarchy. Communicates over MCP stdio without exposing network listeners.
      -

    • mobile-freecode

      zunairvf-sys
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to discover, pair with, and control Android phones running the FreeCode Agent app over a local network, including accessibility tree inspection, taps/swipes/text input, screenshots, and live screen streaming.
      8
      Apache 2.0

    • scrcpy-agent

      EF-Code
      A
      license
      B
      quality
      B
      maintenance
      Local MCP server for observing and controlling an authorized Android device over USB using ADB and scrcpy, providing screen capture, UI automation, app inspection, logcat, and evidence recording.
      29
      21 npm
      2
      MIT

    • adb-mcp-server

      sfaizi24
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP-compatible agents to control an Android device over the network via ADB, providing tools for shell commands, screen capture, UI inspection, file operations, and input simulation.
      5 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

    A3.5/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools map to clearly distinct actions and objects, and the descriptions generally resolve potential confusion. However, mobile_take_screenshot and mobile_save_screenshot have overlapping purposes, and mobile_press_button vs. mobile_click_on_screen_at_coordinates could be misread without careful attention.

    Naming Consistency4/5

    All tools share a consistent mobile_ prefix and mostly follow a verb_noun pattern, making the set predictable. Minor deviations exist with longer prepositional names like mobile_click_on_screen_at_coordinates and mobile_long_press_on_screen_at_coordinates, but they do not break readability.

    Tool Count3/5

    27 tools is on the heavy side for a typical MCP server, but the broad mobile automation scope—UI interaction, app lifecycle, screenshots/recording, crash reporting, and remote device management—largely justifies the count. Still, the surface feels larger than ideal and could be tightened.

    Completeness4/5

    The server covers the core mobile automation lifecycle well: app install/uninstall/launch/terminate, screen interaction, navigation, screenshots, recording, and crash retrieval. Notable gaps include file push/pull, device health/battery info, and an explicit wait-for-element/condition tool, but these are workable around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources