Mobile Next MCP Server
OfficialMobile Next - MCP server for Mobile Development and Automation | iOS, Android, Simulator, Emulator, and Real Devices
This is a Model Context Protocol (MCP) server that enables scalable mobile automation, development through a platform-agnostic interface, eliminating the need for distinct iOS or Android knowledge. You can run it on emulators, simulators, and real devices (iOS and Android). This server allows Agents and LLMs to interact with native iOS/Android applications and devices through structured accessibility snapshots or coordinate-based taps based on screenshots.
https://github.com/user-attachments/assets/bb084777-beb3-4930-ae6f-8d3fe694ddde
🚀 Mobile MCP Roadmap: Building the Future of Mobile
Join us on our journey as we continuously enhance Mobile MCP! Check out our detailed roadmap to see upcoming features, improvements, and milestones. Your feedback is invaluable in shaping the future of mobile automation.
Main use cases
How we help to scale mobile automation:
📲 Native app automation (iOS and Android) for testing or data-entry scenarios.
📝 Scripted flows and form interactions without manually controlling simulators/emulators or real devices (iPhone, Samsung, Google Pixel etc)
🧭 Automating multi-step user journeys driven by an LLM
👆 General-purpose mobile application interaction for agent-based frameworks
🤖 Enables agent-to-agent communication for mobile automation usecases, data extraction
Main Features
🚀 Fast and lightweight: Uses native accessibility trees for most interactions, or screenshot based coordinates where a11y labels are not available.
🤖 LLM-friendly: No computer vision model required in Accessibility (Snapshot).
🧿 Visual Sense: Evaluates and analyses what's actually rendered on screen to decide the next action. If accessibility data or view-hierarchy coordinates are unavailable, it falls back to screenshot-based analysis.
📊 Deterministic tool application: Reduces ambiguity found in purely screenshot-based approaches by relying on structured data whenever possible.
📺 Extract structured data: Enables you to extract structred data from anything visible on screen.
🎯 Platform Support
Platform | Supported |
iOS Real Device | ✅ |
iOS Simulator | ✅ |
Android Real Device | ✅ |
Android Emulator | ✅ |
Related MCP server: Mobile Next MCP
🔧 Available MCP Tools
For detailed implementation and parameter specifications, see
src/server.ts
Device Management
mobile_list_available_devices- List all available devices (simulators, emulators, and real devices)mobile_get_screen_size- Get the screen size of the mobile device in pixelsmobile_get_orientation- Get the current screen orientation of the devicemobile_set_orientation- Change the screen orientation (portrait/landscape)
App Management
mobile_list_apps- List all installed apps on the devicemobile_launch_app- Launch an app using its package namemobile_terminate_app- Stop and terminate a running appmobile_install_app- Install an app from file (.apk, .ipa, .app, .zip)mobile_uninstall_app- Uninstall an app using bundle ID or package name
Screen Interaction
mobile_take_screenshot- Take a screenshot to understand what's on screenmobile_save_screenshot- Save a screenshot to a filemobile_list_elements_on_screen- List UI elements with their coordinates and propertiesmobile_click_on_screen_at_coordinates- Click at specific x,y coordinatesmobile_double_tap_on_screen- Double-tap at specific coordinatesmobile_long_press_on_screen_at_coordinates- Long press at specific coordinatesmobile_swipe_on_screen- Swipe in any direction (up, down, left, right)
Input & Navigation
mobile_type_keys- Type text into focused elements with optional submitmobile_press_button- Press device buttons (HOME, BACK, VOLUME_UP/DOWN, ENTER, etc.)mobile_open_url- Open URLs in the device browser
Platform Support
iOS: Simulators and real devices via native accessibility and WebDriverAgent
Android: Emulators and real devices via ADB and UI Automator
Cross-platform: Unified API works across both iOS and Android
🏗️ Mobile MCP Architecture
📚 Wiki page
More details in our wiki page for setup, configuration and debugging related questions.
Installation and configuration
Standard config works in most of the tools:
{
"mcpServers": {
"mobile-mcp": {
"command": "npx",
"args": ["-y", "@mobilenext/mobile-mcp@latest"]
}
}
}Add via the Amp VS Code extension settings screen or by updating your settings.json file:
"amp.mcpServers": {
"mobile-mcp": {
"command": "npx",
"args": [
"@mobilenext/mobile-mcp@latest"
]
}
}Amp CLI:
Run the following command in your terminal:
amp mcp add mobile-mcp -- npx @mobilenext/mobile-mcp@latestTo setup Cline, just add the json above to your MCP settings file.
Use the Claude Code CLI to add the Mobile MCP server:
claude mcp add mobile-mcp -- npx -y @mobilenext/mobile-mcp@latestFollow the MCP install guide, use json configuration above.
Use the Codex CLI to add the Mobile MCP server:
codex mcp add mobile-mcp npx "@mobilenext/mobile-mcp@latest"Alternatively, create or edit the configuration file ~/.codex/config.toml and add:
[mcp_servers.mobile-mcp]
command = "npx"
args = ["@mobilenext/mobile-mcp@latest"]For more information, see the Codex MCP documentation.
Use the Copilot CLI to interactively add the Mobile MCP server:
/mcp addYou can edit the configuration file ~/.copilot/mcp-config.json and add:
{
"mcpServers": {
"mobile-mcp": {
"type": "local",
"command": "npx",
"tools": [
"*"
],
"args": [
"@mobilenext/mobile-mcp@latest"
]
}
}
}For more information, see the Copilot CLI documentation.
Click the button to install:
Or install manually:
Go to Cursor Settings -> MCP -> Add new MCP Server. Name to your liking, use command type with the command npx -y @mobilenext/mobile-mcp@latest. You can also verify config or add command like arguments via clicking Edit.
Use the Gemini CLI to add the Mobile MCP server:
gemini mcp add mobile-mcp npx -y @mobilenext/mobile-mcp@latestClick the button to install:
Or install manually:
Go to Advanced settings -> Extensions -> Add custom extension. Name to your liking, use type STDIO, and set the command to npx -y @mobilenext/mobile-mcp@latest. Click "Add Extension".
Follow the MCP Servers documentation. For example in .kiro/settings/mcp.json:
{
"mcpServers": {
"mobile-mcp": {
"command": "npx",
"args": [
"@mobilenext/mobile-mcp@latest"
]
}
}
}Follow the MCP Servers documentation. For example in ~/.config/opencode/opencode.json:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mobile-mcp": {
"type": "local",
"command": [
"npx",
"@mobilenext/mobile-mcp@latest"
],
"enabled": true
}
}
}Open Qodo Gen chat panel in VSCode or IntelliJ → Connect more tools → + Add new MCP → Paste the standard config above.
Click Save.
Open Windsurf settings, navigate to MCP servers, and add a new server using the command type with:
npx @mobilenext/mobile-mcp@latestOr add the standard config under mcpServers in your settings as shown above.
SSE Server Mode
By default, Mobile MCP runs over stdio. To start an SSE server instead, use the --listen flag:
npx @mobilenext/mobile-mcp@latest --listen 3000This binds to localhost:3000. To bind to a specific interface:
npx @mobilenext/mobile-mcp@latest --listen 0.0.0.0:3000Then configure your MCP client to connect to http://<host>:3000/mcp.
Authorization
To require Bearer token authorization on the SSE server, set the MOBILEMCP_AUTH environment variable:
MOBILEMCP_AUTH=my-secret-token npx @mobilenext/mobile-mcp@latest --listen 3000When set, all requests must include the header Authorization: Bearer my-secret-token.
🛠️ How to Use 📝
After adding the MCP server to your IDE/Client, you can instruct your AI assistant to use the available tools. For example, in Cursor's agent mode, you could use the prompts below to quickly validate, test and iterate on UI intereactions, read information from screen, go through complex workflows. Be descriptive, straight to the point.
✨ Example Prompts
Workflows
You can specifiy detailed workflows in a single prompt, verify business logic, setup automations. You can go crazy:
Search for a video, comment, like and share it.
Find the video called " Beginner Recipe for Tonkotsu Ramen" by Way of
Ramen, click on like video, after liking write a comment " this was
delicious, will make it next Friday", share the video with the first
contact in your whatsapp list.Download a successful step counter app, register, setup workout and 5-star the app
Find and Download a free "Pomodoro" app that has more than 1k stars.
Launch the app, register with my email, after registration find how to
start a pomodoro timer. When the pomodoro timer started, go back to the
app store and rate the app 5 stars, and leave a comment how useful the
app is.Search in Substack, read, highlight, comment and save an article
Open Substack website, search for "Latest trends in AI automation 2025",
open the first article, highlight the section titled "Emerging AI trends",
and save article to reading list for later review, comment a random
paragraph summary.Reserve a workout class, set timer
Open ClassPass, search for yoga classes tomorrow morning within 2 miles,
book the highest-rated class at 7 AM, confirm reservation,
setup a timer for the booked slot in the phoneFind a local event, setup calendar event
Open Eventbrite, search for AI startup meetup events happening this
weekend in "Austin, TX", select the most popular one, register and RSVP
yes to the event, setup a calendar event as a reminder.Check weather forecast and send a Whatsapp/Telegram/Slack message
Open Weather app, check tomorrow's weather forecast for "Berlin", and
send the summary via Whatsapp/Telegram/Slack to contact "Lauren Trown",
thumbs up their response.Schedule a meeting in Zoom and share invite via email
Open Zoom app, schedule a meeting titled "AI Hackathon" for tomorrow at
10AM with a duration of 1 hour, copy the invitation link, and send it via
Gmail to contacts "team@example.com".More prompt examples can be found here.
Prerequisites
What you will need to connect MCP with your agent and mobile devices:
node.js v22+
MCP supported foundational models or agents, like Claude MCP, OpenAI Agent SDK, Copilot Studio
Simulators, Emulators, and Real Devices
When launched, Mobile MCP can connect to:
iOS Simulators on macOS/Linux
Android Emulators on Linux/Windows/macOS
iOS or Android real devices (requires proper platform tools and drivers)
Make sure you have your mobile platform SDKs (Xcode, Android SDK) installed and configured properly before running Mobile Next Mobile MCP.
Telemetry
Mobile MCP collects anonymous usage telemetry via PostHog. To disable it, set the MOBILEMCP_DISABLE_TELEMETRY environment variable:
MOBILEMCP_DISABLE_TELEMETRY=1 npx @mobilenext/mobile-mcp@latestFor json configurations:
{
"mcpServers": {
"mobile-mcp": {
"command": "npx",
"args": ["-y", "@mobilenext/mobile-mcp@latest"],
"env": {
"MOBILEMCP_DISABLE_TELEMETRY": "1"
}
}
}
}Running in "headless" mode on Simulators/Emulators
When you do not have a real device connected to your machine, you can run Mobile MCP with an emulator or simulator in the background.
For example, on Android:
Start an emulator (avdmanager / emulator command).
Run Mobile MCP with the desired flags
On iOS, you'll need Xcode and to run the Simulator before using Mobile MCP with that simulator instance.
xcrun simctl listxcrun simctl boot "iPhone 16"
Thanks to all contributors ❤️
We appreciate everyone who has helped improve this project.
Available Tools
36 toolsget_more_toolsGet More ToolsARead-only
Only call this when none of the other tools can do what you need on a mobile device, or for mobile testing or mobile app development. Do not call it for tasks unrelated to mobile, or when another tool already covers the task. The context is sent to the mobile-mcp developers, so never include PII, secrets, credentials or other private information in it.
Inputs: context (required).
mobile_allocate_remote_deviceAllocate Remote DeviceA
Reserve a physical device from the remote cloud fleet for exclusive use, returning a device identifier usable with the other mobile_* tools. Unlike local devices, a remote device is a shared and billed resource borrowed for the session - never call this silently. If no local device is available, offer a remote device to the user and call this only after they agree. Requires mobile_login_to_cloud_provider to have been called first; if this fails with an authentication error, call that tool then retry. Use mobile_list_remote_devices first to see which names and versions actually exist in the fleet before filtering by them. Release the device with mobile_release_remote_device once the whole task is finished - releasing wipes the device's state, so do not release and reallocate between steps of the same task just to be tidy.
Inputs: platform (required), name, type, wait, +2 more.
mobile_batch_commandsBatch CommandsADestructive
Run multiple tools in sequence in a single call, e.g. click, type, click, type. Use this to fill forms or perform multi-step flows without round-trips. The device argument is applied to every step unless a step provides its own. Tools allowed as steps: get_more_tools, mobile_list_available_devices, mobile_login_to_cloud_provider, mobile_list_remote_devices, mobile_allocate_remote_device, mobile_release_remote_device, mobile_list_apps, mobile_get_foreground_app, mobile_launch_app, mobile_terminate_app, mobile_clear_app_data, mobile_install_app, mobile_uninstall_app, mobile_get_screen_size, mobile_click_on_screen_at_coordinates, mobile_double_tap_on_screen, mobile_drag_on_screen, mobile_long_press_on_screen_at_coordinates, mobile_list_elements_on_screen, mobile_press_button, mobile_open_url, mobile_swipe_on_screen, mobile_type_keys, mobile_save_screenshot, mobile_take_screenshot, mobile_set_orientation, mobile_fold_device, mobile_set_location, mobile_clipboard, mobile_get_device_logs, mobile_get_orientation, mobile_start_screen_recording, mobile_stop_screen_recording, mobile_list_crashes, mobile_get_crash. A step named "delay" with arguments {"milliseconds": N} (up to 10000) waits before the next step, e.g. for an animation or a page load to finish before looking at the screen.
Inputs: steps (required), device (required), stopOnError, listElementsAtEnd.
mobile_clear_app_dataClear App DataADestructive
Clear an app's data, such as its cache, documents, preferences and databases, and stop the app, so the next launch starts as if freshly installed. The app stays installed. Supported on Android devices and emulators and on iOS simulators, not on real iOS devices.
Inputs: device (required), packageName (required).
mobile_click_on_screen_at_coordinatesClick ScreenA
Click on the screen, either at x,y coordinates or on an element by its ref (e.g. "@e5") from the latest mobile_list_elements_on_screen result. Prefer ref when the element is listed.
Inputs: device (required), x, y, ref.
mobile_clipboardClipboardA
Read or replace the device clipboard. Pass text to set the clipboard, omit it to read the current clipboard.
Inputs: device (required), text.
mobile_double_tap_on_screenDouble Tap ScreenA
Double-tap on the screen, either at x,y coordinates or on an element by its ref (e.g. "@e5") from the latest mobile_list_elements_on_screen result. Prefer ref when the element is listed.
Inputs: device (required), x, y, ref.
mobile_drag_on_screenDrag On ScreenA
Drag one finger from one point to another, e.g. to move a slider, reorder a list or drag and drop. Each end is either x,y coordinates or an element by its ref (e.g. "@e5") from the latest mobile_list_elements_on_screen result. Prefer ref when the element is listed.
Inputs: device (required), x1, x2, y1, +4 more.
mobile_fold_deviceFold DeviceA
Fold or unfold a foldable device, such as iPhone Duo simulators and foldable Android emulators. Provide either posture or angle.
Inputs: device (required), angle, posture.
mobile_get_crashGet Crash ReportARead-only
Get the full content of a crash report by its ID. Use mobile_list_crashes to find available crash IDs.
Inputs: id (required), device (required).
mobile_get_device_logsGet Device LogsARead-only
Collect live device logs (logcat on Android, unified log on iOS) as one JSON object per line. Only logs emitted after the call starts are captured, so trigger the behavior you want to observe right before or during the call. Stops after limit entries or after 30 seconds of silence. Each line of a stack trace counts as one entry, so filter by process or tag to avoid filling the limit with noise. Start with a small limit (20-50) for a quick look. For large captures, pass saveTo to write logs to a file and only the entry count is returned.
Inputs: device (required), limit, filter, saveTo.
mobile_get_foreground_appGet Foreground AppARead-only
Get the app currently in the foreground on the device, including the focused activity class on Android or view controller class on iOS when available. Use this to verify which app or screen you are on before interacting with it.
Inputs: device (required).
mobile_get_orientationGet OrientationBRead-only
Get the current screen orientation of the device
Inputs: device (required).
mobile_get_screen_sizeGet Screen SizeARead-only
Get the screen size of the mobile device in pixels
Inputs: device (required).
mobile_install_appInstall AppC
Install an app on mobile device
Inputs: path (required), device (required).
mobile_launch_appLaunch AppA
Launch an app on mobile device. Use this to open a specific app. You can find the package name of the app by calling mobile_list_apps.
Inputs: device (required), packageName (required), locale.
mobile_list_appsList AppsCRead-only
List all the installed apps on the device
Inputs: device (required).
mobile_list_available_devicesList DevicesARead-only
List all available devices. This includes both physical mobile devices and mobile simulators and emulators. It returns both Android and iOS devices. These are local devices already connected to this machine, ready to use immediately at no cost - for devices from the shared remote cloud fleet, use mobile_list_remote_devices instead.
Inputs: no named parameters.
mobile_list_crashesList Crash ReportsCRead-only
List crash reports available on the device
Inputs: device (required).
mobile_list_elements_on_screenList Screen ElementsARead-only
List elements on screen with their ref, coordinates, and display text or accessibility label. Use the ref with mobile_click_on_screen_at_coordinates, mobile_double_tap_on_screen, mobile_long_press_on_screen_at_coordinates or mobile_drag_on_screen. Refs and coordinates stay valid as long as the screen does not change; re-list only after navigation or a layout change.
Inputs: device (required), format.
mobile_list_remote_devicesList Remote DevicesARead-only
List the catalog of device models (make, platform, OS version) available to reserve from the remote cloud device fleet. This is different from mobile_list_available_devices, which lists real devices and simulators/emulators already connected to this local machine and ready to use immediately at no cost. Remote devices live in a shared cloud fleet: they are not usable until reserved with mobile_allocate_remote_device, and reserving one may be a limited/billed resource. Requires mobile_login_to_cloud_provider to have been called first; if this fails with an authentication error, call that tool then retry.
Inputs: no named parameters.
mobile_login_to_cloud_providerLogin to Cloud ProviderA
Start authenticating this machine with the remote device cloud provider. This is required once before mobile_list_remote_devices or mobile_allocate_remote_device will work; if either of those fails with an authentication error, call this tool and then retry. This starts a browser-based device-code login and returns quickly with a URL and a one-time code - it does NOT wait for the login to complete. Show the URL and code to the user verbatim and ask them to open the URL and enter the code in their own browser. The login keeps running in the background after this tool returns; once the user confirms they've completed it, retry the remote devices tool that originally failed. Only call this after the user has asked for, or agreed to, remote/cloud devices - never call it speculatively, since it interrupts the user to act in their browser.
Inputs: no named parameters.
mobile_long_press_on_screen_at_coordinatesLong Press ScreenA
Long press on the screen, either at x,y coordinates or on an element by its ref (e.g. "@e5") from the latest mobile_list_elements_on_screen result. Prefer ref when the element is listed.
Inputs: device (required), x, y, ref, +1 more.
mobile_open_urlOpen URLA
Open an http:// or https:// URL in the browser on device. Other URL schemes, such as app deep links, are rejected unless the server was started with MOBILEMCP_ALLOW_UNSAFE_URLS=1.
Inputs: url (required), device (required).
mobile_press_buttonPress ButtonC
Press a button on device
Inputs: button (required), device (required).
mobile_release_remote_deviceRelease Remote DeviceADestructive
Release a device previously reserved with mobile_allocate_remote_device back to the remote cloud fleet so it becomes available to others. Releasing is destructive to the device's state: apps installed, files pushed, and any other changes made during this session are lost, and a later mobile_allocate_remote_device call may take time and could return a different physical unit. Only release once the whole task is finished - if there is more work to do on the same device shortly, keep holding it rather than releasing and reallocating.
Inputs: device (required).
mobile_save_screenshotSave ScreenshotC
Save a screenshot of the mobile device to a file
Inputs: device (required), saveTo (required), scale, maxSize.
mobile_set_locationSet LocationA
Override the GPS location reported by the device, or clear the override to restore the real location. Omit latitude and longitude to clear.
Inputs: device (required), latitude, longitude.
mobile_set_orientationSet OrientationC
Change the screen orientation of the device
Inputs: device (required), orientation (required).
mobile_start_screen_recordingStart Screen RecordingA
Start recording the screen of a mobile device. The recording runs in the background until stopped with mobile_stop_screen_recording. Returns the path where the recording will be saved.
Inputs: device (required), output, timeLimit.
mobile_stop_screen_recordingStop Screen RecordingA
Stop an active screen recording on a mobile device. Returns the file path, size, and approximate duration of the recording.
Inputs: device (required).
mobile_swipe_on_screenSwipe ScreenC
Swipe on the screen
Inputs: device (required), direction (required), x, y, +1 more.
mobile_take_screenshotTake ScreenshotARead-only
Take a screenshot of the mobile device. Use this to understand what's on screen, if you need to press an element that is available through view hierarchy then you must list elements on screen instead. The screenshot is usually smaller than the screen, so when the device reports its screen size the result also states how to convert positions in the screenshot into screen coordinates before tapping. Do not cache this result.
Inputs: device (required), clip, scale, maxSize.
mobile_terminate_appTerminate AppC
Stop and terminate an app on mobile device
Inputs: device (required), packageName (required).
mobile_type_keysType TextB
Type text into the focused element
Inputs: text (required), device (required), submit.
mobile_uninstall_appUninstall AppCDestructive
Uninstall an app from mobile device
Inputs: device (required), packageName (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 36 tools
Most tools target a distinct action on a distinct resource, and the local-vs-remote device split is explicitly disambiguated in the descriptions (mobile_list_available_devices vs mobile_list_remote_devices). Minor overlaps remain: mobile_take_screenshot vs mobile_save_screenshot return an image vs write a file, and mobile_press_button is vague about which buttons are accepted. mobile_batch_commands duplicates other tools by design but its description scopes it as a meta-tool.
Nearly every tool follows a clean mobile_verb_noun pattern (mobile_launch_app, mobile_list_apps, mobile_set_orientation), which makes scanning and grouping easy. The deviations are small but real: get_more_tools has no mobile_ prefix, mobile_batch_commands and mobile_clipboard use a noun rather than a verb, and mobile_press_button omits the target object unlike its siblings.
36 tools is heavy and sits above the comfortable range, though the domain is genuinely broad (device discovery, remote cloud allocation, app lifecycle, gestures, capture, logs, crashes, location, clipboard). Some entries could be consolidated, notably take_screenshot/save_screenshot and the many single-purpose setters. It is defensible but toward the bloated end for the stated purpose.
Coverage of the mobile automation lifecycle is strong: device listing/allocation/release, app install-launch-clear-uninstall, full gesture and input set, screenshots and recording, logs, crash reports, orientation, location and clipboard. The main gaps are file push/pull and permission or network-condition manipulation, which agents can sometimes work around via batch flows and shell-adjacent tools but not cleanly.
Maintenance
Related MCP Connectors
Let AI agents control Android and iOS devices on Mobilerun Cloud: screen, input, apps, workflows.
Melaya is a remote MCP server. It gives an assistant hands on your own Android phone and browser: it reads the screen through the accessibility tree, then taps, types and navigates inside the apps and sites you allow-list, with no per-app API. It also builds, schedules and runs agent pipelines across 6k+ connected tools. OAuth 2.1, nothing to install.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Let your AI agent control real iPhones: screenshots, tap, swipe, type and open apps.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI agents to control and automate Android devices through natural language, supporting actions like app management, UI interactions, and device monitoring.60MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables scalable mobile automation for iOS and Android through a platform-agnostic interface, allowing LLMs to interact with mobile applications via accessibility snapshots or screenshot-based inputs.192Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with iOS simulators, perform accessibility testing, manage apps, and automate complex iOS workflows.32Apache 2.0
- AlicenseAqualityCmaintenanceA Model Context Protocol server for ad-hoc UI testing of Android and iOS apps, enabling LLM agents to interact with mobile app UIs and react to observations.407 npm3MIT