mcpSource-backedReview first Safety ✓ Privacy ✓

Mobile MCP Server

Cross-platform mobile automation MCP server for iOS and Android simulators, emulators, and real devices using accessibility snapshots, screenshots, coordinate taps, app management, and input tools.

by mobile-next·added 2026-06-05·

Claude CodeClaude Desktop

HarnessClaude CodeClaude Desktop

Install

Source

npx -y @mobilenext/mobile-mcp@latest

Readiness

TrustReview first
Sourcesource-backed
Safety notesPresent
ReviewedYes

Documentation Source repository Registry JSON · LLM text

Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

Mobile MCP can list devices, launch apps, terminate apps, install or uninstall apps, take screenshots, inspect UI elements, tap coordinates, type text, press device buttons, swipe, and open URLs.
Real devices may contain personal accounts, private notifications, photos, messages, payment apps, health data, location data, and authentication prompts.
Use simulators, emulators, or dedicated test devices for automation, and require approval before installing apps, uninstalling apps, sending messages, making purchases, changing settings, or entering credentials.
Coordinate-based taps can hit the wrong UI when layouts change; verify critical actions with screenshots or accessibility snapshots.

Privacy notes

Screenshots, accessibility trees, app lists, device names, package identifiers, typed input, visible notifications, and app contents may be sent to the MCP client and model.
Real-device automation can expose personal data, customer data, tokens, one-time codes, location, contacts, photos, and private app state.
Saved screenshots and logs should be protected or deleted after sensitive testing.

Prerequisites

Node.js 18 or newer.
iOS Simulator, Android Emulator, or connected real iOS or Android device.
Platform tooling required for the target device, such as Xcode tooling for iOS or ADB for Android.
MCP client such as Claude Code, Claude Desktop, Codex, Cursor, Cline, Gemini CLI, Goose, Kiro, or Windsurf.
Test accounts and test devices for workflows that may touch private data.

Schema details

Install type: cli
Troubleshooting: No

Source repository stats

Scope: Source repo

Collection metadata

Estimated setup: 20 minutes
Difficulty: intermediate

Tool listing metadata

Website: https://mobilenext.ai

Full copyable content

{
  "mcpServers": {
    "mobile-mcp": {
      "command": "npx",
      "args": ["-y", "@mobilenext/mobile-mcp@latest"]
    }
  }
}

About this resource

Content

Mobile MCP Server lets AI agents automate mobile apps across iOS and Android simulators, emulators, and real devices. It provides a platform-agnostic MCP interface over accessibility snapshots, screenshots, coordinate-based taps, device management, app management, input, and navigation.

The project is designed for native app automation, mobile testing, scripted flows, form interaction, data extraction, and agent-driven mobile workflows.

Source Review

These sources were reviewed on 2026-06-05. Prefer the live repository and wiki for current platform support, client-specific setup, device requirements, and debugging guidance.

Features

iOS Simulator and iOS real-device support.
Android Emulator and Android real-device support.
Accessibility snapshots plus screenshot and coordinate fallback workflows.
Device listing, screen size, and orientation tools.
App listing, launch, terminate, install, and uninstall tools.
Screenshot, UI element listing, tap, double-tap, long-press, swipe, type, device button, and open-URL tools.
Client examples for Claude Code, Claude Desktop, Codex, Cursor, Cline, Gemini CLI, Goose, Kiro, Windsurf, and more.

Installation

Add the standard MCP server config:

{
  "mcpServers": {
    "mobile-mcp": {
      "command": "npx",
      "args": ["-y", "@mobilenext/mobile-mcp@latest"]
    }
  }
}

Connect an iOS or Android simulator, emulator, or real device with the platform tooling required by the Mobile MCP wiki.

Use Cases

Let an AI assistant test native mobile app flows.
Capture screenshots and accessibility snapshots for debugging.
Automate repetitive mobile QA tasks on emulators or simulators.
Drive multi-step data entry flows in controlled test apps.
Inspect visible mobile UI state before generating test scripts.

Safety and Privacy

Prefer simulators, emulators, or dedicated test devices. Real phones can expose private notifications, messages, photos, contacts, payment apps, health data, and authentication prompts. Require confirmation before installing or uninstalling apps, sending messages, submitting forms, entering credentials, or touching production accounts.

Treat screenshots, accessibility snapshots, app lists, typed input, and device metadata as sensitive test artifacts.

Duplicate Check

No mobile-next/mobile-mcp entry or source URL was found in content/mcp. This entry is separate from browser, desktop, Windows, and Xcode automation MCP servers because it targets mobile devices and native mobile apps.

#mobile#ios#android#automation#testing

Source citations

Signals

Loading live community signals…