Mobile MCP
Mobile mcp mcp server connects Mobile MCP to AI assistants that speak the Model Context Protocol. Mobile MCP.
This is a Model Context Protocol (MCP) server that enables scalable mobile automation, development through a platform-agnostic interface, eliminating the need for distinct iOS or Android knowledge. You can run it on emulators, simulators, and real devices (iOS and Android). This server allows Agents and LLMs to interact with native iOS/Android applications and devices through structured accessibility snapshots or coordinate-based taps based on screenshots.
Once connected, the assistant can call these 3 tools directly:
Authorization — To require Bearer token authorization on the SSE server, set the MOBILEMCP_AUTH environment variable:Workflows — You can specify detailed workflows in a single prompt, verify business logic, setup automations. You can go crazy:Telemetry — Mobile MCP collects anonymous usage telemetry via PostHog. To disable it, set the MOBILEMCP_DISABLE_TELEMETRY environment variable:The server is distributed via npm as @mobilenext/mobile-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
The server reads one environment variable: MOBILEMCP_DISABLE_TELEMETRY. Keep credentials in your client's env block or a secrets manager rather than committing them.
What you will need to connect MCP with your agent and mobile devices: - Xcode command line tools - Android Platform Tools - node.js v20+ - MCP supported foundational models or agents, like [Claude
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Mobile MCP sits in that group, and the shape of its toolset — Authorization, Workflows, Telemetry — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| Authorization | To require Bearer token authorization on the SSE server, set the MOBILEMCP_AUTH environment variable: |
| Workflows | You can specify detailed workflows in a single prompt, verify business logic, setup automations. You can go crazy: |
| Telemetry | Mobile MCP collects anonymous usage telemetry via PostHog. To disable it, set the MOBILEMCP_DISABLE_TELEMETRY environment variable: |
{
"mcpServers": {
"mobile-mcp": {
"command": "npx",
"args": ["-y", "@mobilenext/mobile-mcp@latest"]
}
}
}Configuration as documented by the project. Restart the client after saving.
What you will need to connect MCP with your agent and mobile devices: - Xcode command line tools - Android Platform Tools - node.js v20+ - MCP supported foundational models or agents, like [Claude
| Variable | Description | Required |
|---|---|---|
| MOBILEMCP_DISABLE_TELEMETRY | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.