Skip to main content
Glama

Related Servers

Alternatives to AutoBot MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables control and automation of Android devices using uiautomator2 and ADB. It supports UI interactions, app management, and shell command execution through the Model Context Protocol.
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides Android Debug Bridge functionality for automating Android devices, enabling remote device management, screen operations, app management, file operations, and shell command execution.
      20
      7
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to control and automate Android devices through natural language, supporting actions like app management, UI interactions, and device monitoring.
      59
      MIT
    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables remote control of Android devices via ADB, including screen operations, input, app management, file transfer, and advanced tools like UI testing and performance analysis.
      24
      MIT
    • F
      license
      B
      quality
      B
      maintenance
      Enables comprehensive Android device control over ADB, including UI automation, screen capture/recording, app management, file operations, and log/notification access, with a built-in permission system.
      71
      -

    TDQS

    B3.3/5.0

    Scored across 53 tools

    Disambiguation4/5

    Most tools have distinct purposes, such as call_phone for calls, click for tapping, and get_screenshot for capturing images. However, some overlap exists, like click, long_click, and press all involving screen interactions, which could cause confusion despite their nuanced differences in duration or action.

    Naming Consistency5/5

    Tool names consistently follow a verb_noun pattern throughout, such as call_phone, clear_app_data, and get_device_info. There are no deviations in naming conventions, making the set predictable and easy to parse.

    Tool Count2/5

    With 53 tools, the count is excessive for an automation server, leading to potential overwhelm and redundancy. While the domain is broad, many tools could be consolidated or omitted without losing functionality, indicating poor scoping.

    Completeness5/5

    The toolset comprehensively covers mobile device automation, including UI interactions, file management, app control, system info, and communication features. There are no obvious gaps; agents can perform full workflows from setup to cleanup without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues