mobile-next/mobile-mcp

Mobile Next – Mobile MCP Server

What it is – A Model Context Protocol (MCP) server that lets AI agents (Claude, Gemini, Copilot, etc.) control iOS and Android devices through a single, platform‑agnostic API. It works with simulators, emulators, and real phones, exposing tools for device management, app lifecycle, UI interaction, screen capture, and crash reporting.

Why it matters – By exposing the native accessibility tree instead of raw screenshots, the server can drive apps quickly and cheaply while still falling back to coordinate‑based taps when needed. This makes it possible to write prompts like “open the Weather app, read tomorrow’s forecast for Berlin and send it to Slack” and have an LLM execute the steps on a real device without any iOS/Android‑specific code.

Key capabilities

• Unified API for iOS simulators, iOS real devices, Android emulators, and Android real devices.
• Accessibility‑first interaction – reads UI elements from the native accessibility tree, providing deterministic, structured data.
• Full device control – taps, swipes, gestures, hardware buttons, app install/launch/terminate, deep links, orientation changes, screen recording, crash‑report retrieval.
• Multiple client integrations – works with Claude Code, Codex, Gemini, GitHub Copilot, Antigravity, and any other MCP‑compatible client.
• Deployable as a local stdio server or an SSE HTTP server (with optional bearer‑token auth) for CI/CD or cloud scaling.

Typical workflow

1. Install the server via npx @mobilenext/mobile-mcp@latest (or through the VS Code “Install Server” badge).
2. Add the server to your AI‑assistant client’s MCP configuration (JSON snippet shown in the README).
3. Prompt the assistant to run a tool, e.g. mobile_list_available_devices → get a list of connected simulators/emulators.
4. Use higher‑level tools like mobile_click_on_screen_at_coordinates or mobile_type_keys to perform the desired UI actions.

Installation & setup

• Prerequisites: Xcode command‑line tools (iOS), Android Platform Tools, Node v20+, and for real iOS devices also go-ios + WebDriverAgent + a tunnel.
• One‑line config (works for most clients):

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

• The README lists detailed add‑on steps for many MCP‑enabled IDEs/clients (Amp, Antigravity, Claude Code, Codex, Copilot, Cursor, Gemini, Goose, Kiro, opencode, Windsurf).

Running

• Default: runs over stdio (ideal for local development).
• SSE mode: npx @mobilenext/mobile-mcp@latest --listen 3000 to expose a HTTP endpoint; optional MOBILEMCP_AUTH env var adds bearer‑token protection.
• Telemetry can be disabled with MOBILEMCP_DISABLE_TELEMETRY=1.

Ecosystem

• Part of the Mobile Next toolkit:
  • mobilewright – deterministic test framework built on top of MCP.
  • mobilecli – low‑level CLI that MCP wraps.
  • Mobile Next Cloud – hosted real devices that can be accessed via the same MCP calls.

Roadmap & community

• Ongoing development is tracked in ROADMAP.md and driven by community feedback.
• Contributions are welcomed; the repo includes CONTRIBUTING.md, a code of conduct, and a Slack community for support.

Bottom line – Mobile MCP provides a concrete bridge between large language model agents and real mobile devices, enabling scalable, script‑free automation of iOS and Android apps.