Add Mobilebox as a remote MCP server, then give your agent one bounded task. The server is https://mobilebox.dev/mcp: stateless Streamable HTTP with a bearer API key. Your agent does the reasoning; Mobilebox supplies an Android sandbox, a cloud Android 14 phone (arm64), and the tools to drive it.

Connect Claude Code

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

Claude Code stores the expanded header in ~/.claude.json. To share the server through a committed .mcp.json, keep the key out of the file:

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

Keep "type": "http": Claude Code treats a url entry without it as a stdio server and skips it. Cursor reads url and headers from .cursor/mcp.json and writes the variable as ${env:MOBILESANDBOX_API_KEY}. Client documentation reviewed on October 30, 2026.

Sign up with GitHub at /signup; new workspaces get free credit. Keys come from the dashboard.

What the agent can call

create_phone, start_phone, park_phone, delete_phone and list_phones manage the phone; create and start return its first screen. install_app (from a download URL), list_apps and uninstall_app manage apps, and app_logs reads an app’s own log lines and how it last exited, such as a crash. push_file puts a file in the phone’s Downloads for an app to import, and pull_file reads back a file or folder an app wrote. observe, act and screenshot read and drive the screen. set_device sets timezone, locale, location and proxy, the battery (battery with level and charging) and the picture an app gets when it asks the camera app for a photo (camera_image, e.g. a QR code). The receive_sms action in act delivers a test SMS, such as a one-time code, to the apps on the phone. watch_phone gives the user a live view of the screen with each action drawn on it. publish_proof returns the run’s proof as a PR comment: passed or failed, time, cost and screenshots, plus a video of the run if record_screen recorded one. request_capability tells the Mobilebox team what you needed and the tools don’t offer yet. The agent guide has the loop.

First task

Ask: “Use Mobilebox. Create a phone named settings-check. Open com.android.settings. Observe the screen and report a visible label. Park the phone even if the task fails. Do not install apps or sign into accounts.”

Expect create_phone, act, park_phone. Read act’s result text: it stops at the first failed action and says so. A country such as DE also sets the display language, so English text targets stop matching.

Hosted or local?

OptionWhere the phone runsYou own
mobile-mcpYour emulators, simulators or devices, Android and iOSDevices and SDKs
Appium MCPLocal Appium drivers or your Appium serverDrivers and devices
MobileboxCloud Android 14 phone (arm64)Your app and agent; no ADB, Android only

Scope from each project’s documentation, October 30, 2026. For a hosted platform with its own agent, see Mobilebox and Mobilerun.

What is shown

The recorded run is eight MCP calls, observe and act, that find the Matterhorn’s height on Wikipedia; responses and frame hashes are in the manifest. It does not show your client, your app, Google Play services, a physical phone or iOS. Finish with park_phone or delete_phone; a closed chat is not cleanup.