Skip to main content
Glama
pedro-rivas

Android Puppeteer

by pedro-rivas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Android Puppeteer

No user-submitted related servers found.

    Related Servers

    • Android Mobile MCP

      erichung9060
      F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact with Android devices through UI manipulation, screen capture, touch gestures, text input, and app management via ADB. Provides comprehensive mobile automation capabilities including element detection, navigation, and application control for Android device testing and interaction.
      9
      4
      -

    • Karagöz

      yagizdo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to automate Android and iOS devices, including emulators and physical devices, by capturing screenshots, reading UI accessibility trees, performing touch and text input, and managing app lifecycle and logs.
      MIT

    • android-mcp

      ibrahimali111
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to control, inspect, and automate Android devices, Waydroid containers, and AVD emulators over ADB. Provides tools for screenshots, UI-hierarchy text-based tapping, gestures, key presses, text input, app management, and raw shell commands.
      12
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have distinct purposes for Android device interaction, but 'press' and 'long_press' overlap in functionality as both handle screen touches with duration parameters, which could cause confusion. Other tools like 'get_device_dimensions' and 'get_ui_elements_info' are clearly differentiated.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with clear verb_noun structure (e.g., 'take_screenshot', 'type_text', 'scroll_element'). The naming is predictable and readable throughout the set.

    Tool Count5/5

    With 12 tools, this server is well-scoped for Android automation, covering essential actions like input, navigation, and media capture. Each tool serves a specific role without bloat, fitting typical automation needs.

    Completeness4/5

    The toolset covers core Android interaction workflows including input, navigation, and media, but lacks tools for advanced tasks like app management (e.g., install/uninstall) or system settings. Minor gaps exist, but agents can perform basic automation effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources