clousd-mcp
An MCP server that gives any MCP-capable agent a real Android phone in the cloud: a device modelled on a real phone, with Google Play, a network in the country you choose, and saved states to reset to between runs.
Early access: ask for a key at clousd.com/agents.
Install
pip install clousd-mcp
Any MCP client (Cursor, Windsurf, Zed, a desktop assistant or your own agent) - stdio server, one environment variable:
{
"mcpServers": {
"clousd": {
"command": "clousd-mcp",
"env": { "CLOUSD_API_KEY": "cl_live_..." }
}
}
}
Clients that take a command line instead of JSON: clousd-mcp with CLOUSD_API_KEY in the environment.
Remote server (no install)
The same server runs at https://api.clousd.com/mcp (streamable HTTP). Point any MCP client at it with your key in
the Authorization header; clients that cannot set headers can pass ?api_key=cl_live_... in the URL.
{
"mcpServers": {
"clousd": {
"url": "https://api.clousd.com/mcp",
"headers": { "Authorization": "Bearer cl_live_..." }
}
}
}
Self-hosting the remote mode: CLOUSD_MCP_HTTP=127.0.0.1:8790 clousd-mcp serves /mcp over HTTP; every request must
carry a key, nothing is read from the environment.
Tools
Six tools - a few large tools are easier for a model to choose from than dozens of small ones:
| Tool | What it does |
|---|---|
devices |
list the phones this key can use; start or stop one |
observe |
the screen as an image with a number drawn on every element, plus the elements as text |
act |
tap / long_press (element number or point), swipe, scroll, tap_text, wait_text, type, key, open_app, close_app, open_url, intent, settings, clipboard_set, notifications_open / _close / _clear, installed |
inspect |
read without touching the screen: notifications, clipboard, app (version, running), crashes, health, installed |
snapshots |
list, save, restore (reset between runs) or clone a phone |
recipe |
run an app recipe (built-in or your own steps); record a new one from what is done on the phone |
Every tool has parameter descriptions, a result schema and hints (read-only, destructive). Screenshots come back 540 px
wide (CLOUSD_SHOT_WIDTH to change); act on an element by its number from the last observe - the most reliable way to
press a button - or give coordinates in that image, which the server scales to the phone. Typing works in any language.
Built on the clousd Python client. MIT license.
mcp-name: io.github.Clousd-Android/clousd-mcp
Metadata
Release files for clousd-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| clousd_mcp-0.2.0.tar.gz | 10.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| clousd_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.6 kB
Release files / clousd_mcp-0.2.0.tar.gz
| Download URL | clousd_mcp-0.2.0.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33188e4f3ac8fb164ef0d59e26728a5c9d03f8aa7ab61df9176f03cee9f375a4
|
|
BLAKE2b-256 checksum How to use checksums |
f44fe91feca27ea4d91afd54f2ae63ef00a31722767949ba8a160a344ab10a79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logRelease files / clousd_mcp-0.2.0-py3-none-any.whl
| Download URL | clousd_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 10.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
36d7f523947ae0111b15715db2c4e836b669630151fbc5b0b88f6e7388fa1d14
|
|
BLAKE2b-256 checksum How to use checksums |
2ca9978caaf26d072a926f94c4dcb546e1441ff9f27913a0818bcda6e56697e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency log