Mobilebox
Log inGet started
Menu

API + MCP.
Android,
read as text.

Mobile Sandboxes, controllable by your agents.

Explore the APIReplay the recorded run

$0.01 per phone-minute. Parked phones are free.

Android screenshot of Fossify Notes holding a four-line release checklist

GET /v1/phones/{phone_id}/observe

app: org.fossify.notes[1] Button desc="Search" (657,146)[2] Button desc="Create a new note" (784,146)[3] Button desc="Undo" (911,146)[4] Image desc="More options" (1027,146)[5] TextField "Release checklistRun the Android smoke testInspect the accessibility treePark the phone when finished" [focused] (540,1252)
Recorded on an Android 14 arm64 sandbox. MCP’s observe tool prints the same list.

A checklist that outlives a restart

One recorded run on an Android 14 sandbox: eight calls over REST and MCP, each paired with the screen it left behind.

Task Write a release checklist. Verify it survives a restart.

Android screenshot: Create a sandbox

Captured screen

8 steps

Loading recorded evidence…

    Create a sandbox

    POST /v1/phones?wait=ready

    Android sandbox ready.

    Inspect the captured request and response
    Choose a step to inspect its captured request.
    Recorded replay of one run on 29 October 2026, not a live phone. Playback is shortened; the times shown are the original measurements.Download the recording (JSON)

    Connect over MCP or REST

    Claude Code, Codex or any HTTP MCP client gets the phone as tools. Your own code calls the same sandbox over REST.

    12 MCP tools

    • list_phones
    • create_phone
    • start_phone
    • park_phone
    • delete_phone
    • set_device
    • install_app
    • list_apps
    • uninstall_app
    • observe
    • act
    • screenshot
    Read the quickstart

    Add the phone tools to Claude Code

    terminal, Claude Code
    claude mcp add --transport http \
  mobilebox https://mobilebox.dev/mcp \
  --header "Authorization: Bearer $MOBILEBOX_API_KEY"

    Using Codex or another client? See every agent setup

    Five calls run the loop

    Create a phone, read and act on its screen, park it when the task is done. Each state keeps its own limits.

    ready

    An Android 14 phone, ready for your apps

    One request provisions it; wait for ready before you act. Set the country, locale and timezone when you create it.

    REST
    POST /v1/phones?wait=ready
    MCP
    create_phone
    Running
    3 phones per workspace
    Kept
    10 phones, parked ones included
    Full server
    503 box_full with a retry time
    Every control in the agent guide

    The field guide

    24 articles on Android agents: guides, engineering notes, comparisons and decisions.

    Open the journal

    Give your coding agent an Android sandbox over MCP

    Add the remote MCP server to Claude Code or Cursor, see every phone tool, run a bounded first task and know what is proven.

    Guides3 min read

    Why your agent tapped the wrong thing

    Understand stale screen references, choose stable targets, and recover without repeating side effects.

    Engineering2 min read

    A timeout does not mean the tap never happened

    Reconcile phone creation, inspect partial action batches and check side effects before retrying an uncertain Android operation.

    Engineering4 min read

    Screenshot or accessibility tree? Choose the evidence your agent needs

    Choose structured Android observations for labels and state, screenshots for pixels, and synchronized evidence when both matter.

    Engineering3 min read

    $0.01 per phone-minute

    Billed per second while a phone is ready, with a one-minute minimum per session. Parked phones are free.

    Explore the API
    Pricing and limits
    SessionBootReadyBilledCost
    ses_fuhxfawlquvs18.1 s10.1 s60 s$0.010000
    ses_r7ybhndnzqud10.5 s2.8 s60 s$0.010000
    The recorded run’s own bill, from its sessions endpoint. Boot time is not billed; each session billed the one-minute minimum.