Mobile Mcp
About
Model Context Protocol Server for Mobile Automation and Scraping (iOS, Android, Emulators, Simulators and Real Devices)
Details
- Author
- mobile-next
- GitHub stars
- 5,387
- Downloads
- 1,514
- Categories
- Developer Tools, Other, Automation, AI
Jump to
- Fast and lightweight using native accessibility trees
- LLM-friendly: no computer vision model required in Accessibility mode
- Visual Sense: evaluates rendered screen and falls back to screenshot analysis
- Deterministic tool application reduces ambiguity from screenshots
- Extract structured data from anything visible on screen
- Supports iOS and Android real devices, simulators, and emulators
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Mobile McpCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install and configure Mobile MCP by adding the standard MCP configuration to your MCP client using npx with @mobilenext/mobile-mcp@latest. By default it runs over stdio; optionally start as an SSE server with the --listen flag and protect it with Bearer token authorization via the MOBILEMCP_AUTH environment variable.
mobile_list_available_devices
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_provider
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 explicitly asked to connect to, log into, or use remote/cloud devices - never call it speculatively, since it interrupts the user to act in their browser.
mobile_list_remote_devices
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_device
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 - only call this after the user has explicitly asked to use a remote/cloud device, never speculatively or as a fallback when a local device isn't found. 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_device
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_apps
List all the installed apps on the device
mobile_launch_app
Launch an app on mobile device. Use this to open a specific app. You can find the package name of the app by calling list_apps_on_device.
mobile_terminate_app
Stop and terminate an app on mobile device
mobile_install_app
Install an app on mobile device
mobile_uninstall_app
Uninstall an app from mobile device
mobile_get_screen_size
Get the screen size of the mobile device in pixels
mobile_click_on_screen_at_coordinates
Click on the screen at given x,y coordinates. If clicking on an element, use the list_elements_on_screen tool to find the coordinates.
mobile_double_tap_on_screen
Double-tap on the screen at given x,y coordinates.
mobile_long_press_on_screen_at_coordinates
Long press on the screen at given x,y coordinates. If long pressing on an element, use the list_elements_on_screen tool to find the coordinates.
mobile_list_elements_on_screen
List elements on screen and their coordinates, with display text or accessibility label. Do not cache this result.
mobile_press_button
Press a button on device
mobile_open_url
Open a URL in browser on device
mobile_swipe_on_screen
Swipe on the screen
mobile_type_keys
Type text into the focused element
mobile_save_screenshot
Save a screenshot of the mobile device to a file
mobile_take_screenshot
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. Do not cache this result.
mobile_set_orientation
Change the screen orientation of the device
mobile_get_orientation
Get the current screen orientation of the device
mobile_start_screen_recording
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_recording
Stop an active screen recording on a mobile device. Returns the file path, size, and approximate duration of the recording.
mobile_list_crashes
List crash reports available on the device
mobile_get_crash
Get the full content of a crash report by its ID. Use mobile_list_crashes to find available crash IDs.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mobile mcp": {
"mobile-mcp": {
"command": "npx",
"args": [
"-y",
"@mobilenext/mobile-mcp@latest"
]
}
}
}
}
McpServers
{
"mobile-mcp": {
"command": "npx",
"args": [
"-y",
"@mobilenext/mobile-mcp@latest"
]
}
}
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.


