Mobile Next
A Model Context Protocol server that enables scalable mobile automation through a platform-agnostic interface for iOS and Android devices, allowing agents and LLMs to interact with mobile applications using accessibility snapshots or coordinate-based
What is Mobile Next?
Mobile Next is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to model context protocol server that enables scalable mobile automation through a platform-agnostic interface for ios and android devices, allowing agents and llms to interact with mobile applications u...
A Model Context Protocol server that enables scalable mobile automation through a platform-agnostic interface for iOS and Android devices, allowing agents and LLMs to interact with mobile applications using accessibility snapshots or coordinate-based
This server falls under the Browser Automation category on MCPgee, the world's largest MCP server directory with 33,000+ servers.
Features
- mobile_use_default_device
- mobile_list_available_devices
- mobile_use_device
- mobile_list_apps
- mobile_launch_app
Use Cases
Maintainer
Works with
Installation
NPM
npx -y @mobilenext/mobile-mcpManual Installation
npx -y @mobilenext/mobile-mcpConfiguration
Configuration Details
claude_desktop_config.json
Performance
Response Metrics
Resource Usage
How to Set Up and Use Mobile Next
Mobile Next MCP Server is a platform-agnostic MCP server that enables AI agents and LLMs to control iOS simulators, iOS real devices, Android emulators, and physical Android devices through a single unified interface. It exposes tools for device management, app installation and launching, screen capture, accessibility-tree inspection, gesture simulation (tap, swipe, long-press, double-tap), text input, hardware button presses, and URL opening — letting agents drive complete mobile app workflows without writing platform-specific automation code. QA engineers and developers use it to automate mobile regression tests, onboarding flows, and multi-app workflows by describing the steps to Claude in plain language.
Prerequisites
- Node.js 18+ and npx
- For iOS: Xcode with iOS simulators installed, or a real device connected and trusted
- For Android: Android Studio with ADB installed, an emulator running, or a physical device connected via USB with debugging enabled
- An MCP-compatible client such as Claude Desktop, Claude Code, or Cursor
Install via Claude Code CLI (quickest method)
Use the Claude Code CLI to add the mobile-mcp server in a single command. This handles the config automatically.
claude mcp add mobile-mcp -- npx -y @mobilenext/mobile-mcp@latestOr configure manually in your MCP client config
Add the server directly to your claude_desktop_config.json or equivalent config file for other MCP clients.
{
"mcpServers": {
"mobile-mcp": {
"command": "npx",
"args": ["-y", "@mobilenext/mobile-mcp@latest"]
}
}
}Start your iOS simulator or Android emulator
For iOS, open a simulator from Xcode > Open Simulator. For Android, start an AVD from Android Studio's Virtual Device Manager, or connect a physical device via USB.
List available devices
Restart your MCP client. In Claude, ask it to list available devices. The server will enumerate all connected simulators and emulators.
Disable telemetry (optional)
To disable anonymous usage telemetry, set the environment variable in your MCP config.
{
"mcpServers": {
"mobile-mcp": {
"command": "npx",
"args": ["-y", "@mobilenext/mobile-mcp@latest"],
"env": {
"MOBILEMCP_DISABLE_TELEMETRY": "1"
}
}
}
}Mobile Next Examples
Client configuration
Full configuration block for Claude Desktop at ~/Library/Application Support/Claude/claude_desktop_config.json.
{
"mcpServers": {
"mobile-mcp": {
"command": "npx",
"args": ["-y", "@mobilenext/mobile-mcp@latest"],
"env": {
"MOBILEMCP_DISABLE_TELEMETRY": "1"
}
}
}
}Prompts to try
After connecting, use these prompts to automate mobile workflows through Claude.
- "List all connected devices and simulators."
- "Launch the Settings app on the iPhone 15 simulator."
- "Take a screenshot of the current screen on my Android device."
- "Open the App Store on the iOS simulator, search for 'Notion', and tap the Get button."
- "Swipe left three times on the onboarding screen and then tap the 'Get Started' button."Troubleshooting Mobile Next
No devices listed when asking Claude to list available devices
Ensure a simulator or emulator is already running before the MCP server starts. For iOS, open Xcode > Open Simulator and boot a device. For Android, start an AVD in Android Studio or connect a physical device with USB debugging enabled and run 'adb devices' to verify connectivity.
iOS real device automation fails with 'device not trusted' error
On the iPhone, go to Settings > General > VPN & Device Management and trust the developer certificate associated with your Mac. Also ensure the device is unlocked and that you have accepted the 'Trust This Computer?' prompt.
Taps land in the wrong place on screen
Coordinate-based taps depend on the device's screen resolution and scale factor. Prefer using accessibility-snapshot-based interactions by asking Claude to 'find the button by its label' rather than specifying raw coordinates, which are more reliable across different device sizes.
Frequently Asked Questions about Mobile Next
What is Mobile Next?
Mobile Next is a Model Context Protocol (MCP) server that model context protocol server that enables scalable mobile automation through a platform-agnostic interface for ios and android devices, allowing agents and llms to interact with mobile applications using accessibility snapshots or coordinate-based It connects AI assistants to external tools and data sources through a standardized interface.
How do I install Mobile Next?
Install via npm with the command: npx -y @mobilenext/mobile-mcp. Then add the server configuration to your AI client's JSON config file (e.g., claude_desktop_config.json or .cursor/mcp.json).
Which AI clients work with Mobile Next?
Mobile Next works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.
Is Mobile Next free to use?
Yes, Mobile Next is open source and available under the Apache 2.0 license. You can use it freely in both personal and commercial projects.
Mobile Next Alternatives — Similar Browser Automation Servers
Looking for alternatives to Mobile Next? Here are other popular browser automation servers you can use with Claude, Cursor, and VS Code.
Chrome DevTools MCP
★ 40.6kAI-powered Chrome automation server with natural language element detection. Control Chrome browser through MCP protocol for testing, debugging, and performance analysis. Features 91% accuracy in element location, works with free AI models, and suppo
UI TARS Desktop
★ 34.9k📇 🏠 - Browser automation capabilities using Puppeteer, both support local and remote browser connection.
Playwright
★ 32.8kA production-ready browser automation server that enables AI assistants to interact with web pages using tools for navigation, element interaction, and data extraction. It features a built-in Inspector UI and robust crash recovery for reliable automa
Page Agent
★ 18.0kJavaScript in-page GUI agent. Control web interfaces with natural language.
Chrome
★ 11.7kAn extension-based MCP server that enables AI assistants to control your browser, leveraging existing sessions and login states for automation and content analysis. It provides over 20 tools for semantic tab search, interactive element manipulation,
LAMDA
★ 7.8kThe most powerful Android RPA agent framework, next generation mobile automation.
Browse More Browser Automation MCP Servers
Explore all browser automation servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.
Set Up Mobile Next in Your Editor
Choose your AI client for step-by-step setup instructions.
Quick Config Preview
Add this to your claude_desktop_config.json or .cursor/mcp.json
Ready to use Mobile Next?
Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.