clousd-mcp: real Android phones for your AI agent

Clousd MCP server gives any MCP-capable agent real Android phones in the cloud. Each device is built as a specific handset (Pixel, Galaxy, Xiaomi, Motorola, OnePlus and 150+ more, Android 12 to 17) with Google Play inside and its own network exit, so apps behave the way they do on the phone in a user's pocket.

Your agent does not have to tap every button itself. It gives a phone the goal in plain words - "open the app, sign in with the saved work login and tell me what the order page shows" - and Clousd's own phone agent works the screen and comes back with the answer, a step-by-step replay and, if asked, JSON in your schema. One call can give the same task to up to 32 phones at once. When your agent wants to drive the screen itself, observe and act are there too.

Docs: clousd.com/docs/mcp. Source: github.com/Clousd-Android/clousd-sdk.

Tools

Connect

Hosted server, no install

https://api.clousd.com/mcp (streamable HTTP).

• Claude.ai, ChatGPT and other apps with connectors: add the URL; the app opens Clousd's sign-in page (OAuth 2.1) and you allow access. Disconnect any time in the dashboard: Settings → Connections → Connected apps.
• Coding agents and other clients: send your key in the header.

{
  "mcpServers": {
    "clousd": { "url": "https://api.clousd.com/mcp", "headers": { "Authorization": "Bearer cl_live_..." } }
  }
}

claude mcp add --transport http clousd https://api.clousd.com/mcp --header "Authorization: Bearer cl_live_..."

The key goes only in the Authorization header: a key in the address is refused (addresses end up in logs and histories). Without a header the server answers 401 with the OAuth metadata, which is how connector apps start the sign-in.

Local (stdio)

pip install clousd-mcp

{
  "mcpServers": {
    "clousd": { "command": "clousd-mcp", "env": { "CLOUSD_API_KEY": "cl_live_..." } }
  }
}

Keys: dashboard → Settings → Connections → API keys. A read key can look but never acts; a read & write key can act and run tasks.

A session

account                                         -> plan, 4 phones, no warnings
devices                                         -> "Pixel 7 #1" running, "Galaxy A35 #2" running
credentials package=com.example.shop            -> use: com.example.shop/work (username, password)
run task="Open the Example Shop app, sign in and tell me how many orders are on the Orders page"
    devices="1,2" credentials="com.example.shop/work"
                                                -> status running, next: run_status in 20-60 s
run_status run=r_8f2c wait_seconds=40           -> completed; Pixel 7 #1: "3 orders", Galaxy A35 #2: "3 orders";
                                                   replay https://clousd.com/app/?run=r_8f2c

Settings

Upgrading from 0.3

1.0 gives phones goals instead of scripts: run / run_status / answer replace fleet and recipe; saved logins (credentials) replace resources accounts; reading the phone moved into act; network, snapshots and inspect are no longer MCP tools (the REST API and the Python client still have proxies, snapshots and device reads). Keys in the URL (?api_key=, ?config=) are no longer accepted - send the Authorization header or connect with OAuth.

mcp-name: io.github.Clousd-Android/clousd-mcp

License

MIT