AutoMobile MCP
AutoMobile lets an agent control Android and iOS devices in plain language: explore an app, reproduce bugs and write UI tests
- 56 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The agent controls a connected device or emulator: it taps, types and installs apps
- Helper UI observation services are installed on the device
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/automobileDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent controls a connected device or emulator: it taps, types and installs apps
- Helper UI observation services are installed on the device
This is third-party code. Review the repository files before installing.
What it does
AutoMobile is an MCP server that uses standard platform tools, `adb` and `simctl`, together with Kotlin and Swift libraries. You describe a task in words and the agent taps, scrolls, types and switches apps on a real device, emulator or simulator. UI observations come from a Kotlin accessibility service and a Swift XCTestService, and touches cover tap, swipe, pinch, drag and shake. Typical tasks: exploring an app's screens and flow map, reproducing a bug from a report with screenshots, creating UI tests in plain language and running them through JUnitRunner or XCTestRunner, measuring cold and warm start time and finding scroll jank. All components are open source.
Who it is for. Mobile developers and QA engineers who want to hand app exploration and testing on Android and iOS to an agent.
Good fit when
- The agent walks through the app and maps screens and confusing parts of the interface
- A bug from a report is reproduced step by step with screenshots
- A plain-language scenario becomes an executable UI test
- Cold start time and scroll jank are measured
Not a fit when
- The app cannot run on an emulator or device
- You only need a scripted test with no agent involved
- You have no access to Android SDK or Xcode tools
Example request
Open the app on the emulator, go through signup, find screens with confusing navigation and measure cold start timeMCP
- Transport
- stdio
- Authentication
- not required
Limitations
Platform tools are required: the Android SDK with `adb` for Android and Xcode with `simctl` for iOS. The interactive installer checks dependencies, can download tools and configures the MCP daemon, but it runs through `curl | bash`, so read the script first. Auxiliary UI observation services are installed on the device. The agent gets full control of the connected device, including app installation and text entry. Tests have separate runners in Kotlin and Swift.
How to disable. Uninstall the package (`brew uninstall auto-mobile`), remove the server from the client and delete the helper apps from the device or emulator.
FAQ
How do I install AutoMobile?
Through Homebrew `brew install kaeawc/tap/auto-mobile` or the interactive installer `curl -fsSL https://raw.githubusercontent.com/kaeawc/auto-mobile/refs/heads/main/scripts/install.sh | bash`. Details are in the installation guide.
How do I connect it to Claude Code?
Run `/plugin marketplace add kaeawc/auto-mobile`, then `/plugin install auto-mobile@auto-mobile-marketplace`.
Which platforms are supported?
Android through `adb` and iOS through `simctl` on emulators, simulators and devices. Observations use a Kotlin accessibility service and a Swift XCTestService.
Which touches are available?
Tap, swipe, pinch, drag and shake with automatic element targeting.
Can I write tests?
Yes, a scenario is described in plain language and the result runs through the Kotlin JUnitRunner or the Swift XCTestRunner, with device pooling.
Discussion
No questions or reviews yet.
Related
MCP serversMobile Device MCP controls iOS and Android: taps, typing, screenshots and the element tree, with several devices at once
An MCP server to drive iOS and Android: simulators, emulators and real devices via accessibility trees and screenshots
The MobAI MCP server: an agent controls Android and iOS devices, emulators and simulators through one DSL scenario tool.
An MCP server that drives an Android device over ADB: app navigation, input and automated tests
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.
A terminal agent for phones: state a goal in plain words and it reads the screen, then decides where to tap and what to type
README in short
The README presents AutoMobile as a toolset for AI control of mobile devices and shows the main tasks: exploration, bug reproduction, UI tests and measurements. How it works, installation and documentation links follow.