New Mobilerun VA is now in beta — a hosted 24/7 agent for mobile automation
MCP

The mobile MCP server. Real phones for your agent.

Connect Claude Code, Claude Desktop, Cursor or VS Code to real Android and iOS cloud phones. Hosted over HTTP — no ADB, no emulator, no local setup.

1

Get your API key

Sign up at cloud.mobilerun.ai and copy your key from the API Keys tab. It starts with dr_sk_.

2

Connect your agent

Claude Code — paste this into your terminal (replace the key):

terminal
claude mcp add --transport http mobilerun https://api.mobilerun.ai/v1/mcp --header "Authorization: Bearer dr_sk_YOUR_API_KEY"

Claude Desktop, Cursor or VS Code — paste this into your MCP config (in Claude Desktop: Settings → Developer → Edit Config):

claude_desktop_config.json
{
  "mcpServers": {
    "mobilerun": {
      "url": "https://api.mobilerun.ai/v1/mcp",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer dr_sk_YOUR_API_KEY"
      }
    }
  }
}
3

Try it

Restart your agent and ask it something like:

prompt
Spin up a cloud phone and take a screenshot of the home screen.

Your agent now has tools for tasks, devices, apps, credentials and webhooks on real Android and iOS cloud phones.

+

Going deeper: mobile-harness

The MCP server gives any client hosted cloud phones with zero install. For coding agents there's also mobile-harness — portable operating instructions plus the mobilerun_core Python API, which drives cloud phones and local devices (Android via ADB, iOS via portal). Setup is one prompt:

prompt · paste into your agent
Set up https://github.com/droidrun/mobile-harness for me.

Read `install.md` and follow the steps to install `mobile-harness`.

OAuth is also supported — full setup in the MCP server docs.

FAQ

Mobile MCP — common questions.

What is the mobilerun MCP server?+
A hosted Model Context Protocol server that connects MCP clients — Claude Code, Claude Desktop, Cursor, VS Code — to real Android and iOS cloud phones. Your coding agent gets tools for task execution, device operations, app browsing, credential storage and webhooks, without installing anything locally.
How is this different from local mobile MCP servers?+
Most mobile MCP servers run on your machine and control a locally connected device or emulator over ADB. mobilerun's MCP server is remote: it runs against cloud-hosted real devices over HTTP with API-key or OAuth authentication, so agents can operate phones from anywhere — CI, servers, or your laptop — with no ADB setup.
Which MCP clients are supported?+
Any MCP client that supports remote HTTP servers, including Claude Code, Claude Desktop, Cursor and VS Code. Configuration is a single JSON block with your API key.
MCP server or mobile-harness — which should I use?+
Use the hosted MCP server when you want cloud phones with zero install from any MCP client. Use mobile-harness (github.com/droidrun/mobile-harness) when your coding agent should also control local devices — Android via ADB or iOS via portal — through the mobilerun_core Python API. Both work with mobilerun cloud, and you can combine them.
Do the phones pass app integrity checks?+
Yes — the devices behind the MCP server are real physical Android and iOS phones with authentic hardware identity, which pass Google Play Integrity, SafetyNet and iOS App Attest, combined with residential proxies in 195+ countries.

Give your agent a phone.

One JSON block between your coding agent and a real device.