Mobilerun logo

Mobilerun

Automates real Android and iOS devices through natural-language commands, screenshots, UI inspection, gestures, and Python workflows.

Install Mobilerun

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mobilerun": {
      "command": "uvx",
      "args": [
        "mobilerun"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

uvx mobilerun

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1d ago.

Overview

  • mobile-automation
  • android
  • ios
  • developer-tools

The mobilerun MCP server connects LLM agents to real Android and iOS devices for UI inspection and interaction. It combines accessibility trees, screenshots, text input, gestures, app launching, and device-state access to execute direct or multi-step tasks. Use it for local mobile automation through the CLI, Docker, or Python rather than for managed cloud device operations. Android requires ADB, Developer options, USB debugging, and the Mobilerun Portal; iOS uses a separate Portal setup flow.

Use cases

  • Automate Android settings changes with natural-language commands
  • Inspect mobile UI state and screenshots
  • Run multi-step workflows across phone apps
  • Build custom device workflows with Python
  • Debug agent execution with traces and saved trajectories

Key features

  • Android and iOS device control
  • Accessibility-tree and screenshot inspection
  • Tap, swipe, text input, and app launching
  • CLI, Python, and Docker execution
  • Vision and reasoning modes
  • Structured output and execution tracing

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

12/12 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · mobilerun (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars9.7kStargazers on the source repository.
Last commit5d agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Mobilerun works

What mobilerun MCP server does

The mobilerun MCP server gives language-model agents a way to operate physical Android and iOS devices. Agents can inspect the current interface, interpret screenshots, launch apps, enter text, perform taps and swipes, and complete workflows that span several actions. Results can be returned through command-line runs or Python-based automation.

The framework is intended for local execution. It is separate from Mobilerun Cloud, which provides managed infrastructure, hosted devices, dashboards, REST APIs, SDKs, and cloud workflows. Choose the local framework when the agent and target phone should remain under your own runtime control.

How it works

Mobilerun uses the device's Portal runtime to expose interaction and state to the agent. On Android, the Portal app works with accessibility information and screenshots to describe the current UI. Vision mode sends screenshots to the model, while vision-only mode supports applications that do not expose useful accessibility-tree data.

Tasks may run directly or with reasoning enabled. Direct runs suit simple commands, while reasoning mode uses manager-executor planning for longer sequences. The framework also supports structured results, saved trajectories, detailed logs, and tracing through Arize Phoenix or Langfuse.

Setup and configuration

Install the package with uv. Use uv tool install mobilerun for CLI use, or uv pip install mobilerun when combining the CLI with Python integration. Python 3.11 through 3.13 is supported; Python 3.14 is not currently supported. Anthropic support is installed separately with the anthropic extra.

For Android, install ADB, enable Developer options and USB debugging, then run mobilerun setup to install and prepare the Portal app. Run mobilerun ping to check the connection. The mobilerun configure command guides provider, authentication, and model selection. Provider keys can also be supplied through environment variables such as OPENAI_API_KEY, GOOGLE_API_KEY, and ANTHROPIC_API_KEY. iOS devices use the separate iOS Portal flow.

Tools and capabilities

The mobilerun MCP server supports:

  • Natural-language device commands from the CLI
  • Python automation and custom tools
  • UI-tree inspection and screenshot-based understanding
  • Taps, swipes, text entry, app launching, and device-state access
  • Vision and vision-only execution modes
  • Reasoning mode for multi-step workflows
  • Structured output, app cards, and credential support
  • Macro replay, debugging, Docker execution, and telemetry

Models can be supplied through OpenAI, Anthropic, Gemini, xAI, Ollama, DeepSeek, OpenRouter, and OpenAI-compatible providers, subject to the relevant configuration and credentials.

Limitations and notes

The mobilerun MCP server requires device-specific preparation rather than providing an independent simulator. Android depends on ADB and an accessible Portal installation. iOS setup is handled through a different Portal process. The local framework runs the agent on your machine; managed phones, hosted devices, and cloud API workflows belong to Mobilerun Cloud instead.

For applications without useful accessibility data, screenshot-based operation may be necessary. Longer or more complex tasks may need reasoning mode, and execution can be inspected with debug output, saved trajectories, or supported tracing systems.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Mobilerun

mobilerun is an MCP server that connects LLM agents to real Android and iOS devices through a Portal runtime. Its main tools support UI inspection, screenshot understanding, tapping, swiping, text entry, app launching, device-state access, and multi-step mobile workflows from the CLI or Python.

Install it with `uv tool install mobilerun` for CLI use or `uv pip install mobilerun` for CLI and Python integration. Use Python 3.11 through 3.13, then run `mobilerun setup` and `mobilerun configure`.

Install ADB, enable Developer options and USB debugging, and run `mobilerun setup`. The command installs the Mobilerun Portal app and prepares the device; `mobilerun ping` checks whether the Portal is accessible.

Yes, mobilerun supports iOS through a separate iOS Portal flow.

Yes, install the package with `uv pip install mobilerun` to use its Python integration. Python workflows can add custom tools and structured output for mobile automation.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMobilerun AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mobilerun?style=directory)](https://allmcps.com/mcp/mobilerun)
HTML Embed
<a href="https://allmcps.com/mcp/mobilerun"><img src="https://allmcps.com/api/badge/mobilerun?style=directory" alt="Mobilerun on AllMCPs" /></a>