claude-in-mobile MCP
An MCP server that lets an agent drive Android, the iOS Simulator, HarmonyOS, Aurora, desktop and browser, take screenshots and debug apps
- 382 ★ on the repository
- Last commit
Broad access
Why this level
- The server runs shell commands on the device, reads and copies files and logs and grants permissions to apps
- The agent sees a screen that may hold personal data and codes from messages
Install
- Works in
Manual install
npm i -g claude-in-mobileThe all-in-one edition with every platform. The modular one installs as `npm i -g mcp-devices` plus platform packages.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The server runs shell commands on the device, reads and copies files and logs and grants permissions to apps
- The agent sees a screen that may hold personal data and codes from messages
This is third-party code. Review the repository files before installing.
What it does
claude-in-mobile is an MCP server that does for mobile devices and desktop what Claude in Chrome does for the browser. An agent takes screenshots, taps, swipes, types text, launches apps, reads the UI tree, runs shell commands, reads logs, grants permissions and copies files. The project ships in two editions from one codebase. The `claude-in-mobile` package installs every platform at once, while `mcp-devices` is a slim base that platforms are added to separately. Supported are Android through `adb`, iOS through `xcrun` and Xcode, HarmonyOS Next through `hdc`, Aurora OS, desktop on Compose Multiplatform and the Chrome browser. Beyond control there is debugging of running apps: breakpoints, stepping, variable inspection and expression evaluation through JDWP on Android and LLDB on iOS. Testing covers visual screenshot comparison, accessibility checks, performance measurements and sensor and network simulation. About 20 built-in tool modules turn on and off through the `MOBILE_PROFILE` profile or by the agent's own command. For shell use there is a separate native Rust CLI, `mcp-devices-cli`.
Who it is for. For mobile developers and testers who want Claude Code to check an app on an emulator or a real phone, take screenshots, run scenarios and debug.
Good fit when
- You need to walk through a scenario in an app on an Android emulator and capture each screen
- You want to check interface accessibility and compare screenshots before and after a change
- The agent should set a breakpoint in a running app and inspect variable values
- One tool must handle Android, the iOS Simulator and a desktop app window
- You need logs and files pulled off a device or a permission granted to an app without manual `adb` commands
Not a fit when
- You need iOS on a real iPhone: the iOS Simulator through `xcrun` is stated and real iPhones are not listed among the platforms
- The machine has no Android SDK with `adb` or Xcode: each platform needs its own tools, and `mcp-devices doctor` checks readiness
- The device holds personal data and you are not ready to supervise the agent: the server runs shell commands and reads files
- You need only web testing: the web profile keeps the base and browser, and the full set of mobile platforms is pointless
Example request
Take a screenshot of the connected Android device, open the app, go through the sign-in screen and show the UI tree of the last screen.MCP
- Transport
- stdio
- Authentication
- not required
Environment variables
MOBILE_PROFILE- Module visibility profile: full, web or minimal.
Limitations
Node.js 20 or newer is required. Each platform needs its own tools: Android uses `adb`, iOS runs on macOS with Xcode through `xcrun`, web mode needs Chrome, desktop needs a JDK, Aurora uses `flutter-aurora` and HarmonyOS Next uses `hdc`. The `mcp-devices doctor` command checks readiness.
In the modular edition no platforms are loaded by default: after installing the base add a package like `@mcp-devices/plugin-android`, run `mcp-devices install android` and restart the client. In the `claude-in-mobile` edition all platforms are on at once. The debug plugin is enabled separately with `mcp-devices plugin enable debug`.
Modules other than `device` and `screen` can be hidden with the `MOBILE_PROFILE` profile set to full, web or minimal, which saves client context. The repository metadata states no license, so clarify it with the author before company use. The install from Russia was not checked when this card was prepared.
How to disable. Delete the mobile block from the MCP client config and restart the client. Packages come off with `npm uninstall -g claude-in-mobile`, or `npm uninstall -g mcp-devices` for the modular edition.
FAQ
How do I install claude-in-mobile for Claude Code?
Run `npm i -g claude-in-mobile`, add a server with the `mcp-devices` command to the MCP config and restart the client. Then you can ask: take a screenshot of the Android device. `mcp-devices doctor` checks platform readiness.
How does claude-in-mobile differ from mcp-devices?
They are two editions of one tool. `claude-in-mobile` installs every platform at once, while `mcp-devices` is a slim base with separate platform packages. The toolset and client setup are the same.
Which platforms does claude-in-mobile support?
Android through `adb`, the iOS Simulator through `xcrun`, HarmonyOS Next through `hdc`, Aurora OS, desktop on Compose Multiplatform and the Chrome browser. Each platform has its own module in the repository docs.
Can claude-in-mobile debug apps?
Yes, the debug plugin sets breakpoints, steps through code, shows variables and evaluates expressions: through JDWP on Android and LLDB on iOS. It is enabled with `mcp-devices plugin enable debug`.
How do I reduce the number of tools the agent sees?
Start the server with the `MOBILE_PROFILE` variable: full shows all 20 modules, web keeps the base and browser, minimal only device and screen. Modules also switch on at runtime with the device tool and the enable_module action.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server to drive iOS and Android: simulators, emulators and real devices via accessibility trees and screenshots
mobilecli drives iOS and Android devices, emulators and apps from the terminal, and its skill teaches Claude Code how to use it
An MCP server that installs on a jailbroken iPhone and gives an agent 46 tools: taps, screenshots, OCR, apps, files and logs
An MCP server that drives an Android device over ADB: app navigation, input and automated tests
Android MCP Server: control Android through ADB
Android MCP Server
A Python MCP server: the agent takes screenshots of an Android device, reads clickable interface elements and runs ADB commands
Appium MCP
appium-mcp
An agent opens sessions on emulators and real devices, finds elements by description and writes Java tests via the Appium server.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| claude-in-mobile (this card) | no | not required | 382 | |
| Mobile MCP | no | not required | 10,325 | a server for iOS and Android covering simulators, emulators and real devices |
| Android MCP | no | not required | 917 | an MCP server for Android only: app navigation over ADB |
| iOS Simulator MCP Server | no | not required | 2,209 | a server for the iOS Simulator only: taps, swipes and text input |
README in short
The README opens by explaining the two editions and that the old install stays unchanged. Then come a three-step install, a platform table with requirements and guide links, a short list of abilities and instructions for moving from the all-in-one edition to the modular one. The detailed tool catalog lives in docs/modules.