Hosting

Self-hosted local process for local devices; Mobile Next Cloud can provide remote physical devices.

Transport

stdio by default; optional Streamable HTTP with --listen

Endpoint

Local process; no hosted endpoint documented

Authentication

No credential is required for local simulators, emulators, or connected devices. Remote Mobile Next Cloud device operations require its documented browser-based account login. Optional HTTP bearer authorization can be enabled with MOBILEMCP_AUTH.

Requirements

• Node.js 20 or newer.
• Android targets require Android Platform Tools and an authorized adb device/emulator.
• iOS targets require Xcode command-line tools and a booted simulator; physical iOS devices require additional documented tooling and trust setup.
• At least one running or connected target device is needed for device operations.

Setup steps

1. Install Node.js 20 or newer and the platform tools for the device type you will use: Android Platform Tools for Android, or Xcode command-line tools for iOS.
2. Configure a stdio server with command `npx` and args `-y`, `@mobilenext/mobile-mcp@latest`. The official Codex example omits `-y`; the README's standard configuration includes it for non-interactive npx use.
3. Start an Android emulator or authorize a connected Android device, or boot an iOS simulator on a supported host. The official install guide documents `xcrun simctl list` and `xcrun simctl boot` for iOS simulator setup.
4. Restart or reconnect the MCP client, then call `mobile_list_available_devices`. An empty list means the required emulator, simulator, or device is not running or authorized.
5. Telemetry is enabled by default; set `MOBILEMCP_DISABLE_TELEMETRY=1` in the server environment to disable it. For remote device access, follow Mobile Next Cloud's login flow from the server's `mobile_login_to_cloud_provider` tool.

The repository documents the device, app, screen-interaction, navigation, and logs tool groups, including the names below. The list is a partial documentation inventory, not a live tools/list result; remote-device tools additionally require the Mobile Next Cloud path.

• mobile_list_available_devices

  List local simulators, emulators, and connected devices.

  01
• mobile_list_apps

  List installed applications on a device.

  02
• mobile_take_screenshot

  Capture the current device screen.

  03
• mobile_list_elements_on_screen

  Read the visible UI elements and their properties.

  04
• mobile_click_on_screen_at_coordinates

  Tap a screen coordinate or referenced visible element.

  05
• mobile_type_keys

  Type text into the focused mobile UI element.

  06
• mobile_get_device_logs

  Read device logs such as Android logcat or iOS unified logs.

  07

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Device operations affect real or emulated applications and may change app state; use a test device and avoid signing into sensitive accounts during automation.
• iOS device targets require Apple tooling; Android requires platform tools and device authorization.
• The package collects anonymous telemetry by default; the official documentation describes MOBILEMCP_DISABLE_TELEMETRY=1 as the opt-out.
• Documentation and logo were reviewed; MCP initialization, tools/list, and tool calls were not tested.

• official repository documentation

  Documents device targets, Node.js 20+ and platform-tool requirements, stdio package command, Codex configuration, device verification, optional Streamable HTTP, bearer auth, telemetry setting, and supported tool names.

• official installation guide

  Provides an AI-agent installation path and confirms Node.js 20+, target platform prerequisites, and mobile_list_available_devices as the connection check.

• official product page

  Identifies Mobile MCP as a Mobile Next product and links to the canonical repository; describes local and cloud device use cases.

• official project logo asset

  Dedicated icon.png in the official Mobile MCP repository; downloaded, decoded as a 512x512 RGBA PNG, and visually reviewed. Selection tier C: MCP project logo.

• discovery directory

  The October 17 directory-derived shortlist included Mobile MCP; directory listing was used for discovery only.

• official or maintainer tool reference

  Maintainer repository documents mobile automation capabilities and platform-dependent tools; seven stored names are a partial snapshot.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.