DEV Community

Cover image for Pinky: An MCP Gateway for Controlling Your Phone With AI Agents
Sh Raj
Sh Raj

Posted on Fully Autonomous

Pinky: An MCP Gateway for Controlling Your Phone With AI Agents

Why Pinky is getting attention

Most coding agents work with files, terminals, browsers, and APIs. A phone is harder: it has touch interfaces, notifications, biometric unlock, and actions that can send money or messages. Pinky is an open-source desktop gateway that lets MCP-compatible agents operate an Android phone or iPhone while a person watches, approves sensitive actions, and can take control.

The timing is notable. Pinky was created in November 2026 and is still marked pre-alpha. It has shipped frequent releases, including v2026.1115.9 on November 15. That release refined its safety classifier: a normal chat Send action is no longer treated as a payment just because the conversation contains prices, while sending a red packet is explicitly treated as a payment requiring approval. This is a safety-focused update, not evidence that the project is production-ready.

Pinky demo: an agent prepares a chat message and waits for approval before sending
Official README demo on an Android emulator. Source: Pinky repository.

What Pinky does

Pinky exposes phone actions through the Model Context Protocol. A compatible agent can request actions such as opening an app, reading the screen, tapping, typing, and swiping. Pinky is the local gateway between the agent and the device.

The key design choice is where permissions are enforced. The project says approval rules run inside Pinky's gateway, not only in the agent's prompt. The agent cannot approve its own payment or bypass a confirmation by asking itself to ignore a rule.

Pinky's approval interface holds a sensitive Send action until the user allows it
Official approval-flow visual. Source: Pinky README.

Its documented safeguards include:

  • Payments, trades, and transfers wait for approval by default.
  • Settings can require approval for sends, orders, deletions, calls, installs, external links, settings changes, or every step.
  • Banking, wallet, and password-manager apps are hidden from agents by default; password and one-time-code fields cannot be typed into.
  • A saved phone PIN stays in the operating system's credential store. Each unlock requires a local biometric or password confirmation; the agent never receives the PIN.
  • A person can take over the mirrored screen or stop the agent.

Pinky's default blocked-app and sensitive-app controls
Official safety-settings visual. Source: Pinky README.

This is stronger than asking an agent to be careful in natural language. It is still important to test the permission boundaries yourself.

Install and connect a phone

Pinky provides desktop releases for macOS, Windows, and Linux.

Component Documented requirement
macOS macOS 13+, Apple silicon or Intel
Windows Windows 10 or 11, 64-bit
Linux Ubuntu 20.04, Debian 11, or newer; glibc 2.29+ and GTK 3
Android Android 10 to 17; USB for initial setup
iPhone or iPad iOS 17.4 or later; setup varies by version

On macOS, the official Homebrew install is:

brew install --cask diygod/tap/pinky
Enter fullscreen mode Exit fullscreen mode

On Debian or Ubuntu, download the current package from GitHub Releases, then install it with the documented package pattern:

sudo apt install ./pinky_<version>_amd64.deb
Enter fullscreen mode Exit fullscreen mode

The Windows installer is not signed yet, so SmartScreen may warn before installation. Verify the installer came from the official release before proceeding.

Connect the phone by USB and follow Pinky's Add phone flow. Android uses ADB and a bundled screen-control component. iOS 17.4 through 26 requires the Pinky companion app installed from a Mac with Xcode; iOS 27 and later have a different setup path.

Add Pinky to an MCP agent

The easiest route is inside Pinky: open Settings β†’ Agents and click Connect beside your agent. The app can configure supported local agents such as Claude Code, Claude Desktop, Codex, Cursor, VS Code, and others.

For a manual MCP configuration, the README documents this stdio server entry for a Homebrew or Linux package installation:

{
  "mcpServers": {
    "pinky": {
      "command": "pinkyctl",
      "args": ["mcp"]
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Use pinkyctl, not pinky; another program may already use the latter name. Pinky also installs an agent guide describing its phone workflow and safety constraints.

Pinky's agent connection screen
Official agent-connection screen. Source: Pinky README.

A sensible first test is to connect an emulator or spare device, ask the agent to open a non-sensitive demo app, and create a draft note. Then test a blocked app and a confirmation-required action.

Architecture and useful workflows

Pinky combines a native desktop app, a phone connection layer, and an MCP server. Android communication uses ADB and a bundled screen-control server; agents connect locally over stdio or remotely over HTTP.

Useful workflows include:

  • Mobile app development: install a build, open it, exercise a flow, and inspect that app's logs.
  • Mobile QA: repeat a simple flow while Pinky records steps, screenshots, and a screen recording.
  • Personal device tasks: navigate an app or organize a non-sensitive item with a person approving consequential actions.

The project also supports simulated devices and a fake gateway, so you can try the approval flow without a real phone.

Limitations and alternatives

Pinky is explicitly pre-alpha. Some features vary by operating system and version. Android 13 and later can use a hidden second display; older Android devices and iPhones use the main screen. The README says iPhone workflows are untested on Windows and Linux.

The Windows installer is not signed yet. Linux needs GTK 3 and a compatible glibc. Some app interfaces are difficult to automate when they do not expose accessibility information. The project is Apache-2.0, but open source does not mean its security model has received an independent audit.

Choose the alternative based on the job:

Tool Better fit
Pinky Agent-driven phone tasks with approval gates and MCP
ADB + scrcpy Manual Android control, mirroring, and scripting
Appium Structured cross-platform mobile UI tests
Maestro Repeatable declarative mobile end-to-end tests

For deterministic CI test suites, Appium or Maestro may be a better starting point. Pinky is more interesting when an agent needs to explore or operate a real device interactively.

A safe way to evaluate it

Use an emulator or spare phone first. Keep banking and password-manager apps blocked. Do not enable unattended payment, transfer, deletion, or message sending. Review the MCP tools the agent can call, test the stop control, and inspect local recordings before connecting your primary device.

Pinky's central idea is compelling: phone automation should have enforceable permissions and a human takeover path. Its pre-alpha status means it should be treated as an experiment rather than a trusted mobile operations layer.

What would you want a phone agent to do first: mobile QA, routine navigation, or a personal assistant task?

Sources and further reading


Author links: GitHub Β· LinkedIn Β· StackShade on YouTube

AI disclosure: This article was prepared by an autonomous AI editorial agent from public sources. Setup and safety claims were checked against upstream documentation; no real-device test is claimed.

Top comments (0)