Enable AI agents to operate iOS and Android apps directly
Imagine telling an AI in the terminal to open an app and log in, and watching it view the simulator or physical phone screen to perform taps and inputs. This tool is an MCP server that allows AI agents to interact with mobile devices. You can run app automation tests or extract data using natural language instructions without needing platform-specific expertise.
Efficient control based on accessibility trees
The server reads the app's native accessibility tree to identify screen elements. It does not use vision models or image tokens, resulting in faster processing and lower costs. It switches to screenshots and coordinate-based taps only when accessibility information is insufficient. This structure allows the AI to recognize actual UI elements on the screen as structured data, reducing uncertainty.
A single interface across platforms
It controls iOS simulators, Android emulators, and physical devices connected via USB with the same set of tools. You do not need knowledge of platform-specific testing frameworks like XCUITest or Espresso. It supports full device control, including taps, swipes, gestures, app installation and termination, screen recording, hardware button manipulation, deep links, and screen orientation changes. It integrates immediately with MCP-compatible clients such as Claude Code, Codex, and Cursor.
From agent sessions to CI tests
You can convert flows performed by AI agents into deterministic tests. Using Mobilewright, you can evolve scenarios written in an agent session into repeatable tests integrated into CI/CD pipelines. Additionally, through Mobile Next Cloud, you can reserve actual iOS and Android devices in the cloud without local setup, scaling to hundreds of devices. It supports Streamable HTTP server mode, allowing it to operate statelessly in host environments like Smithery.
Environment requirements to check before running
To use this tool, you must have Node.js v20 or higher, Xcode command line tools, and Android Platform Tools installed. Physical iOS devices require a USB connection and trust configuration, while physical Android devices require USB debugging to be enabled and authorized. Telemetry is collected by default, so you can disable it by setting the MOBILEMCP_DISABLE_TELEMETRY environment variable. If you use the HTTP server mode, it is safer to set MOBILEMCP_AUTH to enforce Bearer token authentication.