Runs on your machine from its package; the steps are below.

At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y @kaeawc/auto-mobile
MCP client config
{
"mcpServers": {
"automobile": {
"command": "npx",
"args": [
"-y",
"@kaeawc/auto-mobile"
]
}
}
}

AutoMobile lets AI agents control your mobile devices using natural language. Tell an AI what you want to do, and it interacts with your Android or iOS app.
It can do all this by being an MCP server that uses standard platform tools like adb & simctl paired with additional Kotlin & Swift libraries and apps. All components are open source. The point is to provide mobile engineers with AI workflow tools to perform UX deep dives, reproduce bugs, and run automated tests.
An AI agent navigating to the Clock app, creating a new alarm
An AI agent searching YouTube and browsing results
| Task | What it does |
|---|---|
| Explore app UX | Navigate your app, discover screens, map user flows, identify confusing interactions |
| Reproduce bugs | Paste a bug report and get exact reproduction steps with screenshots |
| Create UI tests | Describe test scenarios in plain English, get executable test plans |
| Measure startup time | Profile cold and warm launch performance |
| Check scroll performance | Detect jank and dropped frames |
You can use our interactive installer to step through all host platform requirements and configuration options. It checks host dependencies, optionally downloads Android or iOS developer tools, and configured the MCP daemon.
curl -fsSL https://raw.githubusercontent.com/kaeawc/auto-mobile/refs/heads/main/scripts/install.sh | bash
Prefer Homebrew for the CLI:
brew install kaeawc/tap/auto-mobile
or follow the installation guide.