Android Puppeteer MCP Server

MCP server for Android device automation using a Puppeteer-style API. Enables AI agents to control Android devices — tapping, swiping, typing, taking screenshots, and navigating apps — through Android Debug Bridge (ADB). Supports UI testing, app automation, and AI-driven Android interaction workflows.

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

Score Breakdown

⚙ Agent Friendliness

MCP Quality
62
Documentation
62
Error Messages
60
Auth Simplicity
90
Rate Limits
90

🔒 Security

TLS Enforcement
72
Auth Strength
65
Scope Granularity
65
Dep. Hygiene
68
Secret Handling
78

ADB access to Android device. Use test devices only. Physical device control has security implications.

⚡ Reliability

Uptime/SLA
62
Version Stability
60
Breaking Changes
58
Error Recovery
62
AF Security Reliability

Best When

A mobile QA engineer or developer wants AI agents to automate Android app testing — controlling device UI through ADB for regression testing, UI exploration, and accessibility validation.

Avoid When

You need iOS automation (use iOS-specific tools). Also: requires ADB access and developer mode — not suitable for consumer production devices.

Use Cases

  • Automating Android app UI testing from AI testing agents
  • Controlling Android devices for QA automation from test orchestration agents
  • Scripting Android app workflows for regression testing agents
  • Building AI-driven Android UI interactions for accessibility testing

Not For

  • iOS automation (Android-specific via ADB)
  • Production device control without proper testing setup
  • Consumer Android devices without developer mode enabled

Interface

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

Authentication

Methods: none
OAuth: No Scopes: No

No external auth. Connects to Android device/emulator via ADB. Device must have ADB debugging enabled.

Pricing

Model: free
Free tier: Yes
Requires CC: No

Free open source. Requires Android SDK (ADB). Works with physical devices and emulators.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • PHYSICAL EFFECTS: Controls real Android device — test actions affect real apps and data
  • ADB must be enabled on target device — not usable on locked-down enterprise devices
  • UI element discovery can be flaky — Android UI hierarchy changes between app versions
  • Device must be unlocked and ADB authorized — setup required before agent use
  • Community implementation — limited maintenance and documentation

Alternatives

Full Evaluation Report

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

$99

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

5220
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered