Android MCP Server

What martingeidobler/android-mcp-server MCP server does

The martingeidobler/android-mcp-server MCP server connects an MCP-compatible assistant to Android devices and emulators through ADB. It covers both device management and application interaction, so an agent can discover connected targets, start an available Android Virtual Device, inspect the current screen, and operate the device without an SDK integration inside the application.

Screen analysis includes screenshots returned for visual inspection and UI hierarchy data containing element bounds, text, resource IDs, and state. Interaction tools support coordinate-based taps, element-based taps, typing into the focused field, key presses, swipes, long presses, double taps, repeated taps, scrolling, and waits for elements to appear. The tap_and_wait operation combines an element tap, UI settling delay, and updated tree retrieval.

How it works

The server invokes ADB against a connected Android device or emulator. Agents can use list_devices and list_avds to identify targets, then use device-specific operations for multi-device workflows. start_emulator waits up to 60 seconds for the selected emulator to become available.

Application workflows can install an APK, launch an app by package name, inspect the foreground activity, and pull files from the device. adb_shell provides access to arbitrary ADB shell commands. For troubleshooting, an agent can clear the logcat buffer before reproducing a problem, then retrieve logs filtered by package, severity, or time. The server also reuses an ADB shell session and caches device information during a session, according to the project documentation.

Setup and configuration

Install the martingeidobler/android-mcp-server MCP server with Node.js 18 or later and configure it as a local stdio MCP server:

{
  "command": "npx",
  "args": ["-y", "android-mcp-server"]
}

The machine must have the Android SDK, ADB platform-tools, and the Android emulator available. A running emulator or connected Android device is also required for device operations. The server looks for the SDK in the default macOS location or through ANDROID_HOME; set that variable in the MCP client configuration when the SDK is installed elsewhere.

The README provides configurations for Claude Desktop, Cursor, and Windsurf, as well as a build-from-source path using npm install, npm run build, and the generated dist/index.js entry point. No application-side SDK changes are needed because interaction occurs through ADB.

Tools and capabilities

• Discover connected devices and configured AVDs.
• Start an emulator and wait for it to connect.
• Capture compressed screenshots, optionally saving them locally.
• Read UI trees and target elements by resource ID, text, or content description.
• Automate taps, gestures, text entry, key presses, scrolling, waits, and action sequences.
• Install APKs, launch packages, inspect activities, and pull device files.
• Read and clear logcat output, including filtered diagnostic logs.
• Query model, manufacturer, Android version, API level, display size, and DPI.
• Run arbitrary ADB shell commands.

Limitations and notes

This tool depends on a working local Android development environment and ADB connectivity. Element-based actions depend on the target UI exposing matching text, resource IDs, or content descriptions; coordinate actions require suitable screen coordinates.