Browse
→ Infrastructure
→ phonedriver MCP
phonedriver MCP
Reads phone screens as text and controls Android and iOS devices through a local stdio server. Android needs adb; iOS needs a Mac with Xcode, and physical devices need signing setup. Payment approval checks depend on button labels and can be disabled, so they are no substitute for operator oversight. Use a spare device or emulator. Release v0.1.4 published November 14, 2026 (UTC).
MCP unverified
Integration
| Transport | stdio |
| Auth | none |
| Endpoint | npx -y phonedriver mcp |
| Install | Review and pin a phonedriver release before registering phonedriver mcp; connect an authorized emulator or spare phone, run phonedriver doctor and select the intended device explicitly; prepare adb for Android or Xcode and approved signing for iOS; retain human approval for payments, messages, deletion and installation rather than relying only on label detection |
Use Cases
| 01 | Test an app onboarding flow on an emulator |
| 02 | Compare screen text in light and dark modes |
Tags
android ios mobile-testing device-control
Machine-readable: /api/servers.json
· JSON-LD schema embedded in <head>