Skip to main content
Glama
ghost-in-the-droid

ghost-in-the-droid

Official
by ghost-in-the-droid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ghost-in-the-droid

No user-submitted related servers found.

    Related Servers

    • Mobile Device MCP

      srmorete
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets AI agents control iOS and Android devices (tap, scroll, type, take screenshots, read UI trees, and run code). Works with multiple devices at the same time.
      66 npm
      52
      MIT

    • phone-harness

      ZachDreamZ
      A
      license
      Not graded
      quality
      A
      maintenance
      Controls Android and iOS devices from AI agents through a token-efficient MCP server, enabling observation, tapping, typing, gestures, navigation, assertions, and safety-gated actions.
      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

    • 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

    • Phone MCP

      viandwi24
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to remotely control a real Android phone over MCP with no ADB, root, or emulator, by connecting a broker server to a sideloaded APK. Exposes tools to list devices, capture screenshots, read the UI tree, open links and deep links, and perform taps, swipes, typing, and global navigation actions.
      1
      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/5.0

    Scored across 66 tools

    Disambiguation2/5

    Many tools have overlapping purposes (e.g., tap_element vs tap, get_elements vs get_screen_tree vs get_screen_xml, screenshot variants, OCR variants, app listing tools, and CRM lookup tools). Even with descriptions, an agent may struggle to select the correct tool.

    Naming Consistency3/5

    Mostly snake_case verb_noun, but there are bare verbs (swipe, tap, wait), noun-only names (device_health, app_state, screen_recording_status), and inconsistent prefix usage (crm_lookup_contact vs lookup_lead). The pattern is readable but not fully consistent.

    Tool Count1/5

    66 tools is excessive for a single server, far beyond the typical 3-15 well-scoped set. This causes usability issues despite the broad domain.

    Completeness3/5

    The server covers many mobile automation areas (UI, OCR, workflows, skills, crashes, CRM), but notable gaps remain—no direct app uninstall, no lead update/reply, no device setting controls. Agents can work around some gaps via workflows.

    Maintenance

    ActivityStale
    ResponsivenessWithin a week

    Resources