Skip to main content
Glama
TiagoDanin

Android Debug Bridge MCP

by TiagoDanin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Android Debug Bridge MCP

No user-submitted related servers found.

    Related Servers

    • Android MCP

      hamen
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Android devices and emulators through ADB, allowing control actions like tapping, text input, screenshots, UI inspection, and app launching through natural language.
      8 npm
      8
      ISC

    • 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
      -

    • Android MCP Server

      IngaleChinmay04
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables control of Android devices through ADB using natural language commands. Supports browser automation, SMS sending, device information retrieval, settings control, and common device actions like screenshots and button presses.
      3
      -

    • mcp-android-emulator

      Anjos2
      A
      license
      B
      quality
      B
      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
      82 npm
      19
      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 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: screenshot capture, UI dump, folder creation, key events, scrolling, tapping, text input, app listing, and app opening. The descriptions reinforce these distinctions, making it easy for an agent to select the right tool for each specific action.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case, such as capture_screenshot, input_tap, and list_apps. This uniformity makes the toolset predictable and easy to navigate, with no deviations in naming conventions.

    Tool Count5/5

    With 9 tools, the count is well-scoped for Android debugging tasks, covering essential operations like input simulation, app management, and data capture. Each tool serves a clear purpose without redundancy, fitting the domain appropriately.

    Completeness4/5

    The toolset provides strong coverage for core Android debugging workflows, including input actions, app interaction, and data capture. A minor gap exists in lifecycle management tools, such as stopping apps or clearing data, but agents can work around this with the available tools.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources