Buddy phone tools runs on your own machine — the client starts it, so there is no endpoint to ping. 349 installs a week from npm. Last commit 31 Oct 2026.
Android phone tools for AI agents (read the screen, tap, type, open apps), served by the Buddy app.
What the code does
We read the source, 17 h ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
private static final String OC_REMOVE = " for i in 1 2; do rm -rf /usr/local/lib/node_modules/@opencode/cli"
ProcessBuilder pb = new ProcessBuilder(command(c, cmd));
+ " mkdir -p ~/.ssh && { [ -f ~/.ssh/id_ed25519 ] || ssh-keygen -q -t ed25519 -N '' -f ~/.ssh/id_ed25519; }"
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Nothing serious here today
Today is the operative word: we check Buddy phone tools every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add buddy-phone-bridge -e 'BUDDY_TOKEN=<BUDDY_TOKEN>' -- npx -y buddy-phone-bridge{
"mcpServers": {
"buddy-phone-bridge": {
"command": "npx",
"args": [
"-y",
"buddy-phone-bridge"
],
"env": {
"BUDDY_TOKEN": "<BUDDY_TOKEN>"
}
}
}
}[mcp_servers.buddy-phone-bridge]
command = "npx"
args = ["-y", "buddy-phone-bridge"]
env = { BUDDY_TOKEN = "<BUDDY_TOKEN>" }{
"mcpServers": {
"buddy-phone-bridge": {
"command": "npx",
"args": [
"-y",
"buddy-phone-bridge"
],
"env": {
"BUDDY_TOKEN": "<BUDDY_TOKEN>"
}
}
}
}{
"servers": {
"buddy-phone-bridge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"buddy-phone-bridge"
],
"env": {
"BUDDY_TOKEN": "<BUDDY_TOKEN>"
}
}
}
}Put your own value in place of
<BUDDY_TOKEN> (Token from Buddy's Settings > Phone tools in your own sessions).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
BUDDY_URL (Buddy's address, if not http://127.0.0.1:8765/mcp).
Alternatives to Buddy phone tools
same job, measured the same wayCloud Android phones for AI agents: create a phone, read the screen, tap, type, install APKs, park.
Cloud Android phones for AI agents: tap, type, screenshot, install APKs, run plain-English tasks.
Let AI agents see, tap, type, scroll, screenshot and debug your Expo app on a real phone.
Open a React Native app in a simulated phone: read the screen, tap, type, set device state.
Drive cloud Android phones on US mobile IPs. Read the screen, tap, type, install apps and run tasks.
Use your real Android phone from any MCP client: read the screen, tap, type, run tasks and adb.
Let your AI agent control real iPhones: screenshots, tap, swipe, type and open apps.
Read-only Llestia tools: browse open work and agents for AI agents, and read the quick-start.
Buddy phone tools — questions
Answers built from our own checks of this server.