Skip to main content
Glama
Sajinthan

android-emulator

by Sajinthan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to android-emulator

No user-submitted related servers found.

    Related Servers

    • mcp-android-emulator

      Anjos2
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to interact with Android devices and emulators via ADB, providing tools for screenshots, UI inspection, touch and text input, app management, and device control.
      42
      82 npm
      19
      MIT

    • Android DevTools MCP

      xleepy
      A
      license
      A
      quality
      D
      maintenance
      Enables an agent to inspect and interact with Android emulators or physical devices via ADB, capturing UI snapshots, tapping nodes, typing text, and reading app logs.
      10
      MIT

    • adb-tv-mcp

      mosesmrima
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to control Android TV/Android devices through ADB, including screen capture, remote control, app management, and more.
      24
      8 npm
      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

    • Android MCP

      hamen
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Android devices and emulators through ADB, allowing control actions like tapping, text input, screenshots, UI inspection, and app launching through natural language.
      16 npm
      8
      ISC
    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 37 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, from device control (orientation, location, appearance) to UI interaction (tap, swipe, type, find elements) to app management and file operations. Even closely related tools like press_button vs key_event are differentiated by scope (common navigation vs arbitrary keycodes).

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (type_text, press_button, set_orientation, install_app), but a few exceptions like 'swipe', 'tap', 'shake', 'logcat', and 'key_event' break the strict consistency. Overall the naming is clear and readable, with only minor deviations.

    Tool Count3/5

    With 37 tools, this server is twice the typical upper bound of 15. While each tool serves a specific function for comprehensive emulator control, the sheer number feels heavy and could be consolidated (e.g., combining some status bar or UI query tools). Still, the scope justifies the count better than a generic utility server.

    Completeness5/5

    The toolset covers essentially all major aspects of Android emulator interaction: device control, UI automation, app lifecycle, file transfer, logging, screen capture, and emulator lifecycle management. No critical gaps are apparent for the intended domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources