English Français العربية

AutoMobile

Official registry Other

Mobile device interaction automation via MCP

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @kaeawc/auto-mobile
Claude Code 
claude mcp add automobile -- bunx -y @kaeawc/auto-mobile@0.0.67
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "automobile": {
            "command": "bunx",
            "args": [
                "-y",
                "@kaeawc/auto-mobile@0.0.67"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. AutoMobile
  2. How it works
  3. Get Started
  4. Documentation
  5. Contributing

AutoMobile

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

Explore and Test
TaskWhat it does
Explore app UXNavigate your app, discover screens, map user flows, identify confusing interactions
Reproduce bugsPaste a bug report and get exact reproduction steps with screenshots
Create UI testsDescribe test scenarios in plain English, get executable test plans
Measure startup timeProfile cold and warm launch performance
Check scroll performanceDetect jank and dropped frames

How it works

  • 🤖 Fast UX Inspection Kotlin Accessibility Service and Swift XCTestService to enable fast, accurate observations. 10x faster than the next fastest observation toolkit.
  • 🦾 Full Touch Injection Tap, Swipe, Pinch, Drag & Drop, Shake with automatic element targeting.
  • ♻️ Tool Feedback Observations drive the interaction loop for all tool calls.
  • 🧪 Test Execution Kotlin JUnitRunner & Swift XCTestRunner execute tests natively handling device pooling, multi-device tests, and automatically optimizing test timing.

Get Started

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.

Documentation

Contributing

Frequently asked questions

What is AutoMobile?

Mobile device interaction automation via MCP

How do I install AutoMobile?

It runs on your machine. In Claude Code: claude mcp add automobile -- bunx -y @kaeawc/auto-mobile@0.0.67. For other clients, paste the JSON configuration from this page into their MCP settings.

Does AutoMobile need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is AutoMobile open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains AutoMobile?

It is published by kaeawc. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.