Phone MCP (ADB Android Control)

Phone MCP server enabling AI agents to control Android devices via ADB (Android Debug Bridge) — launching apps, taking screenshots, simulating taps and swipes, executing shell commands, installing/uninstalling APKs, capturing device logs, and integrating Android device control into agent-driven mobile testing and automation workflows.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Developer Tools android adb phone-control mcp-server mobile automation appium
⚙ Agent Friendliness
72
/ 100
Can an agent use this?
🔒 Security
72
/ 100
Is it safe for agents?
⚡ Reliability
66
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
65
Documentation
68
Error Messages
65
Auth Simplicity
88
Rate Limits
85

🔒 Security

TLS Enforcement
75
Auth Strength
70
Scope Granularity
65
Dep. Hygiene
65
Secret Handling
82

Full Android device control. ADB authorization on device. No credentials. Trusted devices only. Community MCP.

⚡ Reliability

Uptime/SLA
72
Version Stability
65
Breaking Changes
65
Error Recovery
62
AF Security Reliability

Best When

An agent needs to automate or control an Android device — for mobile testing, UI automation, or Android app development workflows with a device connected via ADB.

Avoid When

You need iOS control, or don't have an Android device with USB debugging enabled.

Use Cases

  • • Automating Android app testing from QA agents
  • • Controlling Android devices for UI automation from testing agents
  • • Capturing screenshots and device state from mobile monitoring agents
  • • Installing and managing apps on Android devices from deployment agents
  • • Debugging Android apps via logcat from mobile development agents
  • • Building AI-driven mobile automation workflows from productivity agents

Not For

  • • iOS device control (ADB is Android-only; use xcrun/libimobiledevice for iOS)
  • • Production Android devices in the field (requires USB/WiFi ADB connection)
  • • Teams without Android development environment or USB debugging enabled

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes ↗
SDK
No
Webhooks
No

Authentication

Methods: none
OAuth: No Scopes: No

No authentication — ADB device access controlled by device USB debugging settings and ADB authorization. Device must have USB debugging enabled and authorize the host computer.

Pricing

Model: free
Free tier: Yes
Requires CC: No

Free open source MCP. Requires Android device with USB debugging enabled and ADB installed on host.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • ⚠ Android device must be connected via USB with USB debugging enabled
  • ⚠ ADB must be installed on host machine (part of Android SDK)
  • ⚠ Device must authorize the host — one-time ADB authorization prompt on device
  • ⚠ ADB over WiFi possible but requires initial USB setup
  • ⚠ Screen actions are coordinate-based — may break with resolution/orientation changes
  • ⚠ Community MCP — ADB API is stable but MCP implementation quality varies

Alternatives

appium-mcp browserstack-mcp

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Phone MCP (ADB Android Control).

$99
API endpoint ↗ Agent guide ↗ Report inaccuracy

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

5215
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
♥
Community Powered