Skip to main content
Glama

Phonebox

by dev.phonebox
OverviewDiscussionsAdmin

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
2.2% over 21 days
Last Tested
Transport
Streamable HTTP
URL
Repository
combined-ai/phonebox-android-mcp
GitHub Stars
0
Server Listing
Phonebox Android MCP server

TDQS

A4.1/5.0

Scored across 13 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

  1. 13 tool updates
    • First observedact
    • First observedcomplete_app_upload
    • First observedcreate_app_upload
    • First observedcreate_phone
    • First observedget_phone
    • First observedinstall_app
    • First observedlist_apps
    • First observedlist_phones
    • First observedlive_view_url
    • First observedobserve
    • First observedpark_phone
    • First observedreboot_phone
    • First observedstart_phone

Related MCP Connectors

Related MCP Servers

  • orion-phone-mcp

    OrionArchitekton
    A
    license
    B
    quality
    A
    maintenance
    Enables 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.
    10
    71 PyPI
    MIT

  • Droidline

    KnifeLemon
    A
    license
    Not graded
    quality
    A
    maintenance
    Lets 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.
    312
    MIT

  • benchfleet-mcp

    benchfleet
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to safely use real Android phones by listing devices, reading screens and UI elements, tapping, typing, launching apps, and running workflows only within allowed permissions and approvals, with every step recorded in an audit log.
    531 npm
    MIT
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources