AutoMobile is a mobile automation MCP server for UI testing and development workflow automation, primarily supporting Android with iOS planned.
Device Management
List, start, kill, and set active devices; list available device images
Rotate orientation, shake device, configure device modes (exploration/test authoring)
App Management
Launch (with optional cold boot/data clearing), terminate, and install apps
List installed apps, open URLs, query deep links and intent filters
UI Interaction
Observe the current view hierarchy on screen
Tap (single, double, long press), swipe on elements or full screen, scroll within containers
Open system tray, navigate home, open recent apps, press hardware buttons (home, back, menu, power, volume)
Text Input
Input text, clear text, select all text, trigger IME actions (done, next, search, send, etc.)
Intent Handling
Detect and dismiss system intent chooser dialogs (always, just once, or a specific app)
Demo Mode
Enable/disable demo mode with customizable status bar indicators for consistent screenshots
Configuration & Dependencies
Set app source directories for source mapping, retrieve/reset configs
Install and verify platform dependencies for Android/iOS automation
Provides UI testing and automation capabilities for Android applications, allowing for interaction with app elements, view hierarchy analysis, and source mapping to identify rendered code.
Mentioned as a planned future platform for mobile automation, though not currently supported.
The AutoMobile tool is published on npm, allowing users to install and use the mobile automation toolset.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AutoMobiletake a screenshot of the current screen and save it as test_failure.png"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AutoMobile
⚠️ PROJECT ARCHIVED
AutoMobile is no longer maintained or supported by Zillow. Zillow does not provide warranties or support for this project.
This repository has been archived and is read-only. For continued development and support, please see the community-maintained fork by Jason Pearson:
🔗
AutoMobile is a set of tools for mobile automation. You can use it for UI testing or as a development workflow assistant.
The first platform supported is Android with plans to extend to iOS.
How it works
🔧 Powerful MCP Server: AutoMobile provides comprehensive actions through MCP tool calls with a fast observations to drive the interaction loop.
🗺️ Source Mapping: Combining project path config with deep view hierarchy analysis we know exactly what code is being rendered.
✍️ Automated Test Authoring: When used in test authoring mode AutoMobile will write tests for you. It is the only way it writes tests.
🧪 Test Execution - Run tests locally or on CI without extra infrastructure.
📱 Device Management: Multi-device support with emulator control and app lifecycle management.
All together you get a system that looks like this:
Related MCP server: UIAutomator2 MCP Server
Documentation
💻 Installation & Getting Started - AutoMobile is published on npm and we have instructions for agents we've tested with.
📝 Change Log - coming soon
Contributing
Contributing - coming soon
Acknowledgement
By continuing to use AutoMobile, you acknowledge and agree to the warnings and responsible use requirements.
Resources
Looking for Admin?
Admins can modify the Dockerfile, update the server description, and track usage metrics. If you are the server author, to access the admin panel.