Skip to main content
Glama
bsaisuryacharan

android-use

by bsaisuryacharan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to android-use

No user-submitted related servers found.

    Related Servers

    • android-control

      brandonbowmansr
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude or any MCP agent to see and operate a real Android phone over adb, with fast screen reads, tap/type/swipe actions, app launching, deep links, and brand-aware setup guidance, all without admin rights or an Android SDK.
      MIT

    • phone-use

      sauravtom
      A
      license
      B
      quality
      C
      maintenance
      Enables coding agents to observe and control an authorized Android phone over ADB through MCP tools and a JSON CLI. It supports UI inspection, screenshots, taps, swipes, typing, key presses, app listing, and launching.
      13
      51
      MIT

    • DroidRun MCP Server

      chukfinley
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables text-based control of Android devices through Claude Code using accessibility tree automation. Supports UI interaction, app launching, text input, gestures, and navigation without requiring screenshots.
      MIT

    • Phone for AI MCP

      lllq-123
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables an AI agent to operate a spare Android phone through MCP: capture screenshots, inspect UI controls, tap/swipe, input Chinese text, launch apps, and optionally run rooted shell commands or transfer files. It also supports a live web console for remote viewing and control.
      20
      MIT

    • Android ADB MCP Server

      xuegao-tzx
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables programmatic control of Android devices via ADB, supporting UI automation, app management, screen capture with OCR, and file transfers through the Model Context Protocol. It allows MCP-compatible clients like Claude Desktop and Cursor to interact directly with physical or emulated Android devices.
      3
      Apache 2.0
    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.3/5.0

    Scored across 38 tools

    Disambiguation4/5

    Most tools are clearly separated by domain (device discovery, connection, UI interaction, Chrome, phone management), but some overlap exists: check_device, phone_health, and watchdog_report all diagnose reachability, and unlock_phone/lock_phone are inverse operations that could be confused with disconnect_wireless. The descriptions help, but a few boundaries are fuzzy.

    Naming Consistency4/5

    The naming is predominantly verb_noun (check_device, list_devices, tap_text, open_app, chrome_read), with a consistent style. Minor deviations: 'watchdog_report' is noun-ish, 'use_phone' and 'lock_phone' are less descriptive, and the chrome_* prefix is a clear sub-pattern. Overall predictable and readable.

    Tool Count3/5

    38 tools is on the heavy side for a single server, though the scope is broad (device management, UI automation, Chrome automation, phone registry). The count feels bloated because several tools could be merged (e.g., check_device/phone_health/watchdog_report, or the wireless pairing cluster), but each tool does have a distinct function.

    Completeness4/5

    The server covers the full lifecycle: discovery, pairing, connection, screen interaction, app control, Chrome automation, and phone registry management. Minor gaps: no explicit tool for swiping/long-press, no way to get device logs, and no tool to manage the allowlist for open_app, but the core workflows are well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources