Auto Mobile MCP server
{
"mcpServers": {
"jasonpearson-auto-mobile": {
"command": "npx",
"args": [
"-y",
"@kaeawc/auto-mobile@latest"
]
}
}
}{
"mcpServers": {
"jasonpearson-auto-mobile": {
"command": "npx",
"args": [
"-y",
"@kaeawc/auto-mobile@latest"
]
}
}
}{
"mcpServers": {
"jasonpearson-auto-mobile": {
"command": "npx",
"args": [
"-y",
"@kaeawc/auto-mobile@latest"
]
}
}
}{
"servers": {
"jasonpearson-auto-mobile": {
"command": "npx",
"args": [
"-y",
"@kaeawc/auto-mobile@latest"
]
}
}
}{
"mcpServers": {
"jasonpearson-auto-mobile": {
"command": "npx",
"args": [
"-y",
"@kaeawc/auto-mobile@latest"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y @kaeawc/auto-mobileversion 0.0.67
What it does
AutoMobile is an MCP server that enables AI agents to control Android and iOS devices through natural language commands. It provides fast UX inspection, touch interaction, and test execution capabilities for mobile app testing and automation.
- Navigate mobile apps and map user flows to understand app structure and identify confusing interactions.
- Reproduce bugs by following bug report descriptions and capturing screenshots of each reproduction step.
- Execute UI tests written in plain English or native test frameworks (JUnit/XCTest) across multiple devices.
Tools this server exposes
| Tool | Does |
|---|---|
| tap | Tap elements on the mobile device screen with automatic element targeting. |
| swipe | Perform swipe gestures on the mobile device screen. |
| pinch | Perform pinch gestures on the mobile device screen. |
| drag | Drag and drop elements on the mobile device screen. |
| shake | Trigger shake gestures on the mobile device. |
| observe | Capture the current state and UI hierarchy of the app screen with fast accessibility inspection. |
| run_test | Execute native JUnit or XCTest test files on connected Android or iOS devices. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.