mcpField
B
Buddy phone tools

Buddy phone tools

Local
ghorbelhamdi.github.ioOther141Updated 1d ago
RepositoryVisit website

About Buddy phone tools

Buddy phone tools is a local MCP server inside the Buddy Android app, exposing phone actions such as reading the screen, tapping, typing, and opening apps to AI agents. Its stdio bridge supports MCP clients that can only launch servers as commands.

Key features

  1. 01Read the phone screen and take screenshots
  2. 02Tap, type, and scroll
  3. 03Open apps and a background browser
  4. 04View notifications
  5. 05Provide a stdio bridge

Use cases

  1. 01Let an agent inspect a phone screen
  2. 02Automate taps and text entry
  3. 03Open and interact with apps
  4. 04Connect Buddy from a command-only MCP client

MCP support

Buddy exposes a local MCP server on the Android phone, at `http://127.0.0.1:8765/mcp` by default. The stdio bridge forwards requests from MCP clients to Buddy.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "ghorbelhamdi-buddy-phone-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "buddy-phone-bridge"
      ],
      "env": {
        "BUDDY_TOKEN": "<BUDDY_TOKEN>",
        "BUDDY_URL": "<BUDDY_URL>"
      }
    }
  }
}
Run commandnpx -y buddy-phone-bridge
Environment variables to set
BUDDY_TOKENSecretToken from Buddy's Settings > Phone tools in your own sessions
BUDDY_URLBuddy's address, if not http://127.0.0.1:8765/mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmbuddy-phone-bridge1.1.0

Tools

28

Saved tool list · updated 1d ago

This tool takes no parameters.

Details

From the project README

Buddy phone bridge (stdio)

Buddy's phone tools (read the screen, tap, type, scroll, open apps, screenshots, notifications, the background browser…) are a local MCP server inside the Buddy app on your Android phone: http://127.0.0.1:8765/mcp. Most agents connect to it directly; Buddy's Settings → Phone tools in your own sessions gives the command for Claude Code, Codex, OpenCode, Antigravity and Grok.

This bridge is for MCP clients that can only start a server as a command. It speaks MCP over stdio and passes every request on to Buddy. It has no dependencies (Node 18+).

BUDDY_TOKEN=<token from Buddy's Settings> node bridge.mjs

MCP client config:

{
  "mcpServers": {
    "phone": {
      "command": "node",
      "args": ["/path/to/mcp-bridge/bridge.mjs"],
      "env": { "BUDDY_TOKEN": "<token from Buddy's Settings>" }
    }
  }
}
  • BUDDY_TOKEN: the token Buddy shows (with or without Bearer ).
  • BUDDY_URL: Buddy's address, if not http://127.0.0.1:8765/mcp.

Run it on the phone itself (Termux, for example): Buddy only listens on 127.0.0.1. When Buddy can't be reached, the bridge still lists the tools (from tools.json, a copy of Buddy's list) and each call says why it couldn't run; that's also what happens in the Dockerfile's container, which has no phone.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.