PlugWiki
mobile-mcp logo

Mobile Next MCP Server: Setup for Claude Code, Cursor and Other Apps

CommunityLocal
Getnpm@mobilenext/mobile-mcpmobile-next/mobile-mcp

Lets Claude, Cursor or Codex use a phone for you: tap, type, scroll and read the screen on iOS and Android simulators, emulators and real devices.

Mobile Next's server drives iOS and Android through the accessibility tree and screenshots. It runs on your computer and needs Node.js 20, Xcode command line tools for iOS and Android Platform Tools for Android. Local use needs no account. A cloud option adds rentable real phones with a browser sign-in. Anonymous usage data is sent unless you turn it off.

Good for

  • App developers who want an assistant to test flows on a simulator or phone
  • QA engineers who automate mobile checks without writing XCUITest or Espresso
  • Teams that want an assistant to reproduce a bug and read device logs

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install mobile MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the mobile MCP server to Claude Code. Run this command:
    
    claude mcp add mobile -- npx -y @mobilenext/mobile-mcp
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js, Xcode CLI tools (iOS) or Android Platform Tools (Android).

Needs Node.js 20 or newer. The README also offers npx @mobilenext/mobile-mcp@latest install, which finds your clients and sets them up. To turn off usage data, add the MOBILEMCP_DISABLE_TELEMETRY environment variable with any value to the server config.

Built from the package data we hold. Not yet tested by us.

Tools

  • Lists the phones, simulators and emulators you can use

    Finds every iOS simulator, Android emulator and connected real device the assistant can control.

    Try: “Which devices are available right now?”

    Runs code · mobile_list_available_devices

  • Reads the buttons and text on the current screen

    Returns the UI elements on screen with their positions, so the assistant can tap by element instead of guessing from a picture.

    Try: “What buttons are on the login screen?”

    Read · mobile_list_elements_on_screen

  • Takes a screenshot of the device

    Captures what is on the device screen and returns it as an image for the assistant to look at.

    Try: “Take a screenshot and tell me what screen this is.”

    Read · mobile_take_screenshot

  • Saves a screenshot to a file

    Captures the screen and writes it to a .png or .jpg path on your computer.

    Try: “Save a screenshot to ~/Desktop/home.png.”

    Write · mobile_save_screenshot

  • Taps a spot or element on the screen

    Taps at x,y coordinates or on an element from the screen list.

    Try: “Tap the Sign in button.”

    Write · mobile_click_on_screen_at_coordinates

  • Double-taps the screen

    Double-taps at coordinates or on an element.

    Try: “Double-tap the photo to like it.”

    Write · mobile_double_tap_on_screen

  • Long-presses the screen

    Presses and holds at coordinates or on an element.

    Try: “Long-press the app icon.”

    Write · mobile_long_press_on_screen_at_coordinates

  • Swipes up, down, left or right

    Swipes in any direction, for scrolling lists or moving between pages.

    Try: “Scroll down to the bottom of the feed.”

    Write · mobile_swipe_on_screen

  • Types text into the focused field

    Types text into the field that has focus, with an option to press submit.

    Try: “Type my test email into the field and submit.”

    Write · mobile_type_keys

  • Presses Home, Back, Volume or Enter

    Presses a hardware or system button on the device.

    Try: “Press the Back button twice.”

    Write · mobile_press_button

  • Opens a web link on the device

    Opens an http or https address in the device browser.

    Try: “Open https://example.com on the phone.”

    Write · mobile_open_url

  • Opens an app by its package name

    Starts an installed app using its package name or bundle ID.

    Try: “Launch com.example.shop.”

    Write · mobile_launch_app

From the official docs

Permissions

high risk · 4 things to watch · 6 advisories

High risk

The assistant can control a phone like a person would, including uninstalling apps and clearing their data. Use a simulator, an emulator or a spare test phone with no real accounts on it.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It can uninstall apps and wipe their data

    Uninstall, clear-data and batch tools are marked destructive. Use a test device or simulator, not your daily phone. github.com

  • It can tap and type anywhere on the device

    The assistant acts like a user on the screen, so it can send messages or buy things in apps that are signed in. Keep real accounts off the device. github.com

  • It sends usage data and your goal text unless you opt out

    Tool names, run times and platform details go to PostHog, and a counter pixel is fetched. While telemetry is on, an extra get_more_tools tool sends the assistant's written goal to the developers; the tool text says to leave out private data. Set MOBILEMCP_DISABLE_TELEMETRY to any value to stop both. github.com

  • Cloud devices are billed and shared

    The cloud tools reserve real phones. The tool text tells the assistant to ask you first, so confirm before you agree. github.com

Security advisories

6 known advisories, all fixed in a newer version.

Show all 6
Technical details
Turning on read-onlyNo read-only switch is documented.
Talks tous.i.posthog.com and static.scarf.sh for usage data, and the goal text from get_more_tools, unless MOBILEMCP_DISABLE_TELEMETRY is set. Mobile Next Cloud when you use the remote device tools
Sign-in and keysNo account for local devices. The cloud tools use a browser device-code login.

Questions

Is the Mobile Next MCP server official?

It is made by Mobile Next, the project behind it, and is not made by Apple or Google. It works with iOS and Android through their own tools.

What do I need installed?

Node.js 20 or newer. For iOS you need Xcode command line tools and a booted simulator or a trusted USB device. For Android you need Platform Tools (adb) and a running emulator or a phone with USB debugging on.

Does it work with real phones?

Yes. The README lists iOS simulators, iOS real devices, Android emulators and Android real devices as supported. Real devices connect over USB.

Does it collect usage data?

Yes, by default. It sends tool names, run times and basic system details to PostHog. Set the MOBILEMCP_DISABLE_TELEMETRY environment variable to any value to turn that off.

Can it run read-only?

No. No read-only switch is documented, and most tools tap, type or change the device. Some tools only read, such as listing apps or logs.

Is the list of 35 tools complete?

It matches the server code for the current release. One of them only appears when telemetry is on.

Information

updated Nov 2, 2026

Publisher
Community
Package
@mobilenext/mobile-mcp
Registry
npm
Transport
stdio
Auth
None
Version
1.0.15
License
Apache-2.0
Last commit
Oct 30, 2026
Open issues
42
Listed in
Official MCP registry

WebsiteGitHubnpmOfficial MCP RegistryChangelogIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 2
  1. github.com · github.com
  2. github.com · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.