Mobilebox
Provides cloud Android phones/sandboxes that agents can control to create, resume, park, and delete phones; install or uninstall apps from APK URLs; and observe the screen as numbered elements before performing taps, long presses, swipes, scrolling, typing, key events, and app launch/close actions.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
Mobilebox gives your AI agent a phone it can use. Claude Code, Codex, Cursor or your own agent loop creates a cloud Android 14 phone, reads the screen as numbered elements, taps, types, installs your APK, then parks or deletes the phone. One phone per task or pull request costs a few cents: $0.01 per phone-minute, billed per second.
Measured, 2026-11-08 (method, scripts and CSV): a Mobilebox phone was ready for its first screenshot in 19.4 s (median of 10) and a 10-minute session cost $0.10. On a GitHub Actions runner, the same start took 20.3 s, against 50 s for the Android emulator with KVM and 813 s without it (one run).
Fair comparison: in the same benchmark Limrun started in 0.98 s ($0.04 a minute on its $20 plan), and Clousd lists a lower price ($0.004 a minute, as published on 2026-11-10). All cloud phones for AI agents, compared.
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 prompt2. Add Mobilebox to your agent.
claude mcp add --transport http mobilebox https://mobilebox.dev/mcp \
--header "Authorization: Bearer $MOBILESANDBOX_API_KEY"Codex, ~/.codex/config.toml:
[mcp_servers.mobilebox]
url = "https://mobilebox.dev/mcp"
bearer_token_env_var = "MOBILESANDBOX_API_KEY"Cursor: the Add to Cursor button above installs the URL alone and Cursor signs you in over OAuth, no key. Or .cursor/mcp.json with the key:
{ "mcpServers": { "mobilebox": { "url": "https://mobilebox.dev/mcp", "headers": { "Authorization": "Bearer ${env:MOBILESANDBOX_API_KEY}" } } } }Claude Code, shared through a committed .mcp.json without the key in it. Keep "type": "http", or Claude Code treats the entry as a stdio server:
{ "mcpServers": { "mobilebox": { "type": "http", "url": "https://mobilebox.dev/mcp", "headers": { "Authorization": "Bearer ${MOBILESANDBOX_API_KEY}" } } } }Other clients: any MCP client with Streamable HTTP and a custom header. Hand-written clients also send Accept: application/json, text/event-stream. The registry entry is server.json.
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).
Related MCP server: mobilerun-mcp
Watch your agent
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 windowOver 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. Sign in once with OAuth from any MCP client that supports it (Claude, ChatGPT, Cursor, VS Code): add https://mobilebox.dev/mcp and approve. Or send your key as Authorization: Bearer.
Tool | What it does | Arguments ( |
| List this project's phones. | – |
| Create a phone and wait until it is ready. |
|
| Resume a parked phone and wait until it is ready; its apps, data and logins are kept. |
|
| Park a phone: shuts it down and stops billing. |
|
| Delete a phone and everything on it: apps, data and logins. |
|
| Set where the phone is: country and city together, or timezone, locale and GPS one by one, plus the network its IP comes from or a proxy; its battery; and the picture its camera app returns. |
|
| Install or update an app from a public download URL: an APK (arm64-v8a or universal) or a split bundle (.apks/.xapk; the splits this phone needs are picked), up to 2 GB. |
|
| List the apps the user installed on this phone, not the system apps. |
|
| Uninstall an app and delete its data. |
|
| Read the current screen as a numbered element list. |
|
| Run 1–20 actions on the phone in order (tap, type, swipe, scroll, keys, open or close apps, waits) and stop at the first failure. |
|
| Take a screenshot of the phone. |
|
| Get a link to watch the phone live, for the user: its screen with each of your actions drawn on it (cursor, taps, swipes, typed text) and a caption per step. |
|
| Publish this run's proof for a pull request: returns Markdown to post as the PR comment (passed or failed, duration and cost from the phone's session, up to 3 screenshots) and the screenshot URLs. |
|
| Tell Mobilebox about something you needed and we don't offer yet; it's recorded and answered by the team. |
|
Actions for act: tap, long_press, swipe, scroll, scroll_to, type, key, back, home, open_app, close_app, wait, wait_for. Targets: {"text":"OK"} (best default), {"ref":3}, {"id":"com.app:id/login"}, {"desc":"Navigate up"}, {"x":540,"y":1200}. REST only: POST /v1/phones/{id}/apps (APK upload), GET /v1/account, GET /v1/phones/{id}/sessions. Full vocabulary: API reference.
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).
Example | Shows | Needs |
create, observe, act, screenshot, delete | bash, curl, jq | |
open the live view, then act while you watch | bash, curl, jq; Node for | |
minimal client + Settings check | Python 3.9+, stdlib | |
minimal client + Settings check | Node 24 | |
Claude Code tests the APK you just built | an arm64 or universal APK | |
APK smoke test in a workflow | a repo secret with your key | |
| Python 3.10+ | |
OpenAI Agents SDK, LangGraph, CrewAI, browser-use, Mastra, Vercel AI SDK, Claude Agent SDK | the framework and a model key |
Pricing
Device | Price |
Cloud Android 14 phone (arm64) | $0.01 per phone-minute |
iPhone and iPad ( | $0.05 per phone-minute |
Real Android device ( | $0.03 per phone-minute |
Dedicated devices | from $79 per month |
Billed per second while a phone is ready, with a one-minute minimum per session. Boot time and parked phones are free. New accounts start with $2 of credit; add more from the dashboard. Over 100 devices: contact sales. Pricing.
Up to 20 actions per
actcall, 256 KB of JSON per request, waits up to 55 s per call, APK uploads up to 300 MiB.Phones park after 5 idle minutes (
idle_timeout, 60–3,600 s) and after 15 minutes of running (max_duration, up to 3 hours).All keys of a workspace (called project in the API) share its phones and balance.
Apps with strict root or integrity checks (e.g. Play Integrity) may not run on a cloud phone; use a real Android device for those.
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.
Your key is a bearer token for one workspace. Every key in a workspace can see and control all of its phones and spend its balance. For a hard boundary between two agents or customers, use separate workspaces, not separate keys.
Agent keys only control phones. They cannot sign into the dashboard or create other keys. Revoke or rotate keys in the dashboard.
The phone is a sandbox, not your machine. Each phone is a cloud Android 14 phone on Mobilebox servers in Nuremberg, Germany. There is no public ADB or shell. Phones can reach the internet (or the SOCKS5 proxy you set) but not each other or Mobilebox's internal network.
Screen content goes to your agent, and from there to its model provider. Don't put data on a phone that you aren't allowed to send to your agent's model.
We don't look into phones except to fix a fault you report or when the law requires it. Park keeps apps, data and logins; delete removes them. Deleting a phone does not log out sessions on third-party servers.
Details: privacy policy, key security. Found a vulnerability? See SECURITY.md.
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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Cloud Android phones for AI agents: create a phone, read the screen, tap, type, install APKs, park.
Give your AI agent a real cloud Android phone: push APKs, drive it, get screenshots and logs.
Disposable cloud Android emulators for coding agents: run an APK or PR build, tap, type, screenshot.
Drive cloud Android phones on US mobile IPs. Read the screen, tap, type, install apps and run tasks.
Related MCP Servers
- AlicenseBqualityBmaintenanceEnables AI agents to automate Android and iOS devices, including emulators and physical devices, by capturing screenshots, reading UI accessibility trees, performing touch and text input, and managing app lifecycle and logs.184MIT
- AlicenseCqualityBmaintenanceEnables AI agents to control Android phones, emulators, redroid containers, iOS devices, and cloud-hosted devices through a perceive-act-verify loop of screen reading, taps, gestures, typing, and app launching. Exposes 138 tools for driving screens, elements, and files over adb, Portal APIs, and ios-portal without running ARM-only code on the device.949 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control real cloud phones by reading screens as text, tapping, typing, installing APKs, handing off to humans, and parking devices to stop billing, without ADB or emulators.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to remotely control a real Android phone over MCP with no ADB, root, or emulator, by connecting a broker server to a sideloaded APK. Exposes tools to list devices, capture screenshots, read the UI tree, open links and deep links, and perform taps, swipes, typing, and global navigation actions.1MIT