Skip to main content
Mobilerun runs AI agents that control real Android and iOS devices. Give the agent a natural language goal such as “open Settings and turn on dark mode” and it taps, swipes, and types its way to the result. There are two ways to use Mobilerun. Pick the path that matches your project and then follow its quickstart.

Cloud API, SDK and MCP

Hosted devices with zero local setup. Authenticate with a dr_sk_ key and call the REST API, the TypeScript or Python SDK, or the MCP server. Start here for most integrations.

Framework, open source and local

Run the open source mobilerun Python package on your own machine against your own Android device over adb. Bring your own LLM provider key.

​
Which path is right for me?

​
Two kinds of API keys

Mobilerun involves two separate credentials. Knowing which one you need avoids the most common setup mistake.
  • Mobilerun cloud key (dr_sk_...) authenticates you to the Cloud API, SDK, and MCP server. The agent’s LLM calls are billed from your credit balance, so you do not need your own model key. Create one on the API Keys page.
  • LLM provider key (GOOGLE_API_KEY, OPENAI_API_KEY, and similar) is used only by the open source Framework running on your own machine. The Framework calls the model provider directly, so there are no Mobilerun credits and no dr_sk_ key involved.
If you use the Cloud you only need a dr_sk_ key. If you run the Framework locally you only need an LLM provider key. A single path never needs both.

​
Next steps

Cloud Quickstart

Run your first cloud task in TypeScript, Python, or cURL.

Framework Quickstart

Install the open source package and run a local agent.

API Keys

Create and manage your dr_sk_ cloud keys.

Agent configuration

Every task parameter, including models, vision, reasoning, stealth, memory, and structured output.