mobile

Mobile Next - MCP server provides a unified, platform-agnostic interface to automate and interact with native iOS and Android apps and devices (real devices, simulators, and emulators). It exposes a collection of MCP tools such as mobile_list_available_devices, mobile_get_screen_size, mobile_launch_app, mobile_take_screenshot, mobile_click_on_screen_at_coordinates, mobile_type_keys, and more, allowing agents and LLMs to perform cross-platform automation through structured accessibility snapshots or coordinate-based interactions. The server is designed to work without requiring deep native platform knowledge by translating high-level actions into device-specific commands via the MCP layer. You can run the server behind an automation stack, invoke its tools programmatically, and compose multi-step flows driven by an LLM across iOS and Android ecosystems. The toolset supports common mobile automation tasks like device discovery, app management, screen interaction, and navigation, with fallbacks that leverage screenshot-based analysis when accessibility data is sparse.

Prerequisites:

• Node.js and npm installed on your machine (or a runtime environment that can execute npm/npx).
• Access to the internet to fetch the MCP server package from npm.

Installation steps:

1. Install Node.js and npm if not already installed. Example (on macOS with Homebrew):

brew install node

2. Run the MCP server via npx (this fetches the latest release and runs it directly):

npx -y @mobilenext/mobile-mcp@latest

3. Alternatively, explicitly install the package locally and run the server entrypoint if you prefer a local install:

npm install -D @mobilenext/mobile-mcp@latest
node node_modules/@mobilenext/mobile-mcp/dist/server.js

4. Verify the server starts and is reachable through your MCP client configuration (e.g., Amp, Cline, Claude Code) using the provided mcp_config example.

Notes:

• The server exposes a set of tools under the mobile-mcp namespace for device management, app management, screen interactions, and input/navigation.
• Ensure your environment has access to connected devices or emulators/simulators for testing automation.

Tips and tips:

• The MCP server supports iOS and Android across real devices, simulators, and emulators using a unified API. Tests can use accessibility snapshots when available, or fall back to coordinate-based interactions if necessary.
• Common integration patterns include adding the server to Amp, Cline, or Claude-based workflows via the provided mcp_servers configuration. Examples are included in the README under Amp, Cline, and Claude Code sections.
• If you encounter connectivity or device discovery issues, confirm that devices are discoverable from the host, that required permissions (e.g., Developer mode, accessibility, or USB debugging) are enabled, and that the MCP server has permission to access them.
• Environment variables can be used to customize logging or device filtering if supported by future updates; refer to the wiki for advanced configuration options.
• The npm package name to reference in your project is @mobilenext/mobile-mcp.