Phonedriver logo

Phonedriver

Control Android and iOS devices through MCP with screen text, taps, screenshots, and confirmation before payment actions.

Install Phonedriver

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "phonedriver": {
      "command": "npx",
      "args": [
        "-y",
        "phonedriver"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y phonedriver

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked .

Overview

phonedriver MCP server lets AI agents inspect and operate Android phones, Android emulators, iPhones, and the iOS Simulator. It exposes the phone through standard MCP over stdio, returning compact, numbered screen text so agents can target elements without repeatedly polling or relying on coordinates. Use it for mobile-app testing, device tasks, and workflows that require interacting with a real phone; payment taps pause for human approval.

Use cases

  • Test mobile app signup and onboarding flows
  • Inspect and change Android device settings
  • Find and document reproducible mobile-app bugs
  • Compare app readability in dark and light modes
  • Navigate phone-based checkout flows with approval

Key features

  • Structured screen text with numbered element handles
  • Tap, text-entry, and screenshot actions
  • Settled-screen synchronization and change-only responses
  • Android and iOS device support
  • Human confirmation before payment taps
  • Standard MCP stdio transport

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 20h ago via OSV.dev · phonedriver (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars149Stargazers on the source repository.
Last commitTodayMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.

How Phonedriver works

What phonedriver does

phonedriver gives an MCP-compatible AI client access to a connected Android or iOS device. Agents can read the current interface as structured text, identify controls by handles such as @e24, tap those controls, enter text, and request screenshots when visual content is necessary.

The server is suited to tasks that cannot be completed from a desktop alone. Examples include changing phone settings, working through an app's signup flow, checking onboarding in multiple display modes, finding reproducible bugs, and navigating a mobile website. It can also drive commerce flows while stopping for confirmation before a payment action.

How it works

phonedriver runs as a standard MCP server over stdio, allowing an MCP client to launch it as a local process. The client sends actions to the device and receives a screen representation after the interface settles. Screen output is presented as a short numbered hierarchy of apps, buttons, switches, groups, and other visible elements.

Actions can refer to those numbered handles instead of requiring the model to estimate screen coordinates. Responses can report only the changes since the previous screen: added lines use +, removed lines use -, and changed lines use ~. This keeps the device state compact for the agent. Screenshots are available for cases where text is not enough.

The underlying device can be an Android emulator, an Android phone connected with USB debugging enabled, or the iOS Simulator. The project also supports real iPhones through its installation workflow.

Setup and configuration

The quick-start command registers the npm-delivered server with Claude Code:

Terminal
claude mcp add phonedriver -- npx -y phonedriver mcp

A Homebrew installation is also available:

sh
brew install hridaya423/tap/phonedriver
claude mcp add phonedriver -- phonedriver mcp

Claude Code and Codex can install phonedriver as a plugin. The plugin supplies the server and its skill together; it should not be used alongside a separate MCP registration, or the tools will appear twice. Cursor and VS Code have installation links in the project documentation.

On its first run, phonedriver downloads and caches a machine-specific binary for macOS, Linux, or Windows. Run phonedriver doctor to check adb, Xcode, and detected devices and to identify setup problems.

Tools and capabilities

  • Read the active phone screen as compact, numbered text.
  • Tap controls by their returned element handles.
  • Wait for the interface to settle before returning the result.
  • Report only screen changes when an action produces a delta.
  • Enter text on the device.
  • Capture screenshots when visual inspection is required.
  • Pause before tapping a payment control such as Buy with GPay.
  • Drive Android phones, Android emulators, iPhones, and the iOS Simulator.

Limitations and notes

A usable device environment is required: Android workflows need an emulator or a phone with USB debugging, while iOS workflows use the iOS Simulator or supported iPhone setup. Android and iOS dependencies such as adb and Xcode must be available where applicable.

The server is distributed under the AGPL-3.0 license. Its standard transport is local stdio rather than a hosted HTTP endpoint. Avoid registering the plugin and standalone MCP command at the same time, because that duplicates the exposed tools.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Phonedriver

phonedriver is an MCP server that connects AI agents to Android phones, Android emulators, iPhones, and the iOS Simulator. Its main tools expose screen text, taps, screenshots, and text entry, with actions synchronized to settled screens and a confirmation pause before payment taps.

Install it with `npx -y phonedriver mcp` through your MCP client, or install the Homebrew binary and register `phonedriver mcp`. Claude Code and Codex also support the phonedriver plugin; use either the plugin or a separate MCP registration, not both.

Yes, phonedriver works with Cursor through its standard MCP-over-stdio interface. The project provides a Cursor installation link, and the server can then operate a configured Android or iOS device.

phonedriver supports Android emulators, Android phones with USB debugging enabled, the iOS Simulator, and real iPhones through its installation workflow. Android setup uses adb, while iOS setup may require Xcode.

phonedriver pauses and asks for human approval before tapping a payment control such as Buy with GPay. This lets an agent complete the surrounding phone workflow without finalizing the payment automatically.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPhonedriver AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/phonedriver?style=directory)](https://allmcps.com/mcp/phonedriver)
HTML Embed
<a href="https://allmcps.com/mcp/phonedriver"><img src="https://allmcps.com/api/badge/phonedriver?style=directory" alt="Phonedriver on AllMCPs" /></a>