Pinky: an MCP gateway for agents to control a real phone
Pinky connects MCP agents to a real Android phone or iPhone through a local desktop gateway that can pause risky actions for approval and record each task.
Project facts
GitHub Ecosystem- License
- Apache-2.0
- Language
- Go
- Stars
- 1,844
- Data checked
- 2026-11-12
Snapshot figures reflect the check date and may change over time.
Letting a coding agent tap a real phone makes the permission boundary part of the setup. Pinky is a desktop app that connects an MCP agent to an Android device or iPhone through a local gateway; that gateway handles approvals, safety rules, and task records. The project is marked pre-alpha. GitHub showed 1,844 stars on November 12, 2026, and the README says Claude Code has completed end-to-end workflows on real phones.
Core features
- Approvals at the gateway: MCP calls reach Pinky before the phone driver. The README says payments, trades, and transfers wait for the user by default. Settings can also require approval for sends, orders, deletions, calls, installs, external links, and settings changes, or for every step. A request with no answer is denied after 60 seconds, and Pinky checks that the target button is still in place before acting.
- Sensitive apps and codes: Banking, wallet, and password-manager apps are hidden from agents by default. Agents cannot type into password fields, and one-time codes are masked before they are passed to the model. If the user allows a finance app for a task, the README says Pinky keeps no screenshots or recordings of it. The README does not describe CAPTCHA detection or handling.
- Phones and virtual devices: Pinky lists Android 10–17 and iPhone or iPad on iOS 17.4 or later, along with Android emulators and iOS Simulators. Android 13 and later can run work on a hidden second screen. Older Android devices and iPhones use the phone’s main screen, so the user may see the agent’s actions there.
- Local and remote MCP: Local clients connect over stdio. HTTP access is off by default and requires a bearer token when enabled. The MCP guide lists 19 tools for observing screens, tapping, typing, swiping, launching apps, and handing control back. Remote access exposes the same device-control surface, so users need to choose its network scope deliberately.
- Records and telemetry: Screenshots, recordings, and task history stay on the computer for 30 days by default. Exporting a recording to an agent asks for approval each time. Usage statistics and crash reports are enabled by default; users can turn them off in Privacy settings or with
DO_NOT_TRACK=1. The project says those reports exclude screens, typed text, and app names.
Typical use cases
- Mobile developers can ask an agent to open a test app, repeat a task, and save steps or screenshots for a bug report. The gateway still applies its app, credential, and action rules.
- Someone who wants a desktop agent to operate their own phone can rehearse on an emulator, then pair a device over USB or Wi-Fi. iOS 17.4–26 also needs a helper app, so setup takes more work than the Android path.
- Codex or Claude Code users can delegate forms, messages, or settings tasks while approving consequential actions in Pinky. This is a supervised workflow; it does not transfer payment or account responsibility to the model.
- Developers comparing phone-control approaches can also read iPhone-use. That project focuses on Codex and iPhone from macOS; Pinky covers Android and iOS and puts approval policy in a separate gateway.
Quick start
On macOS, the README gives this Homebrew Cask command:
brew install --cask diygod/tap/pinky
Windows and Linux users can choose a package from GitHub Releases. Open Pinky, choose Add phone, and follow the USB or Wi-Fi pairing steps shown for that device. Then connect an MCP client in Settings › Agents. The README includes setup instructions for Claude Code, Codex, Cursor, and other clients, while also marking the project pre-alpha and identifying Claude Code as the agent with completed real-phone end-to-end workflows. MCP compatibility alone does not establish the same device testing for every client.
Before using a physical phone, check Pinky’s Checkup for adb, device authorization, Pinky Companion, and tapping support. The helper for iOS 17.4–26 requires a Mac with Xcode; the README says a free Apple ID installation may need to be signed again every seven days. Enable remote HTTP only if another machine needs access, and keep its bearer token protected.
Summary
Pinky’s strongest idea is that approval happens in a gateway between the model and the device, instead of relying on a prompt that tells the agent to be careful. That boundary has a clear condition: the README warns that an agent able to run shell commands on the same computer can call adb directly and bypass Pinky. Anyone depending on Pinky’s rules should avoid giving the agent another route to the phone. Default-on telemetry is also part of the setup, though the project documents opt-out controls.
Pinky remains pre-alpha, and support across desktop systems does not mean every phone, OS release, and MCP client has the same real-device coverage. It is written in Go and uses Apache-2.0. At 1,844 GitHub stars on November 12, 2026, it is a project to evaluate with the actual phone and agent you plan to use. It fits developers willing to check device capabilities and keep a person involved in consequential actions; teams that need unattended or thoroughly validated iOS automation should verify that path first. This entry relies on the README and docs; the tool was not installed or run here.