phone-agent apps
Controls Android apps and devices over ADB, including reading device state, launching packages, analyzing or capturing the screen, and tapping, swiping, sending keys, or entering text.
Supports cellular voice conversations through an existing ElevenLabs/ElevenAgents private agent using bidirectional PCM audio and a signed WebSocket, with either agent speech recognition or standalone Scribe.
Supports OpenAI-compatible HTTP speech-to-text, chat, and text-to-speech endpoints for the online call pipeline, with configurable API roots, models, and credentials.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Phone Agent
Run a cellular call agent on a USB-connected Galaxy Z Flip5, or give another agent Android app controls through MCP. Each entry point starts independently. Both use an Android device profile created after installation.
Function | Entry point | Install extra |
Configure and inspect a device |
| Base package |
Control Android apps from another agent |
|
|
Run a cellular voice conversation |
|
|
Run speech recognition on the host | Faster-Whisper provider |
|
Install and set up a phone
Use Python 3.10 or newer on Linux with Android Platform Tools. Enable USB debugging on your phone and approve the host's ADB key. After cloning:
python3 -m venv .venv
. .venv/bin/activate
pip install '.[apps,calls]'
phone-agent device list
phone-agent device setup
phone-agent device doctorIf more than one authorized device is connected, run
phone-agent device setup --serial YOUR_ADB_SERIAL --profile my-phone.
Pass --profile my-phone to the relevant command. Profiles are stored in
${XDG_CONFIG_HOME:-$HOME/.config}/phone-agent/devices/. ADB commands stay
pinned to the selected serial and model. The setup command records a profile
and leaves the Android lock screen and USB debugging policy as configured by
the device owner.
Related MCP server: phone-use
App control
Add a stdio MCP server to the agent that will operate your phone. Use the local example if it runs on the ADB host, or the SSH example if it runs elsewhere. Replace the host alias and executable path with your own. SSH must already authenticate and recognize the host key. Connect trusted agents to this interface since it can operate the foreground app.
MCP tool | Purpose |
| Read the phone model and screen and keyguard state |
| Reserve and release app UI access for the client's multi-step task |
| Launch an installed app by its Android package |
| Read visible text, resource IDs and logical coordinates |
| Get a PNG image for screens with sparse UI data |
| Tap, swipe, send supported keys, or enter ASCII text |
For example, wake the screen with
interact_with_screen(action="key", params={"keycode":"wake"}), launch an
app, and analyze the current screen before choosing a tap. The
agent integration guide describes the tool contract. App-specific
skills live under the operator's local skills/ directory.
Cellular calls
The Android audio helper currently targets the Galaxy Z Flip5 family. The underlying audio route was exercised on a Korean Z Flip5 running Android 16. Other firmware and carrier combinations need their own checks. App control also works on compatible Android devices with ADB and a readable UI hierarchy. The call agent currently supports explicit outgoing calls.
Install JDK 17+ and Android SDK platform 36 with build-tools and d8. Set
JAVA_HOME and ANDROID_SDK_ROOT when needed. Provision the helper:
phone-agent call install-bridge --sdk "$ANDROID_SDK_ROOT"
phone-agent device doctor --callsSelect a call configuration file:
ElevenAgents uses an existing private agent with
pcm_16000audio in both directions and a signed WebSocket. Use either the agent's speech recognition or standalone Scribe.Local pipeline uses Faster-Whisper, a local OpenAI-compatible chat endpoint, and Piper. Install
.[local-speech]and provision the models and Piper executable. Use a voice that supports your chosen language.Online pipeline uses OpenAI-compatible HTTP speech and chat endpoints. Each of STT, LLM, and TTS can have its own API root, model, and credential environment variable.
Pass --config PATH for an individual command or register it with
phone-agent call setup --config PATH. Export any credential references
used by the chosen configuration.
phone-agent call setup --config /path/to/calls.json
phone-agent call check
phone-agent call dial --to +12025550123 --seconds 10Use a destination you control for the first test. call check validates the
installed bridge and provider settings without dialing. On the active call,
the helper supplies 16 kHz PCM for capture and routes playback to telephony
TX with 700 ms of initial silence. Calls default to a 10-second test limit.
If USB disconnects midcall, end the call on the phone. See the
call configuration guide for provider details and limits.
Source code is licensed under Apache-2.0. See third-party notices for phone-mcp attribution.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Give your AI agent a real cloud Android phone: push APKs, drive it, get screenshots and logs.
Phones for your agents: each agent gets its own cloud Android phone over MCP, reads the screen, taps, types and installs your APK. Ready in ~20 s, $0.01/min, parked phones free.
Melaya is a remote MCP server. It gives an assistant hands on your own Android phone and browser: it reads the screen through the accessibility tree, then taps, types and navigates inside the apps and sites you allow-list, with no per-app API. It also builds, schedules and runs agent pipelines across 6k+ connected tools. OAuth 2.1, nothing to install.
Remote MCP for Android CLI agent build gate, structured receipts, audit logs, and reviewer-ready evi
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables MCP-compatible agents to control an Android device over the network via ADB, providing tools for shell commands, screen capture, UI inspection, file operations, and input simulation.4 npmMIT
- AlicenseBqualityBmaintenanceEnables coding agents to observe and control an authorized Android phone over ADB through MCP tools and a JSON CLI. It supports UI inspection, screenshots, taps, swipes, typing, key presses, app listing, and launching.136MIT
- AlicenseNot gradedqualityCmaintenanceEnables Android device control over ADB through MCP tools that mirror CLI subcommands, including taps, swipes, text input, app launch/stop, screenshots, UI inspection, and running action sequences. Coordinates from screenshots are converted to screen coordinates automatically.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to control an Android phone by reading the screen, taking screenshots, tapping, typing, swiping, opening apps, and running multi-step tasks. It also supports on-device Android app testing and optional adb commands.1,178 npm2MIT