Skip to main content
Glama

Server Details

Cloud Android phones for AI agents: give phones a task in plain words and get the answer

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Clousd-Android/clousd-sdk
GitHub Stars
1
Server Listing
clousd-mcp
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 11 tools

Disambiguation4/5

Tools target distinct areas such as account, devices, run, observe, act, schedules, and library, and descriptions clarify run vs act vs observe. Minor overlap remains between apps and library for APK handling, and act/run both perform phone actions, but the intended boundaries are explicit.

Naming Consistency3/5

Names are mostly single words, but conventions mix nouns (account, apps, devices, schedules), verbs (act, answer, observe, run), singular/plural forms, and run_status uses snake_case. It is readable but not a uniform, predictable pattern.

Tool Count5/5

11 tools is well within a healthy range for a cloud-phone automation server. Complex operations are grouped under op parameters rather than expanding into many separate tools.

Completeness4/5

The surface covers core workflows: device lifecycle, task execution and follow-up, library/app handling, credentials, schedules, and account checks. Minor gaps such as library file deletion or apps listing/removal are not fatal and may be dashboard-managed.

Publisher details

Operator
Clousd · Publisher source
Vendor relationship
First-party · Publisher source
Privacy policy
Not provided
Restrictions
Requires a Clousd account and an API key (early access, request at https://clousd.com/agents/). Usage is billed per minute while a phone runs · Publisher source

Available Tools

11 tools
accountA
Read-only
Inspect

The account: plan and phones, money left, what is about to renew, and warnings. Check it before starting phones or long work, and tell the user every warning in plain words with the top_up link.

Inputs: no named parameters. Returns: result

actA
Destructive
Inspect

Do one thing on the phone yourself, then wait until the screen settles. Prefer element numbers from observe over coordinates; tap_text taps the element whose text contains text. Typing goes into the focused field (tap it first) and works in any language. "the screen did not change" means the action probably missed - observe again. Read without touching the screen: installed (apps), notifications (the shade), clipboard, app_info (version, installer, running), crashes (recent app crashes and ANRs), health (running, booted, network exit, last check). For a whole goal, prefer run: it does all the steps for you.

Inputs: action (required), device (required), x, y, +6 more. Returns: result

answerAInspect

Reply to a run that waits for you: answer its question with text, or allow / decline the step it asks permission for. If the question is something only the user knows, ask the user first. The run goes on at once.

Inputs: run (required), text, allow. Returns: result

appsAInspect

The user's own apps on Clousd: APKs they uploaded, kept in their private storage. Upload an APK once (op=upload), then install it by id on any of their phones (op=install), as often as needed. Clousd has no catalog of other people's apps - for apps from Google Play, open the Play Store on the phone. Every APK is checked on upload (a real Android app, 64-bit ARM code, no root or system tools) and refused with the reason otherwise. To have an app on the phone before a task, pass its id in run(files=...).

Inputs: op, app, path, devices. Returns: result

credentialsA
Read-only
Inspect

Saved logins of the account: package, name and which fields are set (username, email, password, phone, totp...). Values are never shown. Pass one to run as "package/name"; the agent types it on the phone without seeing it. The user adds logins in the dashboard (Tasks → Sign-in) - do not ask them for passwords in the chat.

Inputs: package. Returns: result

devicesA
Destructive
Inspect

Phones this key can use. op=list: name, label (the name people see in the dashboard, e.g. "Phone #3"), number, state (running / stopped / starting), Android version and network exit. Every tool takes the name, the label or the number. op=start / op=stop / op=restart with device: start a stopped phone (one to three minutes until it has booted), stop one (it keeps its apps and data) or restart it. op=reset with device: back to a fresh state - apps and data wiped, same Android version; works whether the phone runs or is stopped. Ask the user before reset. op=rename with device and label: give a phone a name (empty = back to "Phone #N"). op=delete with device: the phone moves to Trash for 14 days - stopped, not billed, apps and data kept - and op=restore brings it back (stopped). forever=true deletes it with all its data at once and cannot be undone: only when the user says so. op=trash: what is in Trash (name, label, android, deleted_at, purge_at, reason). op=restore with device: back from Trash (the name or label as shown by op=trash).

Inputs: op, label, device, forever. Returns: result

libraryAInspect

The user's Library on Clousd: every file they want on their phones lives here once (photos, videos, documents, apps) and is used by id. op=list shows it; op=upload adds a local file and returns its id; op=send copies files to phones right away (photos and videos into the gallery as if taken there, documents into Downloads, apks installed). For a task that needs a file, prefer run(files=...) - the file is placed on the phone before the first step.

Inputs: op, ids, kind, path, +1 more. Returns: result

observeA
Read-only
Inspect

Look at the phone yourself: a fresh screenshot, the app on screen and (with_text) every labelled or tappable element with a number. Act on an element by its number (act element=N); coordinates, when needed, are in this image's pixels.

Inputs: device (required), numbers, with_text.

runA
Destructive
Inspect

Give phones a task. Clousd's agent looks at the screen, taps and types until the goal is reached, and finishes with an answer. Several devices = the same task on each, all at once (one run per phone under one parent). Returns the run with its status; if it is still going, follow it with run_status. A run in mode=ask may stop with waiting_for: reply with answer. Logins: never ask the user for passwords - pass credentials; their values are typed on the phone without you or the model seeing them. A task that needs a file (post this photo, fill this form from this PDF, install this app): upload it once with the library tool and pass its id in files - do not push files by hand each time.

Inputs: task (required), devices (required), mode, files, +4 more. Returns: result

run_statusB
Read-only
Inspect

Follow a run. op=status: status (queued, running, paused = waits for an answer, completed, failed, cancelled), the answer or error, the last steps, per-device results for a run on several phones, and a replay link for the user. op=list: recent runs of this key. op=cancel: stop it. op=message: tell the running agent something (it reads it before its next step).

Inputs: op, run, text, steps, +1 more. Returns: result

schedulesA
Destructive
Inspect

Tasks that run by themselves. op=list: id, name, task, phones, at, days, tz, enabled and the runs it started last time. op=add: run task on devices at at on days, or every hour (every=hour), or only on demand (trigger=api); each firing starts runs like the run tool. op=run: start it now. op=toggle: pause or resume. op=delete: remove it.

Inputs: at, op, tz, days, +7 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create and drive cloud Android phones, reading each screen as a numbered element list and then tapping, typing, installing apps, and parking or deleting phones. It exposes 12 tools covering the phone lifecycle, app installs, device settings like locale and GPS, plus screen observation and batched actions.
      1
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.