adb-mcp

describe_ui→tap_on_text→screenshot, driven live against a real emulator (emulator-5556), showing the actual tool calls and their actual output.

Driving Android by hand means a long runbook of rawadbcommands, and it is easy to get wrong (stale tap coordinates, CRLF-corrupted screenshots, forgettingexec-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 useexec-out screencap(no CRLF corruption) and are auto-downscaled so the image reader accepts them.
- describe_uireturns each element'scenter 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 readableresourcesthe agent can pull up mid-task (the observe→act loop, native PIN/lock handling, crash triage, see below) instead of relearning them each session.

- Android SDK withplatform-tools(adb) andemulator. The server finds it via$ANDROID_HOME/$ANDROID_SDK_ROOT, else the platform default (~/Library/Android/sdkon macOS). If your MCP client launches the server without those set, pass--sdk /path/to/sdkin the client config'sargs(the server then exports it, so Gradle finds the SDK too).doctorprints the location it resolved.
- At least one AVD (create one in Android Studio's Device Manager).

curl -fsSL https://raw.githubusercontent.com/iksnerd/adb-mcp/main/install.sh | sh

Once installed, stay current with the built-in updater. It fetches the latest release, verifies its checksum, and swaps the binary in place:

The registration below launches the server by the bare nameadb-mcp, so it must be on your$PATH(which adb-mcpshould resolve; the installer warns if~/.local/binisn't on it). Otherwise point the client at the absolute path to the binary instead.

(When working inside this repo itself, the bundled.mcp.jsonis picked up automatically, no registration needed.)

Cursor / VS Code: one-click install (assumesadb-mcpis on yourPATHfrom step 2):

Any other client(Windsurf, Codex, …): runadb-mcpover stdio. The usual config shape:

{ "mcpServers": { "adb": { "command": "adb-mcp" } } }

To confirm it's wired up, ask your agent to "boot an emulator and take a screenshot".

make install # builds ./bin/adb-mcp and copies it to ~/.local/bin # or: go build -o bin/adb-mcp ./cmd/adb-mcp # or straight from the module (note the /cmd/adb-mcp suffix): go install github.com/iksnerd/adb-mcp/cmd/adb-mcp@latest

observe → locate → act → re-observe.screenshotto see,describe_uito get true-pixel centers,tap/tap_on_text/swipe/input_textto act, thenscreenshotagain to confirm. Readandroid://guide/drivingfor the full loop and the gotchas that waste turns.

make check # go vet + go test (unit tests need no emulator) make run # run over stdio for manual JSON-RPC poking

cmd/adb-mcp/main.go entry: subcommands (update/version) or serve MCP over stdio internal/tools/ thin MCP tool bindings internal/adb/ the device layer: an adb.Client whose methods are the commands internal/gradle/ host-side Gradle: build, find APKs, parse test reports internal/uiauto/ pure uiautomator-hierarchy model + parsing (unit-tested) internal/sdk/ resolves the Android SDK (adb/emulator paths, PATH env) internal/concurrent/ RunAll/RunIndexed: fan out independent I/O calls, join, done internal/guides/ the skill guides, embedded and served as MCP resources internal/selfupdate/ the adb-mcp update release fetch/verify/swap internal/bridgeupdate/ the adb-mcp bridge install release fetch/verify/install

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Control Android devices via the Android Debug Bridge (ADB).

An agentic toolkit to control, debug, and profile iOS and Android apps.

The deepest Android Debug Bridge MCP server — 147 tools from UI to baseband.

Proxyman MCP allows AI to inspect HTTP traffic, create debugging rules, and control Proxyman - all through natural language conversations.

Interact with Android devices using the Android Debug Bridge (ADB).

Interact with Android devices using the Android Debug Bridge (ADB).

AI 測試大師 — MCP server driving pytest / Jest / Cypress / Go / Maestro. Analyze, generate, run, advise. Web + Mobile (iOS/Android/BlueStacks).

Control Android devices using the Android Debug Bridge (ADB).

Automate Android devices using the Gbox SDK.