Mobile Next MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Drive a real or simulated iOS/Android device.
Start with mobile_list_available_devices and pass the chosen device id to every later call - there is no implicit "current device". Use a remote device only when local ones do not fit or when requested by the user. Remote devices cost money and take time to allocate and release. Release when done using, so the remote device cleans and returns to pool.
Read the screen with mobile_list_elements_on_screen, not screenshots: it returns refs, coordinates and labels, and tapping by ref survives layout differences between devices. Fall back to mobile_take_screenshot only for elements missing from the hierarchy, or to judge visual appearance.
Each call is a device round-trip. Group known sequences (tap, type, tap) into mobile_batch_commands instead of issuing them one at a time.
Prefer mobile_launch_app to open an app, and mobile_open_url to open a web page, over navigating through the UI. mobile_open_url only accepts http:// and https:// URLs unless the server was started with MOBILEMCP_ALLOW_UNSAFE_URLS=1, so do not rely on it for app deep links.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_more_toolsA | 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. |
| mobile_list_available_devicesA | 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. |
| mobile_login_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. |
| mobile_list_remote_devicesA | 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. |
| mobile_allocate_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. |
| mobile_release_remote_deviceA | 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. |
| mobile_list_appsC | List all the installed apps on the device |
| mobile_get_foreground_appA | 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. |
| mobile_launch_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. |
| mobile_terminate_appC | Stop and terminate an app on mobile device |
| mobile_clear_app_dataA | 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. |
| mobile_install_appC | Install an app on mobile device |
| mobile_uninstall_appC | Uninstall an app from mobile device |
| mobile_get_screen_sizeA | Get the screen size of the mobile device in pixels |
| mobile_click_on_screen_at_coordinatesA | 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. |
| mobile_double_tap_on_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. |
| mobile_drag_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. |
| mobile_long_press_on_screen_at_coordinatesA | 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. |
| mobile_list_elements_on_screenA | 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. |
| mobile_press_buttonC | Press a button on device |
| mobile_open_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. |
| mobile_swipe_on_screenC | Swipe on the screen |
| mobile_type_keysB | Type text into the focused element |
| mobile_save_screenshotC | Save a screenshot of the mobile device to a file |
| mobile_take_screenshotA | 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. |
| mobile_set_orientationC | Change the screen orientation of the device |
| mobile_fold_deviceA | Fold or unfold a foldable device, such as iPhone Duo simulators and foldable Android emulators. Provide either posture or angle. |
| mobile_set_locationA | Override the GPS location reported by the device, or clear the override to restore the real location. Omit latitude and longitude to clear. |
| mobile_clipboardA | Read or replace the device clipboard. Pass text to set the clipboard, omit it to read the current clipboard. |
| mobile_get_device_logsA | 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 |
| mobile_get_orientationB | Get the current screen orientation of the device |
| mobile_start_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. |
| mobile_stop_screen_recordingA | Stop an active screen recording on a mobile device. Returns the file path, size, and approximate duration of the recording. |
| mobile_list_crashesC | List crash reports available on the device |
| mobile_get_crashA | Get the full content of a crash report by its ID. Use mobile_list_crashes to find available crash IDs. |
| mobile_batch_commandsA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.