android-mcp-server: Control Android Devices Through MCP

Overview

android-mcp-server connects MCP clients to Android devices through Android Debug Bridge (ADB). It provides tools for device management and inspection, making Android functionality accessible to compatible assistants and code editors without requiring users to issue each operation manually in a terminal.

It is a practical fit for developers building or testing Android workflows with an MCP client, especially when they want to inspect the UI, capture screenshots, or run ADB commands. It requires a working ADB setup and a connected device or emulator.

Key Features

• Run ADB commands and return their output.
• Capture and return device screenshots.
• Inspect clickable UI elements, including text, descriptions, bounds, and center coordinates.
• List installed packages.
• Retrieve non-data action intents for a package.
• Select a device automatically when one is connected, or configure a device serial for multi-device setups.

Use Cases

• Android developers can inspect app screens and run device commands from an MCP-compatible client during development.
• QA engineers can capture screenshots and examine clickable UI elements while investigating a test issue.
• Automation and agent developers can expose Android device operations as tools for MCP-based workflows.
• Developers managing several connected devices can target a specific device by its ADB serial.

Getting Started

Install the prerequisites, then clone and set up the project:

git clone https://github.com/minhalvp/android-mcp-server.git
cd android-mcp-server
uv python install 3.11
uv sync

Configure an MCP client to launch server.py. See the README for client configuration and device-selection details.

Alternatives

• docker-android: It provides containerized Android emulators with ADB access for development and testing, rather than an MCP server for controlling devices from AI clients.

Considerations

• Python 3.x and ADB must be installed and configured, and an Android device or emulator must be available.
• The README says emulator use has not been tested.
• With multiple devices connected, configure a device serial; without one, the server reports an error listing available devices.
• The README documents access through MCP clients, so this is not presented as a standalone Android app.