Skip to main content
Glama
zifanersuotang

Codex Android MCP

by zifanersuotang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Codex Android MCP

No user-submitted related servers found.

    Related Servers

    • Android DevTools MCP

      xleepy
      A
      license
      A
      quality
      C
      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

    • 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

    • 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
      46 npm
      17
      MIT

    • adb-mcp-server

      sfaizi24
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP-compatible agents to control an Android device over the network via ADB, providing tools for shell commands, screen capture, UI inspection, file operations, and input simulation.
      7 npm
      MIT
    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

    A4.2/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of Android automation: device lifecycle, screenshots, memory, UI tree vs OCR, logs, processes, backtrace, etc. Even overlapping tools like android_interact, android_tap_element, and android_tap_text are clearly separated by interaction type (raw coordinates, view identity, OCR text), and android_ui_rows/android_tap_row are specific to list items. The descriptions emphasize when to use each, eliminating ambiguity.

    Naming Consistency4/5

    All tools are prefixed with 'android_' and use lowercase snake_case, providing strong consistency. However, there is a mix of noun-only names (android_devices, android_meminfo, android_logs) and verb-noun names (android_list_apps, android_tap_element, android_find_text), which is a minor deviation but still predictable once the pattern is understood.

    Tool Count4/5

    With 19 tools, the count is slightly on the higher side but justified by the breadth of the Android ADB automation domain: device lifecycle, UI inspection, OCR, logging, memory, processes, and backtraces. Each tool has a clear purpose and none feel redundant, though the set is larger than the typical 10-15 range.

    Completeness4/5

    The tool set covers the core workflows for Android automation: device boot/shutdown, screenshots, UI tree and OCR interaction, list handling, log reading, process/memory inspection, and app info. A minor gap is the absence of a build/install tool (mentioned in android_launch_app as android_build_run but not present), and no file push/pull, but the provided surface is comprehensive for typical interaction and diagnostics.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources