Mobilebox

Cloud Android phones your agent drives over MCP or REST.
It reads the screen as numbered elements, then taps, types and installs apps.

Website · Docs · Quickstart · MCP registry

_{Phone screens are unedited API screenshots from one recorded run; steps and times are its MCP calls, from the home screen on. Playback shortened.}

_{Ready time: create to ready, three runs on 2026-11-04 (RUNS.md).}

Works with    Claude Code    Codex    Cursor    any MCP client

• Listed in the official MCP registry as dev.mobilebox/mobilebox, tool definitions rated A on Glama.
• Checked on every deploy: an end-to-end run on production that uses only the public docs (create, install, tap, type, park, resume, delete over REST and MCP).

Quickstart

1. Get a key. Sign up with GitHub ($2 of credit, 200 phone-minutes) and create an agent key in the dashboard.

export MOBILESANDBOX_API_KEY=...   # keep it in your shell or secret manager, never in a prompt

2. Add Mobilebox to your agent.

claude mcp add --transport http mobilebox https://mobilebox.dev/mcp \
  --header "Authorization: Bearer $MOBILESANDBOX_API_KEY"

[mcp_servers.mobilebox]
url = "https://mobilebox.dev/mcp"
bearer_token_env_var = "MOBILESANDBOX_API_KEY"

{ "mcpServers": { "mobilebox": { "url": "https://mobilebox.dev/mcp", "headers": { "Authorization": "Bearer ${env:MOBILESANDBOX_API_KEY}" } } } }

{ "mcpServers": { "mobilebox": { "type": "http", "url": "https://mobilebox.dev/mcp", "headers": { "Authorization": "Bearer ${MOBILESANDBOX_API_KEY}" } } } }

3. Give it a task.

Use Mobilebox. Create a phone, open Settings and tell me which Android version it runs. Delete the phone at the end, even if a step fails.

Next: let your agent test the APK you just built, or run the same check in CI. No MCP client? curl/walkthrough.sh does the whole loop over REST (OpenAPI, reference).

Watch your agent

_{A real agent on a Mobilebox phone, recorded in the live view at real speed. One step fails, and the log says why.}

Open a live view of any running phone and see every step as it happens: a cursor that moves to each target, a ripple for every tap, a trail for every swipe, the text as it is typed (dots in password fields), and a caption with its time for each step. Nothing depends on sound, and screen readers announce each caption.

npx mobilebox watch <phone_id>   # with MOBILESANDBOX_API_KEY set: opens the view in its own window

Over MCP, ask your agent to show you the phone: watch_phone returns the link (REST: POST /v1/phones/{id}/view). The dashboard has a Watch button on every running phone. The view is read-only and watching is free. Try it with watch/watch.sh; details in the API reference.

Tools

Phones, apps and the screen over MCP; REST adds binary APK upload, account balance and billed sessions. Without a key, /mcp answers initialize, tools/list and ping; every tools/call needs the key.

Examples

Each creates a phone, checks one outcome and deletes the phone, also when the check fails. All ran against production: on 2026-11-04, and the live view example on 2026-11-05 (RUNS.md).

Pricing and limits

$0.01 per ready phone-minute, billed per second with a one-minute minimum per session. Boot time and parked phones are free. Up to 3 running and 10 kept phones per workspace. Pricing.

Security

Each phone is an isolated Android sandbox on Mobilebox servers in Germany, reachable only through the API. Keys are per workspace, stored hashed and never logged. Mobilebox runs no model: screen content goes only to your agent.

For agents

AGENTS.md is the operating guide: the loop, targets, error recovery and cleanup. Live versions: skill.md, llms.txt.

Questions: hello@mobilebox.dev, or open an issue. MIT for this repository; the hosted service is covered by its terms.