Skip to main content
Glama
Neem2004

Android ADB MCP Server

by Neem2004
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Android ADB MCP Server

No user-submitted related servers found.

    Related Servers

    • DroidAgentKit

      iVamsi
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server that provides AI coding agents real Android development tools—Gradle, adb, logcat, lint, crash triage—through a local, permissioned interface. Enables agents to inspect projects, run safe Gradle tasks, capture logs/screenshots, and triage crashes.
      1
      -

    • ThumbAgent

      LiuShiYi1027
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first MCP server that enables AI agents to safely control and observe Android mobile devices, supporting device diagnostics, app lifecycle management, async task execution, and performance monitoring through a policy-constrained interface with explicit confirmations.
      Apache 2.0

    • adb-mcp

      axe01010
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to control Android devices via ADB, providing tools for screen capture, tap/swipe/input, app management, and diagnostics. Works locally over USB or WiFi and integrates with MCP clients like Claude and Cursor.
      1
      MIT

    • ADB MCP Server

      srmorete
      A
      license
      A
      quality
      F
      maintenance
      A TypeScript-based bridge between AI models and Android device functionality, enabling interaction with Android devices through ADB commands for tasks like app installation, file transfer, UI analysis, and shell command execution.
      10
      67 npm
      55
      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

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct ADB operation: logcat retrieval, logcat clearing, UI hierarchy extraction, package listing, and safe shell execution. There is no meaningful overlap, and even the two logcat tools are clearly complementary rather than redundant.

    Naming Consistency5/5

    All tool names follow the exact same pattern: adb_ prefix plus a verb_noun combination (get_logcat, clear_logcat, dump_hierarchy, list_packages, execute_shell). This is fully consistent and makes the toolset easy to navigate.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a focused set of ADB inspection capabilities. Each tool fills a clear role without unnecessary bloat or redundancy, fitting comfortably within the ideal tool count range.

    Completeness3/5

    The set covers logcat and package inspection well, but it lacks essential ADB operations such as device management, package installation/uninstallation, screen capture, and UI interaction (tap/swipe/type), making UI automation a dead end after dumping the hierarchy. The restricted shell helps but is intentionally read-only, so the overall surface feels notably incomplete for a general ADB server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources