Buddy phone tools

io.github.ghorbelhamdiPublished by GitHub account ghorbelhamdiv1.2.0Updated Nov 3, 2026

Android phone tools for AI agents (read the screen, tap, type, open apps), served by the Buddy app.

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

Buddy phone tools's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Buddy phone tools in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Buddy phone bridge (stdio)

This needs the free Buddy app on your Android phone: download the APK or see Buddy on GitHub. Buddy lets AI agents read your screen, tap and type, and asks before anything risky. No root, no adb, no PC.

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+).

bash
BUDDY_TOKEN=<token from Buddy's Settings> npx -y buddy-phone-bridge

Or from a copy of this folder: BUDDY_TOKEN=<token> node bridge.mjs.

MCP client config:

json
{  "mcpServers": {    "phone": {      "command": "npx",      "args": ["-y", "buddy-phone-bridge"],      "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.

Buddy is an independent project, not made by or affiliated with Anthropic, OpenAI, Google or xAI.

Source: mcp-bridge/README.md at commit 9828b86

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.2.0LatestNov 3, 2026
  2. v1.1.0Oct 29, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts