Log inSubmit server
Mobile MCP logo

Mobile MCP

by mobile-next

Automates iOS and Android apps on local or cloud devices through accessibility, gesture, app, and diagnostic MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Mobile MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mobile-next-mobile-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mobilenext/mobile-mcp@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

mobile-next/mobile-mcp connects MCP-compatible agents to iOS and Android simulators, emulators, physical devices, and reserved cloud devices. It exposes tools for accessibility-based UI inspection, coordinate interactions, app lifecycle management, screenshots, input, device state, recordings, and logs. Local targets require the relevant Apple or Android tooling, while remote devices use a browser-based cloud login and explicit allocation. Reach for it when an agent needs to test, operate, inspect, or extract data from native mobile applications across platforms.

Use cases

  • Automate native iOS and Android test flows
  • Drive multi-step app journeys with an agent
  • Inspect accessibility elements and extract structured screen data
  • Collect screenshots, recordings, and device logs during debugging

Key features

  • Cross-platform control for iOS and Android targets
  • Accessibility-tree inspection with coordinate-based fallback
  • Local device and cloud device management
  • App installation, launch, termination, and removal
  • Gestures, text input, orientation, location, and clipboard control
  • Screenshots, recordings, and live device logs

Tools33

What Mobile MCP lets your agent do. Expand a tool for its parameters.

Verified live~5.7k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

30/33 checks healthy over the last 78d

Supply-chain signal

2 high-severity advisories on record for this package. Most advisories affect transitive dependencies and may not be exploitable in this server's actual usage — this is a directional signal, not a security audit.

Critical 0High 2Medium 0Low 0

Scanned 9d ago via OSV.dev · @mobilenext/mobile-mcp@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars10kStargazers on the source repository.
npm downloads81kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Tools exposed33Callable tools this server registers over MCP.
Directory activity8 viewsConfig copies, upvotes, and views on AllMCPs.

How Mobile MCP works

What mobile-next/mobile-mcp does

mobile-next/mobile-mcp gives an MCP-compatible agent a single interface for operating native iOS and Android applications. It can work with booted simulators and emulators, USB-connected real devices, or physical devices reserved from Mobile Next Cloud. The same family of tools covers both platforms, so an automation flow does not need separate iOS and Android control logic.

The server fits testing, scripted data-entry flows, multi-step user journeys, app inspection, and agent-driven mobile interaction. It can read the native accessibility hierarchy and return structured element information, while screenshots and coordinate gestures provide an alternative for screens that are not represented adequately through accessibility data.

How it works

Begin by listing devices available to the local machine. For cloud use, authenticate through the browser-based device-code flow, inspect the remote device catalog, and reserve a physical device for the session. A reserved device remains exclusive until released; releasing it removes apps, files, and other changes made during that session.

For UI work, an agent can inspect the current screen, identify elements by accessibility data and references, then tap an element reference or use screen coordinates. It can type into the focused control, press hardware buttons, swipe, open a URL, and verify the foreground application. Screen references and coordinates should be refreshed after navigation or other layout changes.

Setup and configuration

The quick installer is available through npm:

Terminal
npx @mobilenext/mobile-mcp@latest install

The installer detects MCP clients on the machine and can configure selected clients, or all detected clients with --yes. Manual client configuration is also supported.

For an iOS Simulator, use Xcode with a booted simulator. A real iOS device must be connected over USB and trusted. Android automation requires the Android SDK and a running emulator, or adb with USB debugging enabled and authorized for a real device.

Tools and capabilities

  • Discover local devices and inspect screen dimensions and orientation.
  • Authenticate to Mobile Next Cloud, browse its device catalog, allocate a physical device, and release it after use.
  • List installed apps, identify the foreground app, launch or terminate apps, and install or uninstall application packages.
  • Read accessibility elements, take or save screenshots, tap, double-tap, long-press, swipe, type text, and press device buttons.
  • Open web URLs, change orientation, fold or unfold supported devices, override or clear location, and read or set the clipboard.
  • Start and stop screen recordings and collect Android logcat or iOS unified logs, with optional file output for larger captures.

Limitations and notes

Cloud devices are shared resources and may be billed or limited, unlike devices already connected locally. Remote operations require cloud authentication before listing or allocating devices, and allocation should be intentional rather than used as an automatic fallback. Releasing a remote device is destructive to its session state.

Coordinate-based actions depend on the device’s reported dimensions and current layout. Accessibility references remain valid only while the screen is unchanged. Device logs capture entries emitted after collection begins; filtering and modest limits help prevent a capture from filling with unrelated output.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Mobile MCP

mobile-next/mobile-mcp is an MCP server that connects AI agents to local or cloud iOS and Android devices, including simulators, emulators, and physical phones. Its main tools inspect accessibility elements, control taps and gestures, manage apps, capture screenshots and recordings, change device state, and collect device logs.

Run `npx @mobilenext/mobile-mcp@latest install` to detect MCP clients and configure the ones you select. Add `--yes` to configure every detected client. Manual client configuration is also available.

It supports iOS simulators, trusted USB-connected iOS devices, Android emulators, and Android devices connected through authorized `adb` USB debugging. It can also allocate physical iOS or Android devices from the Mobile Next Cloud fleet after cloud authentication.

Authenticate with `mobile_login_to_cloud_provider`, list models with `mobile_list_remote_devices`, and reserve a device with `mobile_allocate_remote_device`. Release it with `mobile_release_remote_device` when the complete task is finished; releasing wipes the device state.

Yes. Cursor is among the MCP clients detected by the quick installer, so the server can be configured with `npx @mobilenext/mobile-mcp@latest install`.

Related MCP servers

All in OS Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMobile MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mobile-next-mobile-mcp?style=directory)](https://allmcps.com/mcp/mobile-next-mobile-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/mobile-next-mobile-mcp"><img src="https://allmcps.com/api/badge/mobile-next-mobile-mcp?style=directory" alt="Mobile MCP on AllMCPs" /></a>