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_lab

      supart
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables Codex to discover, lease, start, control, and release registered local Android Studio emulators through a 63-tool catalog with readiness checks, screen-state reads, and lease-bound UI automation.
      -

    • 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

    • 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
    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

    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

    ActivityStale
    ResponsivenessNo issues

    Resources