Clousd MCP vs Phonebox
A side-by-side look at the Clousd MCP and Phonebox MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Clousd MCP for os automation work as a local process; choose Phonebox for os automation over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Clousd MCP when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CLOUSD_API_KEY.
Choose Phonebox when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
PHONEBOX_API_KEY. - You want tools like
create_phone, observe, act.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 40/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CLOUSD_API_KEY | PHONEBOX_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 8 |
| Full listing | View Clousd MCP | View Phonebox |
Tools & capabilities
Clousd MCP tools
No tool names declared yet. Check the project README from the listing page.
Phonebox tools 8
create_phoneCreates a cloud Android phone and waits until it's readyobserveReads the screen as a numbered text list, plus a 720px screenshotactRuns up to 20 actions in order: tap, type, swipe, scroll, open an app, wait for an elementinstall_appInstalls from the app library or from your own uploaded APKcreate_app_uploadUploads your APK with one `curl` commandlive_view_urlA link for a person to watch and control the phonestart_phoneResumes a parked phone, or parks it to stop billinglist_phonesFind phones, wait for them, list apps, restart a stuck phone
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Clousd MCP
{
"mcpServers": {
"clousd-mcp": {
"command": "uvx",
"args": [
"clousd-mcp"
],
"env": {
"CLOUSD_API_KEY": "YOUR_CLOUSD_API_KEY_HERE"
}
}
}
}
Phonebox
{
"mcpServers": {
"phonebox": {
"url": "https://phonebox.dev/mcp"
}
}
}
Frequently asked questions
Clousd MCP is categorized under OS Automation and uses a local stdio subprocess. Phonebox belongs to OS Automation and uses a remote HTTP/SSE transport. Pick Clousd MCP for os automation work and Phonebox for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Clousd MCP has no declared pricing — check the project's own site. Phonebox has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add clousd-mcp and phonebox as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Clousd MCP has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Phonebox has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.