Android ADB MCP Server

MCP server enabling AI agents to control Android devices and emulators through Android Debug Bridge (ADB) — installing/uninstalling apps, capturing screenshots, running shell commands, tapping and swiping on screen, reading device logs (logcat), managing files, and automating Android device interactions from MCP tool calls.

Evaluated Mar 06, 2026 (0d ago) vcurrent

Homepage ↗ Repo ↗ Developer Tools android adb mobile debugging mcp-server device-control automation

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

100

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Full Android device access via ADB. Only use on development devices. Device data (contacts, messages) accessible. USB debugging must be intentionally enabled.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

An Android developer or QA engineer wants AI-assisted device testing and automation — controlling physical or emulated Android devices through ADB for development and testing workflows.

Avoid When

You need iOS testing — this is Android-only. Also requires USB debugging enabled on device or Android emulator running.

Use Cases

• Automating Android app testing from QA agents
• Controlling Android devices for RPA workflows from automation agents
• Reading Android logcat for debugging from development agents
• Installing and managing apps on test devices from CI/CD agents
• Capturing Android screen state for visual testing from monitoring agents

Not For

• iOS device control (use mcp-server-ios-simulator for iOS)
• Production devices without developer mode enabled
• Automated publishing to Play Store (use Play Console API for that)

Interface

REST API

GraphQL

gRPC

MCP Server

Yes ↗

SDK

Webhooks

Authentication

Methods: none

OAuth: No Scopes: No

No authentication — controls local ADB. Android device must have USB debugging enabled and be authorized for the connecting computer.

Pricing

Model: free

Free tier: Yes

Requires CC: No

Free open source Android ADB MCP. Android SDK/platform-tools (including ADB) required separately.

Agent Metadata

Pagination

none

Idempotent

Partial

Retry Guidance

Not documented

Known Gotchas

⚠ Android device must have USB debugging enabled and be trusted by the host computer
⚠ ADB shell commands run with device-level permissions — agents can modify device state
⚠ Multiple connected devices require explicit device selection via serial number
⚠ ADB WiFi mode possible but less reliable than USB connection for automation

Alternatives

mcp-server-ios-simulator appium-mcp detox-mcp

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Android ADB MCP Server.

$99

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-06.