Skip to content

Summary

Platform-agnostic MCP server that drives iOS and Android apps on simulators, emulators and real devices through the accessibility tree rather than screenshots.

Features

  • Drives apps from the native accessibility tree — no vision model, no image tokens
  • Same tools across iOS and Android, on simulators, emulators and real devices
  • Taps, swipes, gestures, hardware buttons, deep links and orientation control
  • App install, launch and terminate, plus screen recording
  • Structured, deterministic UI output for reliable data extraction
  • No XCUITest or Espresso knowledge required

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Mobile MCP" tools will be available.
{
  "mcpServers": {
    "mobile-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mobilenext/mobile-mcp@latest"
      ]
    }
  }
}

Description

Mobile MCP (from Mobile Next) lets an agent operate a real mobile app the way a person would — list devices, launch the app, tap, swipe, type, read the screen — without you writing XCUITest or Espresso, and without the agent needing to know which platform it is on.

Accessibility-first, not vision-first

Its defining choice is to read the native accessibility tree instead of screenshotting the device and asking a vision model what it sees. That makes runs faster and much cheaper (no image tokens), and the output is structured and deterministic: real UI elements with real identifiers, not a model's guess about a picture. Screenshots with coordinate taps remain available as a fallback for views the accessibility tree does not describe.

One API, every target

The same tools work across iOS simulators (Xcode + xcrun simctl), iOS real devices (go-ios + WebDriverAgent + tunnel), Android emulators (Android SDK + adb) and Android real devices (adb with USB debugging). Device management covers listing devices, screen size and reading or setting orientation; app management covers listing, launching and terminating apps; interaction covers taps, swipes, gestures, hardware buttons, deep links and screen recording.

What it is for

Native app test automation and data entry, scripted flows and form filling without babysitting a simulator, multi-step user journeys driven by an LLM, and general agent-based mobile interaction or data extraction. It works with Claude Code, Codex, Gemini, GitHub Copilot, Antigravity and any other MCP-compatible client.

Published as @mobilenext/mobile-mcp under the Apache-2.0 licence.

Related MCP Servers

MCP: agent-device

by Callstack

Featured

Give a coding agent a live feedback loop on real mobile, TV and desktop apps — inspect, tap, type and capture evidence on iOS, Android and HarmonyOS over MCP or a CLI.

MCP: BrowserStack

by BrowserStack

Official BrowserStack MCP server: run manual and automated tests on real browsers and devices, then debug and fix failing tests from your IDE in plain English.

Sentry's MCP server and CLI for iOS and macOS work — build, run on simulators and devices, capture logs, and drive tests from inside a coding agent.

MCP: DexSQL

by LSPosed

New

Query classes, methods, strings and call references in APK and DEX files with SQL, from the command line or any MCP-connected AI agent.

Browse all MCP servers →