Skip to main content
Glama
multi_uiautomator2

multi_uiautomator2

by Starlordzz

Related Servers

Alternatives to multi_uiautomator2

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      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.
      27
      211 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides tools for controlling Android devices using uiautomator2, enabling AI to automate tasks like tapping, swiping, and managing apps.
      186 PyPI
      57
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents and MCP clients to control an Android phone or emulator through ADB, including reading the screen, finding and tapping controls, typing, scrolling, and verifying results, with a live view and optional UI-decision assistance.
      27
      10
      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.
      392 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables agents to interact with Android via text-based UI trees instead of screenshots, supporting taps, swipes, input, macro recording, and device control through an MCP server and CLI.
      1
      -

    TDQS

    A3.5/5.0

    Scored across 24 tools

    Disambiguation4/5

    Tools are largely distinct, but there is some overlap between screenshot/get_screen_elements (both observe the screen) and among the AI-powered tools (ai_debug_screen vs ai_understand_screen vs ai_execute_goal). Descriptions clarify differences, but an agent might occasionally misselect between observation and AI analysis tools.

    Naming Consistency4/5

    Most tool names follow a verb_noun pattern (e.g., list_devices, start_app, input_text). The main deviation is 'screenshot', which is a noun without an explicit verb, and 'press_key' could be seen as slightly inconsistent but still clear. Overall, the naming is predictable and readable.

    Tool Count3/5

    With 24 tools, the server is on the heavier side (16-25 is considered heavy). However, the count is justified by the breadth of features: device management, app lifecycle, UI interactions, observation, and AI delegation. Still, some tools (like the three AI ones) might be consolidated, making the set feel slightly bloated.

    Completeness4/5

    The toolset covers the core lifecycle: device connection, app control, UI interaction (tap, swipe, scroll, input), observation (screenshot, get_screen_elements), and waiting/finding elements. It lacks explicit handling of system dialogs or advanced gestures, but the AI tools can cover some gaps. Overall, no critical dead ends for typical automation workflows.

    Maintenance

    ActivityStale
    ResponsivenessOutdated data