Skip to main content
Glama
JackoPeru

mcp-android

by JackoPeru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to mcp-android

No user-submitted related servers found.

    Related Servers

    • termux-mcp

      YSCodex
      A
      license
      Not graded
      quality
      B
      maintenance
      Turns an Android phone running Termux into a remotely drivable machine, letting an AI agent run shell commands, manage background jobs and tmux sessions, read and write files, install packages, and use Android device features such as battery status, screenshots, notifications, SMS and sensors. It can be reached either over stdio on the same device or over Streamable HTTP with bearer tokens and token scopes from anywhere on the local network, with a confirmation gate on destructive actions, a jailed file API and an audit log.
      18 npm
      MIT

    • Android MCP Server

      wujie272
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to directly control Android devices via Termux, providing 120+ tools for screen manipulation, file management, app control, and system operations with layered loading and security gating.
      2
      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 Control MCP

      Scofield81
      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
      -
    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.1/5.0

    Scored across 65 tools

    Disambiguation2/5

    Many tools occupy overlapping territory: wait_idle, wait_change, wait_activity, ui_wait_for, and events_wait are all wait-like; status, device_info, capabilities, diagnostics, and the privilege status tools blur together; input_text and ui_set_text both set text; global_action and press_key both handle navigation. Descriptions help in some cases, but with 65 tools the boundaries are frequently unclear.

    Naming Consistency4/5

    All tools share the android_ prefix and use clean snake_case, with strong domain grouping like android_file_*, android_ui_*, and android_notification_*. However, the verb/noun order is inconsistent (android_clipboard_get vs android_launch_app vs android_ui_find) and a few abstract nouns like android_flow and android_batch break the pattern.

    Tool Count1/5

    65 tools is an extreme count for a single MCP server. Many could be consolidated, especially the status/privilege reports, wait variants, coordinate gesture tools, and execution helpers. The scope is broad, but the surface is not well-scoped.

    Completeness4/5

    The set covers UI observation and interaction, app launching and management, clipboard, notifications, media, volume, shell, logcat, file CRUD, and multi-step flows, so real workflows rarely dead-end. Minor gaps exist around app installation/uninstallation and direct system setting toggles, but most can be worked around via existing shell or intent tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources