Skip to main content
Glama

Related Servers

Alternatives to android-adb-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server that gives AI agents full vision and control over Android devices via ADB and scrcpy. Supports screenshots, input, apps, UI automation, shell, files, and clipboard.
      38
      365 npm
      125
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides an MCP server that lets AI agents inspect and control an Android phone over Wi-Fi or USB, including screenshot element maps, OCR, taps, typing, scrolling, app launching, notifications, clipboard, and device settings/controls.
      898 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives MCP-compatible AI assistants vision and control over Android devices — capturing screenshots, tapping, swiping, typing, launching apps, inspecting UI elements, streaming audio/video, transferring files, and running shell commands over ADB, with a fast binary control protocol for near-instant input and screenshots.
      365 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      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
    • F
      license
      A
      quality
      C
      maintenance
      A MCP server that enables AI assistants to control Android devices via ADB, supporting device info, screen control, input simulation, app management, shell execution, file transfer, and UI parsing.
      20
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server gives AI agents vision and control over Android devices through ADB and scrcpy, enabling screen capture, taps, swipes, typing, app launching, UI element inspection, file transfer, and shell commands. It uses scrcpy's binary control protocol for fast input and near-instant screenshots, falling back to ADB when scrcpy is unavailable, and also supports video and audio streaming plus recording.
      365 npm
      MIT

    TDQS

    B3.3/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: device listing, app inspection, input actions, screen capture, and UI element interaction are well separated. tap vs tap_element and open_app vs current_app are unambiguous, so an agent can select correctly without confusion.

    Naming Consistency3/5

    All names use snake_case, which is readable, but the verb/noun convention is inconsistent: list_devices and get_screen_size follow verb_noun, while screenshot, current_app, key_event, and ui_dump use noun or mixed forms. The set is understandable but not predictably patterned.

    Tool Count5/5

    14 tools is well-scoped for an ADB/UI-automation server. Each tool covers a distinct operation, and there is no obvious redundancy or filler.

    Completeness4/5

    The surface covers device discovery, app inspection, input gestures, text entry, key events, screenshots, and UI hierarchy dumping. Minor gaps exist for app install/uninstall, file transfer, shell commands, and reboot, but core UI automation workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing