Power your agent
URL ของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
https://api.clousd.com/mcpปุ่ม Claude ด้านบนจะเปิด Claude พร้อมกรอกชื่อและ URL ให้แล้ว คุณยังต้องยืนยันที่นั่นเอง
claude mcp add --transport http io.github.clousd-android-clousd-mcp https://api.clousd.com/mcpRun in a terminal.
{ "mcpServers": { "io.github.clousd-android-clousd-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.clousd.com/mcp" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดEvery agent framework can tap a phone. Almost none has a phone worth tapping.
Clousd is the phone. Each device is a full Android system built as a specific real model, Pixel to Galaxy to Xiaomi, with the hardware identity, Google Play, cameras, sensors and network of the handset in a user's pocket. Your agent, your script or your test suite drives it over HTTPS: look at the screen, act on it, check the result, reset to a saved state, clone it a hundred times. Apps see a phone, not an emulator, so the agent sees the screens a person sees.
This repository is the public side of it: the OpenAPI description, the Python client, the MCP server and the agent loop. Early access: keys on request at clousd.com/agents.
Pick one from each column. They all compose.
The phone stays the same whatever you plug in. A new model release is a free upgrade to your phone agent.
The phone taps what you'd tap
observe: a fresh screenshot with every element numbered, the app in front, and the UI tree with text, ids and boundsact: tap by element number or point, long press, swipe, scroll, type in any language, keys, open apps and links,
intents, settings pages, clipboard, notification shade; the server waits until the screen settles and refuses an
action taken on a stale screen (409 stale)inspect: notifications, clipboard, app versions, crashes and ANRs from the log, health, without touching the screenA phone that apps believe
Teach it once, replay for free
Scale the fleet
POST /groups, c.run_recipe(...), MCP
fleet), each phone with its own login or caption, starts spread so the phones do not act in lockstepEmulators are the first thing an app checks for. Goldfish hardware, emulator builds, no SIM, a datacenter IP: the "unusual activity" path starts before your agent has tapped anything. A phone built as a real model with a real-looking network takes the same code path a user takes.
Every episode should start from the same state. Evaluation, training and testing are only comparable when run N starts exactly where run 1 did. Snapshots restore in seconds; clones give parallel episodes without copying a phone by hand.
Thinking costs tokens, replaying costs nothing. Use a model for the unknown task; once a flow works, record it and replay it as a recipe. The same phone runs both.
Your keys, your phones. API keys carry a scope (read or control) and an explicit list of phones. A read key
can observe and inspect but never acts. Over HTTP the key travels with every request; the hosted MCP server keeps
nothing between requests.
pip install clousd-mcp
{
"mcpServers": {
"clousd": { "command": "clousd-mcp", "env": { "CLOUSD_API_KEY": "cl_live_..." } }
}
}
Or no install at all, the hosted server:
{
"mcpServers": {
"clousd": { "url": "https://api.clousd.com/mcp", "headers": { "Authorization": "Bearer cl_live_..." } }
}
}
pip install clousd
export CLOUSD_API_KEY=cl_live_...
from clousd import Clousd
c = Clousd()
phone = c.device("dev_04f2")
snap = next(s for s in phone.snapshots() if s["restorable"])
phone.restore(snap["id"]) # every run starts from the same state
phone.open_app("com.android.chrome")
phone.tap_text("Search")
phone.type("weather in Berlin")
phone.key("enter")
phone.wait_text("Berlin", timeout=30)
obs = phone.observe(width=540) # screenshot + UI tree + seq
phone.act("tap", seq=obs["seq"], x=540, y=1200, settle=True)
clousd run "Open Settings and tell me the Android version" --device dev_04f2 \
--model-url http://127.0.0.1:8080/v1 --model qwen # any OpenAI-compatible endpoint
clousd run "Find the cheapest flight to Lisbon next Friday" --device dev_04f2 --save-recipe flights.json
clousd recipe flights.json --device dev_04f2 # replay without a model
clousd bench --device dev_04f2 --model-url ... # the built-in task set, scored
clousd explore com.android.settings --device dev_04f2 # map the screens of an app, draft an app pack
An agent that taps every phone step by step through observe/act is slow and burns model calls. For app tasks use a
recipe, and for many phones one call:
from clousd import Clousd
c = Clousd()
phones = [d for d in c.devices() if d.state == "running"] # 10 phones, any servers
for r in c.recipes("instagram"): # what can run without a model
print(r["action"], "-", r["about"], [i["name"] for i in r["inputs"]])
# sign every phone into its own account: one call, the phones work in parallel
accounts = {"dev_01": {"login": "anna.k", "password": "..."}, "dev_02": {"login": "mark_t", "password": "..."}}
job = c.run_recipe(list(accounts), "com.instagram.android", "login", vars_by_device=accounts)
print(job.failed) # [] - or the devices to look at
# warm all ten up for 15 minutes, starts spread over 20-90 s so they do not move in lockstep
job = c.run_recipe(phones, "com.instagram.android", "warm",
{"seconds": 900, "comment_chance": 0.1, "comments": "Love this|So good|Wow"}, stagger=[20, 90])
for name, r in job.results.items():
print(name, r["state"], r["steps"][-1]["output"])
Accounts, proxies and media come from the account too, so a whole morning is a few calls:
p = c.add_proxy("res.example.net:9000:user:pass", ip_type="residential", rotate_url="https://example.net/rotate?key=...")
c.bind_proxy(p["proxy"]["id"], phones) # exit, time zone, SIM follow the proxy
ids = c.add_accounts([{"platform": "com.instagram.android", "login": "anna.k", "password": "...", "device": "dev_01"}])
c.run(phones, [{"op": "login", "package": "com.instagram.android", "account": "linked"}]) # passwords stay on the server
m = c.upload_media("beach.jpg")
c.run(phones, [{"op": "publish", "package": "com.instagram.android", "text": "post", "media_id": m["id"], "caption": "Sunday"}])
Over MCP the same is the fleet tool: fleet op=recipes app=instagram, then fleet op=run devices=all package=com.instagram.android action=warm vars={"seconds":"900"} stagger=20,90, then fleet op=status job=... until
it is done. Over HTTPS it is GET /v1/recipes and POST /v1/groups (below).
curl -H "Authorization: Bearer cl_live_..." https://api.clousd.com/v1/devices
curl -H "Authorization: Bearer cl_live_..." "https://api.clousd.com/v1/devices/dev_04f2/observe?w=540"
curl -H "Authorization: Bearer cl_live_..." -H "Content-Type: application/json" \
-d '{"op":"tap_text","text":"Search","settle":true}' https://api.clousd.com/v1/devices/dev_04f2/act
curl -H "Authorization: Bearer cl_live_..." https://api.clousd.com/v1/recipes
curl -H "Authorization: Bearer cl_live_..." -H "Content-Type: application/json" \
-d '{"phones":["dev_01","dev_02"],"stagger":[20,90],
"steps":[{"op":"recipe","package":"com.instagram.android","action":"warm","vars":{"seconds":"900"}}]}' \
https://api.clousd.com/v1/groups # -> 202 {"job":{"id":...}}; GET /v1/jobs/{id} for progress
observe dev_04f2 -> screenshot, "On screen: com.android.chrome", elements 1..34
act dev_04f2 tap element=12 -> "ok" (settled in 0.6 s)
act dev_04f2 type text="weather in Berlin"
act dev_04f2 key text=enter
act dev_04f2 wait_text text=Berlin -> "found after 1.9 s"
inspect dev_04f2 crashes -> []
snapshots dev_04f2 restore snapshot_id=snap_7f3 -> "restored" (next episode starts clean)
observe with the UI tree takes about 1 to 3 seconds, act with settle 0.3 to 1 second; a full agent step with the
model is typically 5 to 10 seconds.
Keys have a scope (read or control). Limits: 120 requests a minute per key and device, 600 a minute per key across
devices, 60 a minute for everything else; the server answers 429 with Retry-After and the Python client waits and
retries. Errors are JSON: {"error": "short_code", "message": "what happened"}. Full description with every field:
openapi.yaml; human-readable reference: clousd.com/docs/reference.
clousd bench scores a task set, python/examples/episode.py is the
minimal loop.clousd run and clousd bench: any OpenAI-compatible endpoint; recipes and the API need noneIs this an emulator? No. Each phone is a full Android system built as a specific real model; apps read the same hardware identity the real handset reports. Emulator detection does not trigger.
Which MCP clients work? Anything that speaks MCP over stdio or streamable HTTP. Six tools, each with parameter descriptions, a result schema and read-only/destructive hints.
Which models work? For MCP, whatever your client runs. For clousd run, any OpenAI-compatible chat endpoint with
tool calling; vision is used when the model has it and the loop falls back to the numbered element list when it does
not.
Can I run flows without a model? Yes. Record once (clousd record, clousd run --save-recipe, or the dashboard)
and replay with clousd recipe or the recipe tool on any number of phones.
Can several agents share a phone? One recipe at a time per phone; seq in observe/act makes concurrent actors
safe: an action taken on a screen that has since changed is refused, not guessed.
Where does my data go? The phone runs on Clousd servers; its traffic leaves only through the exit you chose. Keys are per account, per scope, per phone list, and revocable at any time.
pip install -e python
pip install -e mcp
python -m unittest discover -s python/tests # offline: a fake server and a scripted model, no key needed
Releases go to PyPI as clousd and clousd-mcp
and to the MCP registry automatically.
io.github.Clousd-Android/clousd-mcp · hosted MCP endpoint: https://api.clousd.com/mcpMIT. See LICENSE.
Cloud Android phones for AI agents: give phones a task in plain words and get the answer
{ "mcpServers": { "io.github.clousd-android-clousd-mcp": { "url": "https://api.clousd.com/mcp", "headers": {} } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก http สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: CLOUSD_API_KEY
Clousd เข้าถึงได้ผ่าน HTTP
ตรวจสอบล่าสุดเมื่อ 2026-11-16 Cloud Android phones for AI agents: give phones a task in plain words and get the answer