Android MCP servers compared
As of 1 October 2026
An Android MCP server lets an AI agent such as Claude see and control an Android phone through the Model Context Protocol. The eight servers below differ in how they capture the screen, whether they need ADB or a relay, whether they also cover iOS, and what they cost. Each fact links to the project's own page.
Disclosure: ScreenSync MCP is our product. We have tried to describe every other project fairly and only from its own documentation. Spotted an error? Email info@epsoldev.com and we will fix it.
Quick picks
- Live view of your own phone plus your real browser tab, kept on your network: ScreenSync MCP.
- No ADB, and control from anywhere through a relay: ScreenMCP.
- iOS and Android, including simulators and emulators: mobile-mcp.
- Fast screenshots and input if you already use scrcpy: scrcpy-mcp.
- Deep debugging: logs, files, apps and bug reports: DroidMind.
- Phones in the cloud, no device of your own: mobilerun.
The comparison table
Scroll the table sideways on a small screen. “Not stated” means the project's documentation does not say, so we did not guess.
Swipe or scroll the table sideways to see every column.
| Server | Capture method | Needs root? | Needs ADB? | Cable or LAN | Live stream or screenshots | iOS | Cloud relay or quotas | Price | Licence | Best for |
|---|---|---|---|---|---|---|---|---|---|---|
| ScreenSync MCP Oursscreensyncmcp.tech · setup guide | Android MediaProjection, with your consent each session; Chrome or Edge extension for browser tabs | No | Not for capture; yes for control tools (tap, swipe, type), run from the hub | LAN: phone to hub over your network; ADB over USB or wireless debugging; optional Google Drive fallback | Live mirror stream to the hub, plus screenshots and UI tree on demand | No | None | Free while in active development | Not open source; the extension source is public | A live view of your own phone and your real browser tab in one local hub: 29 phone/desktop tools + 197 browser tools |
| ScreenMCPsite · pricing · GitHub | Android app built on AccessibilityService; clients for Windows, macOS and Linux too | No* | No | Neither: commands travel through a WebSocket relay, hosted or self-hosted | Screenshots on demand | No; its README marks iOS as not available, citing Apple restrictions | Hosted relay with daily command limits: 100 (Free), 2,000 (Personal), 20,000 (Business); or self-host | Free; $9/month Personal; $29/month Business; Enterprise on request | MIT | Control without ADB from any network, and desktops as well as phones |
| mobile-mcpGitHub | Native accessibility tree first; screenshots and coordinates as a fallback | No* | Yes for Android (Android Platform Tools); Xcode command-line tools for iOS | Local ADB or Xcode tools; connection type not stated | Accessibility snapshots; screenshots when needed | Yes: simulators and real devices | None for local use; README mentions a paid Mobile Next Cloud for devices | Free | Apache-2.0 | iOS and Android automation on simulators, emulators and real devices |
| Android-MCPGitHub | ADB and the Android Accessibility API; a State-Tool snapshot of active apps and interactive elements | No* | Yes | USB or Wi-Fi ADB | UI-state snapshots on demand | No | None | Free | MIT | A Python toolkit for Android 10+ devices and emulators |
| android-mcp-serverGitHub | ADB: screenshots and a UI layout of clickable elements | No* | Yes | Local ADB; connection type not stated | Screenshots and UI layout on demand | No | None | Free | Apache-2.0 | A minimal starting point with 5 tools, including raw ADB commands |
| DroidMindGitHub | ADB: screenshots, taps, swipes, text input and key presses | No* | Yes | USB or TCP/IP ADB | Screenshots on demand | No | None | Free | Apache-2.0 | Device debugging: logcat, ANR and crash logs, files, app management and bug reports, with command validation |
| scrcpy-mcpGitHub | scrcpy and ADB | No* | Yes | USB or Wi-Fi ADB | Screenshots (about 33 ms with scrcpy, about 500 ms over ADB, per its README); video and audio streaming tools | No | None | Free | MIT | Speed: 44 tools with a fast scrcpy path for screenshots and input |
| mobilerunsite · MCP · pricing · GitHub | Cloud-hosted real phones; the open-source framework uses a Portal app with an accessibility service on local devices | No* | Not for the hosted MCP server (“no ADB, no emulator, no local setup”) | Neither: cloud phones over the internet | UI trees and screenshots | Yes: cloud iPhones as paid add-ons | Hosted MCP server; free tier of 60 device minutes and 500 credits a month | Free tier; paid plans; dedicated phones from $50/month (Android) to $160/month (iPhone, billed yearly) | Framework MIT; hosted service commercial | Agents that need phones in the cloud, from CI or a server |
* Root is not among the project's stated requirements; ADB and accessibility services work without it. “None” for ScreenSync MCP's relay means frames go from phone to hub on your own network; screenshots your agent requests are still sent to that agent's model provider, as with any server here. mobilerun is the project formerly published as DroidRun: github.com/droidrun/droidrun now opens droidrun/mobilerun.
What each one needs to run
| Server | Requirements (as stated) | Tools (as stated) |
|---|---|---|
| ScreenSync MCP | Android 7.0 or later; Node.js 18+ on Windows, macOS or Linux; ADB only for control tools | 226: 29 phone/desktop + 197 browser; 17 prompts, 3 resources |
| ScreenMCP | Android app with its accessibility service enabled; account and API key for the hosted relay | Not stated |
| mobile-mcp | Node.js v20+; Xcode command-line tools (iOS); Android Platform Tools (Android) | Not stated |
| Android-MCP | Python 3.13; ADB; Android 10+ | 10 listed in its README |
| android-mcp-server | Python 3.x with uv; ADB | 5 |
| DroidMind | Python 3.13 with uv; ADB on your PATH; USB debugging | Not stated |
| scrcpy-mcp | Node.js 24+; ADB; scrcpy recommended; ffmpeg for streaming | 44 |
| mobilerun | A mobilerun account for cloud phones; mobilerun setup installs the Portal app for local devices | Not stated |
When to choose which
Choose ScreenSync MCP if…
you want your agent to watch your own Android phone live and also work in your real Chrome or Edge tab, from one free hub on your computer. Capture needs no root and no ADB; the tap, swipe and type tools use ADB over USB or wireless debugging. Frames stay on your network (screenshots your agent requests are sent to that agent's model provider), there is no per-command quota, and the tool count splits into 29 phone/desktop tools + 197 browser tools. It does not support iOS, and it expects the phone and computer on the same network unless you turn on the Google Drive fallback. Start with the ScreenSync MCP setup guide.
Choose ScreenMCP if…
you cannot or do not want to enable ADB, or you need to reach the phone when it is not on your network. Its accessibility-service app talks to a relay, so it works across networks, and you can self-host the relay if you prefer. It also controls Windows, macOS and Linux machines. The hosted plans meter commands per day.
Choose mobile-mcp if…
you need iOS as well as Android, or you test on simulators and emulators. Its accessibility-first approach reads the UI tree before falling back to screenshots, which keeps image tokens down.
Choose scrcpy-mcp if…
you already rely on scrcpy and want the fastest ADB-based screenshots and input, with a large set of 44 tools covering apps, files, the shell and media streaming.
Choose DroidMind if…
your work is device debugging: logs (logcat, ANR, crash, battery), files, app installs and bug reports. Its command validation and risk assessment add a safety layer around ADB.
Choose Android-MCP or android-mcp-server if…
you want a small Python codebase you can read and extend. Android-MCP works over USB or Wi-Fi ADB on Android 10+ devices and emulators; android-mcp-server keeps to five tools, one of which runs any ADB command.
Choose mobilerun if…
you do not want a physical device at all. Its hosted MCP server hands your agent real Android and iOS phones in the cloud, which suits CI and server-side agents. The open-source framework also drives local devices.
How we compared
On 1 October 2026 we read each project's README, website and pricing page, linked under its name in the table. We recorded only what those pages state; where a page is silent we wrote “not stated” rather than guessing. We did not run benchmarks, and we do not publish speed claims for other projects beyond the numbers they publish themselves. ScreenSync MCP's own numbers come from our product: for example, frames arrive in about 94 ms median on our LAN tests.
Projects change quickly. If a row is out of date, write to info@epsoldev.com with a link and we will update the page.
Sources
- screenmcp.com and screenmcp.com/pricing; github.com/shimondoodkin/screenmcp
- github.com/mobile-next/mobile-mcp
- github.com/CursorTouch/Android-MCP
- github.com/minhalvp/android-mcp-server
- github.com/hyperb1iss/droidmind
- github.com/JuanCF/scrcpy-mcp
- mobilerun.ai, mobilerun.ai/mcp, mobilerun.ai/pricing and github.com/droidrun/mobilerun
Background on how these servers capture and control a phone, and why a live stream differs from screenshot polling, is in our guide to the Android screen MCP server. For what ScreenSync MCP stores and where, read the data policy.
Try ScreenSync MCP on your own phone
Free, local-first, phone and browser in one hub, no per-command quota.