Skip to main content
Glama
LioMatthys

DroidPilot

by LioMatthys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to DroidPilot

No user-submitted related servers found.

    Related Servers

    • webadb-agent

      abewartech
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to control a physical Android device or Docker-hosted emulator over ADB by taking screenshots and performing taps, swipes, key presses, text input, shell commands, app launches, and device info queries. It runs as a local MCP stdio server alongside a web UI and REST API for remote access.
      1
      MIT

    • 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

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

    • multi_uiautomator2

      Starlordzz
      F
      license
      A
      quality
      C
      maintenance
      Provides an Android UI automation service with an MCP server, enabling natural language control of Android devices, including clicking, typing, swiping, screenshots, and AI-driven understanding and debugging.
      24
      1
      -
    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.7/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose: text assertion, app launch, device listing, key press, element retrieval, screenshot, screen size, app stop, swipe, coordinate tap, text tap, text typing, and wait. No two tools could be confused for the same action.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (assert_text, launch_app, tap_text, etc.). However, 'screen' and 'screenshot' are nouns used as commands, and 'swipe' is a bare verb, introducing minor inconsistency.

    Tool Count5/5

    13 tools cover the essential operations for Android device automation without being excessive. Each tool addresses a specific need, and the scope aligns well with the server's purpose.

    Completeness4/5

    The tool set covers core interactions (launch, stop, tap, type, swipe, screen inspection, waiting, assertion). Missing features like orientation control, clipboard operations, or scroll, but these are not critical for basic automation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources