Phonebox
Server Details
Cloud Android phones for AI agents: create a phone, read the screen, tap, type, install APKs, park.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- combined-ai/phonebox-android-mcp
- GitHub Stars
- 0
- Server Listing
- Phonebox Android MCP server
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 13 tools
The phone lifecycle tools (create/get/start/park/reboot/list) are clearly distinct, and observe (read screen) vs act (perform actions) is a clean split emphasized in descriptions. The only mildly overlapping cluster is the app-upload flow (create_app_upload, complete_app_upload, install_app), where the boundary depends on reading multi-step prose rather than a crisp purpose split.
Almost all names follow a consistent snake_case verb_noun pattern (create_phone, get_phone, list_phones, park_phone, reboot_phone, start_phone, install_app, list_apps). Minor deviations are the bare verbs act/observe and the noun-phrase live_view_url, but these are still readable and unambiguous.
Thirteen tools is well within the ideal range and each maps to a genuine capability of cloud-phone management. No redundant or filler tools appear; the surface is tightly scoped to the domain.
The surface covers the full phone lifecycle (create, read, list, start, park, reboot), app install/list, upload, on-device actions, and human viewing. Gaps exist: no delete/destroy-phone operation and no uninstall-app, which leaves some dead ends for cleanup workflows.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Cloud Android phones for AI agents: give phones a task in plain words and get the answer
Give your AI agent a real cloud Android phone: push APKs, drive it, get screenshots and logs.
Disposable cloud Android emulators for coding agents: run an APK or PR build, tap, type, screenshot.
AI agents on real phones: run tasks, read the screen, tap, type and install apps.
Related MCP Servers
- AlicenseAqualityBmaintenanceA cloud Android phone for AI agents: push an APK and drive a real device — tap, type, screenshots, UI hierarchy, logs — while the human watches the same phone through a preview link.27MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.1MIT
- AlicenseBqualityBmaintenanceEnables an AI agent to lease its own Android emulator phone and drive it over stdio: reading the screen, tapping, typing, and opening apps, with every action leaving an audit line and screenshot. Leases keep one agent per phone, and a locked phone stays inert until an operator unlocks it on its own screen.10MIT
- AlicenseNot gradedqualityAmaintenanceLets AI agents see and use a real Android phone over Wi-Fi: read the screen, find elements by text or ID, tap, type, swipe, take screenshots and read notifications, without ADB or root.519MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.