Hosted MCP server/Development

Phonebox (Android for AI agents) MCP server

Hosted at phonebox.dev·Streamable HTTP

Phonebox gives an agent a cloud Android phone through a hosted MCP server at https://phonebox.dev/mcp. Tools create a phone, read the screen as numbered text with a screenshot, run up to 20 tap and type actions, install an APK, and park the device. Nothing runs locally and no ADB or emulator is needed. The provider's documented setup is the Phonebox CLI, which signs the user in and writes the client config; clients that send a header can use a token from phonebox token as Authorization: Bearer.

phonebox.dev Streamable HTTP Phonebox CLI token (Bearer) Server not checked yet Reviewed 2026-11-16
About

Where it fits

Mobile QA and agent developers who need to exercise an Android app from a sandbox or CI without an emulator.

  • Create a cloud Android phone and read its screen.
  • Install an APK and tap or type through an app flow.
  • Park the device when the agent is idle.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Set up Phonebox

The documented path is the Phonebox CLI: it signs you in, provisions the cloud phone and writes the client config. A Phonebox token can also be sent as Authorization: Bearer $(phonebox token).

  1. Run the setup prompt

    Give the agent the provider's setup page and let it install and sign in.

    Read https://phonebox.dev/setup.md and set me up with Phonebox
  2. Add the hosted endpoint

    The server is https://phonebox.dev/mcp over Streamable HTTP; clients that use a header can send a token from the Phonebox CLI.

    claude mcp add --transport http phonebox https://phonebox.dev/mcp --header "Authorization: Bearer $(phonebox token)"

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://phonebox.dev/mcp
Host
phonebox.dev · /mcp
Transport
Streamable HTTP
Authentication
Phonebox CLI token (Bearer)
Server name
phonebox-android-for-ai-agents
Listing type
Community or directory listing

The installer uses the server name phonebox-android-for-ai-agents. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that phonebox-android-for-ai-agents appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Create a cloud Android phone and read its screen. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Phonebox (Android for AI agents) documentationhttps://phonebox.dev/guides/android-mcp-serverGitHub repositoryhttps://github.com/combined-ai/phonebox-android-mcp