MCP server for Android — drive emulators and real devices over adb from Claude Code, Cursor, or VS Code.
概览
Boot an AVD, screenshot, read the UI hierarchy, tap/swipe/type, set a device lock, read logcat, run Gradle builds and tests. 80 tools, from Claude Code, Cursor, VS Code, or any MCP client over stdio. It is the Android counterpart to XcodeBuildMCP, built on the official Go MCP SDK. describe_ui → tap_on_text → screenshot, driven live against a real emulator (emulator-5556), showing the actual tool calls and their actual output. Android is a trademark of Google LLC. adb-mcp is an independent, unofficial tool built for Android and is not affiliated with, sponsored, or endorsed by Google. The Android robot above is reproduced/modified from work created and shared by Google and used according to terms described in the Creative Commons 3.0 Attribution License. Driving Android by hand means a long runbook of raw adb commands, and it is easy to get wrong (stale tap coordinates, CRLF-corrupted screenshots, forgetting exec-out, guessing coordinates off a downscaled image).
README
以下为原文 README 节选，完整内容请查看原文。
Boot an AVD, screenshot, read the UI hierarchy, tap/swipe/type, set a device
lock, read logcat, run Gradle builds and tests. 80 tools,
from Claude Code, Cursor, VS Code, or any MCP client over stdio.
It is the Android counterpart to XcodeBuildMCP, built on the official Go MCP SDK.
Android is a trademark of Google LLC.
adb-mcpis an independent, unofficial tool built for Android and is not affiliated with, sponsored, or endorsed by Google. The Android robot above is reproduced/modified from work created and shared by Google and used according to terms described in the Creative Commons 3.0 Attribution License.
Why
Driving Android by hand means a long runbook of raw adb commands, and it is
easy to get wrong (stale tap coordinates, CRLF-corrupted screenshots, forgetting
exec-out, guessing coordinates off a downscaled image). This server bakes
that knowledge into its tools, so the agent doesn’t have to relearn it:
- Screenshots use
exec-out screencap(no CRLF corruption) and are auto-downscaled so the image reader accepts them. describe_uireturns each element’s center in true device pixels (so taps land where you mean them to, no guessing off the image) and retries the transient “could not get idle state” failure on its own.
The workflow itself ships as readable resources the agent can pull up mid-task (the observe→act loop, native PIN/lock handling, crash triage, see below) instead of relearning them each session.
Getting started
1. Prerequisites
安装
This server does not publish a one-line install command.
Open the repository installation guide 新手？先看 mcpskill.org 教程 →配置
{
"mcpServers": {
"adb": { "command": "adb-mcp" }
}
}