Skip to main content
Glama
Sign In
android-mcp-server

android-mcp-server

by chldu2000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to android-mcp-server

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 Control MCP

      Scofield81
      F
      license
      B
      quality
      B
      maintenance
      Enables comprehensive Android device control over ADB, including UI automation, screen capture/recording, app management, file operations, and log/notification access, with a built-in permission system.
      71
      -

    • android-device-mcp

      prashant1507
      F
      license
      B
      quality
      D
      maintenance
      Provides comprehensive Android device management capabilities through ADB, including device management, app management, file operations, and system monitoring.
      18
      1
      -

    • scrcpy-mcp

      marilyn3535
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to view and control Android devices through ADB and scrcpy, supporting screenshots, touch input, app management, UI element discovery, file transfer, shell commands, and audio/video streaming.
      365 npm
      MIT

    • MSC MCP Server

      NakanoSanku
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables control of Android devices through ADB, allowing users to list connected devices, capture screenshots using multiple methods (adb, droidcast, minicap, mumu), and retrieve device information.
      -
    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 25 tools

    Disambiguation5/5

    Each tool targets a distinct function, with clear separation between ADB operations and scrcpy mirroring. No two tools have overlapping purposes; even similar actions like screenshots are differentiated by the underlying technology (ADB vs scrcpy).

    Naming Consistency5/5

    All tools follow a consistent snake_case pattern with a prefix ('adb_' or 'scrcpy_') followed by a verb_noun pair. This uniformity makes it easy for an agent to infer tool roles.

    Tool Count4/5

    With 25 tools, the server is comprehensive but borders on the high side. However, each tool serves a specific need for Android device management, and the set is well-scoped for its purpose.

    Completeness4/5

    The tool surface covers core ADB operations, UI interaction, app lifecycle, file transfer, and screen mirroring. Minor gaps like logcat access or screen recording exist but do not significantly hinder typical automation workflows.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources