claudeers.
// MCP Servers

pinky

Let AI use your iPhone or Android phone, with you in the loop: any MCP agent from macOS, Windows or Linux, or Pinky itself, right on the phone.

// MCP Servers[ cli ][ api ][ desktop ][ web ][ mobile ][ claude ]#claude#ai-agent#android#claude-code#ios#iphone#mcp#mcp-server#mcp-servers◷ Apache-2.0$open-sourceupdated 4 days ago

Install with your AI

Paste into Claude Code, Cursor, or any agent — it reads the repo and wires the tool into your project.

Install and set up pinky (release-binary project) into my current project.
Found on https://claudeers.com/pinky
Repo: https://github.com/DIYgod/pinky
Homepage/docs: —
Detected install method: release-binary → inspect the README
Category: mcp-servers. Platforms: cli, api, desktop, web, mobile.
Read the repo's README for exact setup and env vars, then install it and wire it into my project.

Claudeers Health Verdict:
unknown; community-verified: false. Confirm the source before running anything.
// or install directly (release-binary)

Grab the latest release asset from GitHub.

# download a build from https://github.com/DIYgod/pinky/releases
// or clone
git clone https://github.com/DIYgod/pinky

// compatibility

Platformscli, api, desktop, web, mobile
Operating systems—
AI compatibilityclaude
LicenseApache-2.0
Pricingopen-source
LanguageGo

Get your FREE $2.50 API credits to access TickAtlas financial data ↗

pinky

Pinky

Let AI use your iPhone or Android phone, with you in the loop: any agent from macOS, Windows or Linux, or Pinky itself, right on the phone.

Download · Get started · FAQ · Discord

English · 简体中文 · 日本語

Claude Code types a reply in Messages; Pinky holds the Send tap until it is allowed, then the text goes out
A real Claude Code run on an Android 16 emulator. Pinky asks before payments by default; this run also asks before messages.

Pinky lets any agent (Claude Code, Claude Desktop, Codex, Cursor or a script) operate a real iPhone or Android phone over MCP, while you watch on your computer, approve risky steps, take over and review what happened. Pinky can also do tasks by itself, with an AI model you choose: from your computer, or in Pinky's app right on the phone, with no computer at all. Whoever does the task, approvals are enforced by Pinky's gateway, not by instructions to the agent.

  • Every platform. One app for macOS (Apple silicon and Intel), Windows and Linux. It drives Android phones (Android 10 to 17) and iPhones on iOS 17.4 or later: nothing to install on iOS 27 and later, and Pinky on the iPhone, Pinky's app, installed once from a Mac with Xcode on iOS 17.4 to 26, which you can also choose on iOS 27 (tried there, on a phone below it and on Simulators; details).
  • Tiny and native. The window is drawn by MyGo on the GPU, with no Electron and no webview: a 16–22 MB download that idles at about 70 MB of memory and 0% CPU on a Mac.
  • Any agent, one click. Settings › Agents connects Claude Code, Claude Desktop, Codex, Cursor and more, and any agent that can use MCP servers works, on the same computer or over HTTP.
  • Pinky on the phone, no computer needed. Pinky's app on Android and iPhone does tasks by itself with a model you choose, from DeepSeek, Qwen, Kimi and GLM to Claude, GPT, Gemini and local models in Ollama or LM Studio. Type or speak a task, or share something to it; on Android, ask about what the screen shows from a floating button, and let it work on a hidden background screen while you keep using the phone (how).
  • Scheduled tasks and memory. Pinky can run a task at set times or tell you when a condition holds, on the computer and on Android. After a task it may suggest a note to remember, such as a preference you told it, and keeps it only if you say yes (more).
  • Locked phone? Unlock it from your computer. Save the phone's PIN in Pinky once, then confirm each unlock with Touch ID, Windows Hello or your keyring's password. Agents never see the PIN.
  • Free and open source under the Apache-2.0 license, with no account to create.
You decide what waits: Pinky's window holds an agent's Send tap until you click Allow
You approve the risky steps. Payments, trades and transfers wait for your click; in Settings › Safety you can have sends, orders, deletions, calls, installs, links that leave the app and settings changes wait too, or every step. Pinky spots these buttons in 10 languages. The rules run in Pinky's gateway, so an agent can't approve itself, even when text on the screen tries to talk it into it.
Off-limits by default: Settings › Safety with when agents ask you, and the blocked apps
Off-limits by default. Banking, wallet and password-manager apps are invisible to agents, and agents can't type into password or one-time-code fields. When an agent needs a banking or wallet app for a task, it asks, and you can allow that app for that task only. Every new agent needs your approval and gets only the scope you give it.
A hidden second screen for the agent: the agent's screen beside the phone's own home screen
Your phone stays yours. On Android 13 and later, agents work on a hidden second screen, so the phone's own screen stays yours, or off and locked. On older Android phones and on iPhones they use the main screen.
Take over any time: Claude Code is paused while you are in control, until you hand back
Take over any time. Click the mirror and the agent pauses until you hand back; on Android, touching the phone yourself pauses it too. Stop all is ⌥⌘. (Ctrl+Alt+. on Windows and Linux) from anywhere.
Every run, on the record: a finished task's steps beside its screen recording
Every run is on the record. Each step in plain words, screenshots and a screen recording with a mark per step, exportable as an HTML report. It all stays on your computer.
On iPhone too: Pinky holds a Delete tap in Photos until you click Allow
iPhones too. The same gateway, approvals and records work on iOS 17.4 and later (what works). Shown here on the iOS Simulator, with deletions set to ask.

Status: pre-alpha. Claude Code has used real phones through it end to end (an Android phone over USB, an iPhone on iOS 27, and an iPhone XS Max on iOS 18.7.11 through Pinky Helper, the app Pinky on the iPhone replaces), and agents can connect over stdio or HTTP. Pinky on the phone has done tasks with a real model on a Mi 10 Pro (Android 17) and an iPhone 13 mini (iOS 27.0.1). Unlocking from the computer, background work on Android, recordings, export, Wi-Fi pairing and the phone's files are built; some of it still waits for a person to try it. See docs/ACCEPTANCE.md for what works today and how to try it.

Get started

Install Pinky, connect your phone and add Pinky to your agent. Then ask the agent to do something on the phone, and watch it work in Pinky's window.

What you need

You need
MacmacOS 13 or later, with Apple silicon or Intel
WindowsWindows 10 or 11, 64-bit (x64)
LinuxA 64-bit PC (x86-64) with Ubuntu 20.04, Debian 11 or a newer system (glibc 2.29 or later), and GTK 3
Android phoneAndroid 10 to 17 and a USB cable. Pinky brings its own adb; on Windows some phones need a USB driver, and on Linux USB access (below)
iPhone or iPadiOS 17.4 or later, and a USB cable to set it up; afterwards it works over Wi-Fi too (below). Pinky prepares it itself, with Apple's developer disk image, which comes with Xcode or which Pinky can download from a third-party mirror when you ask (below). On iOS 17.4 to 26 also Pinky on the iPhone, Pinky's app (below)
Simulators and emulatorsOptional, in place of a phone or next to one: an iOS Simulator on a Mac with Xcode, or an Android emulator from Android Studio. You create them there; Pinky starts them (below)
AgentAny agent that can use MCP servers, such as Claude Code, Claude Desktop, Codex or Cursor

1. Download and install Pinky

Get Pinky from the latest release:

  • Mac: download pinky-<version>-arm64.dmg for a Mac with Apple silicon (M1 or later) or pinky-<version>-amd64.dmg for an Intel Mac. Open it and drag Pinky to Applications. With Homebrew, brew install --cask diygod/tap/pinky does the same.
  • Windows: download pinky-setup-<version>-amd64.exe and run it. It installs Pinky for your account, without administrator rights. The installer is not signed yet, so SmartScreen may say that Windows protected your PC: choose More info, then Run anyway. To use Pinky without installing it, unzip pinky-<version>-windows-amd64.zip and open Pinky.exe.
  • Linux: on Debian and Ubuntu, download pinky_<version>_amd64.deb and install it with sudo apt install ./pinky_<version>_amd64.deb. On other systems, unpack pinky-<version>-linux-amd64.tar.gz into a folder of its own and run pinky in it.

Pinky looks for new versions by itself and, on a Mac, with the Windows installer and unpacked from the Linux .tar.gz, installs them too (Updates).

2. Connect your phone

Open Pinky and choose Add phone. A phone that is ready shows up in Pinky's window; when something is missing, the phone's page in Pinky says what.

Android

Add phone › Android shows these steps for your phone's brand, with its own menu names and extra switches: Xiaomi, OPPO, vivo, HONOR, HUAWEI, Samsung and Pixel, and general steps for the rest.

  1. On the phone, turn on USB debugging: in Settings › About phone, tap Build number 7 times, then turn on USB debugging in Settings › System › Developer options. Some brands name these menus a little differently.
  2. Plug the phone into the computer. When the phone asks whether to allow USB debugging, tap Allow. On Android 11 and later you can pair it over Wi-Fi instead, from Add phone (when it fails). Android 10 has no Wireless debugging: once it is plugged in, Use Wi-Fi instead… moves it to Wi-Fi (below).
  3. Pinky offers to install its app for the phone, Pinky on the phone (it shows there as Pinky), which makes reading the screen many times faster and lets Pinky type in any language. The phone may ask you to allow the install once.

Each phone has a Checkup, in the ··· menu under its mirror, that lists what works and how to fix what doesn't, such as a Xiaomi's USB debugging (Security settings) switch.

Over Wi-Fi, Pinky makes sure the phone that answers is yours: it leaves a mark on each phone it sets up, which only the phone's debugging connection can read, and checks it whenever adb connects the phone, so another device on the network can't answer in its place. A phone connected over Wireless debugging that Pinky hasn't used, by another tool for example, shows as found on Wi-Fi, and Pinky leaves it alone until you choose Use. If a phone's page says This may not be … after you reset the phone or set it up again yourself, choose Trust this phone… there, or plug it in once.

Taking the phone out? With Tailscale, Pinky reaches it away from home too (how).

Add phone › Android with a Xiaomi picked: where to turn on Developer options, and the three USB debugging switches
Add phone › Android, with a Xiaomi picked.
A Redmi's checkup: adb, the connection and debugging pass; Pinky on the phone and tapping need fixing, with the steps
A Redmi's Checkup, with two things to fix.

Android tools

Pinky brings its own adb, the tool it reaches Android phones with, built from Android's source, so nothing else needs installing. When the computer has Android's platform tools already, from Android Studio, Homebrew or the system's packages, Pinky uses those, and shares their adb server with Android Studio and other tools. When Pinky quits, it stops the adb it brought, unless another app such as Android Studio is using it; Settings › Advanced › Stop adb when Pinky quits turns that off. An adb you installed keeps running.

USB on Windows and Linux

  • Windows: the phone's USB debugging needs a driver. Windows installs one by itself for many phones; when it has none, Pinky lists the phone as needing setup and says which driver to install: the Google USB Driver for Pixels, Samsung's for Samsung phones, the phone maker's for others. Unplug the phone and plug it in again afterwards.
  • Linux: the computer must let Pinky open the phone's USB device, which takes udev rules for Android phones: sudo apt install android-sdk-platform-tools-common on Debian and Ubuntu, android-udev on Arch, android-tools on Fedora. You may also need to be in the plugdev group. Then plug the phone in again. Pinky says so when they are missing.

When pairing over Wi-Fi fails

When a phone works on the cable but Pair over Wi-Fi does not finish, the pairing page says within half a minute what Pinky sees:

  • The phone hasn't shown up on the network yet: check that Wireless debugging is on and that the phone is on the same Wi-Fi as the computer. Guest Wi-Fi, routers with AP (client) isolation and many office networks keep devices from finding each other. There, choose Pair with a code instead: on the phone, tap Pair device with pairing code and enter the IP address and port and the six-digit code it shows, which change each time that dialog opens. Pinky then needs no search to pair; if it still cannot find the phone afterwards, it asks for the IP address and port at the top of Wireless debugging (not the pairing dialog's) and connects there. If it cannot reach the phone at those addresses either, the network keeps its devices apart: use a Wi-Fi where they can reach each other, such as your home network rather than its guest network, or the cable.
  • Pinky isn't allowed to look for phones on this network: on a Mac, Pinky needs Local Network access, and macOS gives no error without it: the search just finds nothing. Choose Open Local Network settings, turn on Pinky under System Settings › Privacy & Security › Local Network and try again (if macOS asks whether Pinky may find devices on your local network, click Allow). On a Mac, a phone's Checkup shows this too, under Local network. On Windows and Linux, a firewall can block the search the same way: let Pinky use the local network, or pair with a code.
  • Pinky can't look for phones on this network: check that the computer is connected to Wi-Fi or Ethernet.
  • The phone showed up, but pairing hasn't finished: if the phone shows an error or went back to Wireless debugging, scan the code again, or pair with a code.

When pairing stops with an error, the page says what adb reported:

  • The phone ended the pairing before it finished (QR code): the phone left its scanning screen, changed Wi-Fi, or something between it and the computer cut the connection; adb cannot tell which. Keep the phone on the scanning screen and try again, or choose Pair with a code instead next to the message.
  • The phone didn't accept the pairing (pairing code): a wrong code, or a port that is not the pairing dialog's. The address at the top of Wireless debugging is for connecting, not pairing, and adb answers the same way for both mistakes.
  • Nothing at that address is waiting to pair or The phone stopped waiting to pair: the pairing dialog or the scanning screen closed, or the port is wrong. Open it again and use what it shows now.
  • Couldn't reach the phone at that address or Pinky couldn't connect to it: the network keeps the computer and the phone apart, as above; a VPN or firewall on the computer can too.
  • The adb server running on this computer is too old: another program started an adb older than platform-tools 30. Quit it, or update it, and Pinky starts its own.

Pinky writes adb's own words to its log, which Help › Send Feedback… attaches with the diagnostics.

Pairing over Wi-Fi needs Android 11 or later; an Android 10 phone moves to Wi-Fi from the cable instead (Use Wi-Fi instead…, below). Up to Android 16, Wireless debugging turns itself off when the phone leaves the Wi-Fi network, even for another access point of it, or restarts: turn it on again, or pair again from Add phone.

iPhone

Pinky prepares an iPhone itself; Add phone › iPhone walks you through it.

  1. Plug the iPhone into the computer, unlock it, tap Trust and enter its passcode. On Windows, install Apple Devices from the Microsoft Store (or iTunes) first; on Linux, the usbmuxd package. Add phone says when they are missing.
  2. On the iPhone, turn on Developer Mode in Settings › Privacy & Security: Pinky makes the switch appear there. The iPhone restarts; unlock it, tap Turn On and enter the passcode.
  3. Pinky mounts Apple's developer disk image on the iPhone and lists it as ready. An iPhone on iOS 27 keeps the image when it restarts; below iOS 27 Pinky mounts it again after each restart, once you unlock the iPhone.

The developer disk image comes with Xcode, Apple's free app for developers, and Pinky does not ship it. On a Mac, install Xcode once and open it: Pinky uses the image it installs, and Xcode never has to run again. An iPhone on iOS 27 or later needs the image of Xcode 27 or later: Apple's signing server no longer signs older ones, and Add phone then says which image Pinky used and how to get a newer one. On Windows and Linux, copy /Library/Developer/DeveloperDiskImages/iOS_DDI from such a Mac into Pinky's folder (where). Without either, or when Apple refuses the image Pinky found (Xcode's, or one copied into Pinky's folder), Add phone offers to download the image from a third-party mirror, github.com/doronz88/DeveloperDiskImage (Xcode 27.0 beta 4, 32 MB, kept by the author of pymobiledevice3, not by Apple), only when you click Download; Pinky checks every file against the checksum it expects, and from then on uses it instead of an image Apple refused. On iOS 27 and later, no app gets installed on the iPhone.

Checked on the iPhone 13 mini (iOS 27.0.1): Pinky mounting Xcode's image itself (in about 1.5 s, after the image had been taken off), keeping the image already on the phone, and that the iPhone keeps the image when it restarts. Not yet tried on a phone: the downloaded image, the Developer Mode switch, iPhones below iOS 27, and pairing an iPhone on Windows. Contributors have used an iPhone and an iPad on iOS 27.2 on Linux (Arch Linux), and an iPhone on iOS 27.2 on Windows 11, on the cable and over Wi-Fi, with the image already on them.

iPhones and iPads over Wi-Fi

Pinky also uses an iPhone or iPad over Wi-Fi while it is on the same Wi-Fi as the computer, and the computer lists it there, which it does once Wi-Fi connections are on for the phone. Pinky turns them on when you plug the phone in and it trusts the computer: it is the same setting as Finder's Show this iPhone when on Wi-Fi, so a phone already set up that way stays as it is. It is on by default; Settings › Phones › Use iPhones and iPads over Wi-Fi turns it off, which leaves the phones' setting alone. If a phone doesn't show up on Wi-Fi when you unplug it, its Checkup says where it stands under Wi-Fi: whether its Wi-Fi connection is on and whether Pinky turned it on, why Pinky couldn't, and whether this computer sees the phone on Wi-Fi.

  • An iPhone or iPad Pinky has used keeps working when you unplug it, as the same phone with its settings: Pinky moves it to Wi-Fi by itself, and back to the cable when you plug it in, and an agent's task goes on; its calls wait a few seconds meanwhile.
  • One Pinky has not used, such as a family member's iPad paired with this computer, shows as Found on Wi-Fi. Pinky reads its name, model and iOS version and does nothing else, and agents don't see it, until you choose Use, which sets it up over Wi-Fi, or Ignore, which keeps it off the list until you plug it in.
  • A locked iPhone or iPad on Wi-Fi shows as Locked on Wi-Fi, and Pinky connects to it once you unlock it: while it sleeps it drops off the network every minute or so, and connecting to it then lights its screen.
  • Setting one up over Wi-Fi: trusting the computer needs the cable, and so does making the Developer Mode switch appear while it is hidden (on a phone used with Xcode it shows already). Turning Developer Mode on happens on the phone, and Pinky mounts the developer disk image over Wi-Fi too, in about 9 s instead of 1.5 s. Add phone › iPhone says which step needs the cable.
  • Over Wi-Fi, Pinky talks only to the phone it paired with: it checks the certificate the phone got when it first trusted this computer, so another device on the network can't answer in its place. Below iOS 27, the connection to WebDriverAgent in Pinky on the iPhone isn't encrypted, so there it is only as safe as the Wi-Fi.

Over Wi-Fi each step is slower than on the cable, screenshots most of all. Measured on an iPad Pro 11-inch (3rd generation, iPadOS 27.0.1), Wi-Fi against the cable: a swipe shows on screen after 80 to 210 ms (60 to 90 ms), the home screen reads in 0.6 to 2.6 s (0.5 to 0.6 s), a screenshot takes 5 s (1 s), and 0.2 % of the video's packets were lost (none). Unplugging moved a running task to Wi-Fi in about 5 s, and plugging in moved it back in 2 to 6 s (details).

On a Mac, the system's device service, usbmuxd, can lose an iPhone on Wi-Fi after its connection broke once (its Wi-Fi turned off and on, say), and not look for it again for up to about an hour; Finder loses it too. Pinky notices when a phone you use is on the network but no longer listed, shows it as Lost on Wi-Fi, and offers Restart device service… on its page: after you confirm, macOS asks for an administrator's password, and every iPhone and iPad, also on a cable, disconnects for a second or two. sudo killall usbmuxd in Terminal does the same. Right after you unplug a phone it says so within about 10 seconds; it waits a minute otherwise, as a phone that wakes comes back by itself. A phone you unplug that this computer doesn't see on Wi-Fi at all shows as Not seen on Wi-Fi, with what may hide it: it's asleep, on another network or one that keeps devices apart (guest networks, some routers), a VPN, or Pinky not allowed on the local network.

On Linux and Windows, the system's device service does not list iPhones and iPads on Wi-Fi by itself: on Linux (the usbmuxd package) it lists them only on the cable, and on Windows (Apple Devices or iTunes) only while they are on the cable too. So there Pinky runs a small device service of its own in front of the system's, while it uses phones over Wi-Fi: it finds the phones paired with this computer on the network and connects to them directly, and passes everything about phones on a cable to the system's. All of Pinky's connections to iPhones and iPads go through it then, on the cable too. There is nothing to install or set up for it beyond the system's own (usbmuxd on Linux, Apple Devices on Windows). If you run a device service that lists phones on Wi-Fi itself, such as netmuxd, and start Pinky with USBMUXD_SOCKET_ADDRESS pointing at it (unix:///path/to/socket or tcp://127.0.0.1:port), Pinky uses that one instead and runs none of its own.

While Pinky opens a phone, or moves it between the cable and Wi-Fi, it shows Connecting or Moving to Wi-Fi rather than offline. Over Wi-Fi Pinky reads text from the live picture rather than from screenshots, which take about 5 s there. An iPhone or iPad without a passcode never reads as locked, so after it has dropped off the network to sleep, Pinky connects to it only once it has been back for 30 seconds.

iPhones on iOS 17.4 to 26

Below iOS 27, an iPhone takes taps and typing from a computer only through an app on the phone that hosts WebDriverAgent: Pinky on the iPhone, Pinky's own app, which you install once from a Mac with Xcode, signed with your Apple ID: plug the iPhone in and click Install Pinky on the iPhone on its page in Pinky (or in Add phone › Try an older iPhone), or run pinkyctl helper install in Terminal. Either builds it, signs it and installs it, and Pinky's window shows each step and asks you to unlock the phone when Xcode waits for it (how). While Pinky on the computer uses the phone, the app says so on the iPhone. Pinky Helper, the app Pinky installed for this before November 2026, keeps working, and Pinky still installs it when Pinky on the iPhone can't be built (pinkyctl helper install --helper-only asks for it). With a free Apple ID it has to be installed again every 7 days: two days before, the phone's page and its checkup remind you, with Install again, and once it has run out the phone shows as needing setup and says why (how to install it again). Pinky Helper has been tried on an iPhone XS Max on iOS 18.7.11, on Windows, over its cable and Wi-Fi; Pinky on the iPhone in its place has been installed over Pinky Helper on an iPhone 13 mini on iOS 27.0.1, where the computer started and stopped its testing service; not yet on iOS 17.4 to 26. Without it, Pinky can only show and read the screen (on a Mac) and open apps: no taps, swipes or typing. iOS 17.3 and earlier are not supported.

3. Add Pinky to your agent

In Pinky, open Settings › Agents and click Connect next to your agent. Pinky finds Claude Code, Claude Desktop, Codex, Cursor, VS Code, Copilot CLI, Windsurf (Devin Desktop) and Gemini CLI on your computer and adds itself to the agent's MCP servers, by the app's own path: with the agent's own command where it has one, such as claude mcp add, or in its settings file, which Pinky copies first and changes only in Pinky's entry. It also installs Pinky's agent guide, SKILL.md, where the agent reads skills, and keeps it current: when Pinky updates, it rewrites the guide it installed to the new version's. Until an agent is connected, a card in Pinky's sidebar offers to do it, or says where to get one.

Settings › Agents › Connect an agent: Claude Code connected; Claude Desktop, Codex, Cursor and VS Code with Connect buttons

  • Claude Desktop: Connect opens Pinky's extension in Claude Desktop; click Install there. Double-clicking pinky-<version>.mcpb from the release page does the same.

  • Other agents: Settings › Agents › Add an agent by hand shows the command for your copy of Pinky, with buttons that copy it. Add an MCP server (stdio) that runs it. In a JSON config, with the Homebrew cask or a Linux package:

    { "mcpServers": { "pinky": { "command": "pinkyctl", "args": ["mcp"] } } }
    

    Claude Code in a terminal: claude mcp add --scope user pinky -- pinkyctl mcp. Most agents read the guide from ~/.agents/skills/pinky/SKILL.md, Claude Code from ~/.claude/skills/pinky/SKILL.md.

The command is pinkyctl, not pinky: many computers already have another program named pinky. An agent on another computer or in a container can connect over HTTP instead (how). docs/mcp.md says what Connect changes for each agent.

4. Try it

Ask the agent to do something on your phone, for example "Open Messages on my phone and tell Sam I'm running late." The first time an agent connects, Pinky asks whether to allow it and what it may do. Payments wait for your click in Pinky's window; in Settings › Safety you can have sends, deletions and more wait too.

No phone at hand? Start an iOS Simulator or an Android emulator in Add phone › Virtual phone (below). Or quit Pinky and start it with two scripted demo phones (a payment to approve, a blocked banking app, a password field): /Applications/Pinky.app/Contents/MacOS/Pinky --fake on a Mac, pinkyctl --fake on Linux, or & "$env:LOCALAPPDATA\Programs\Pinky\Pinky.exe" --fake in PowerShell on Windows.

Using Pinky

Phones

  • Android: connected over USB or Wi-Fi (above). Pinky works over adb and a bundled scrcpy server. Pinky on the phone, Pinky's Android app, which ships with Pinky, reads the screen in about 70 ms instead of 2 s and types any language without the clipboard: the phone's page offers to install it (the phone may ask you to allow it once). Its accessibility service is on only while an agent works on the phone, as banking apps refuse to run next to one (why). On Android 13 and later, agents work on a background display, so the phone's own screen can stay off and locked. Text that an app draws without describing it to the accessibility tree, as in mini-programs and other web pages inside super-apps, games and maps, is read from the screen's pixels (OCR) on macOS and Windows, so agents can read it and tap it. Pinky reads a blocked app this way only once you allow it for the task, never a locked phone, and keeps no picture.

  • Wi-Fi on Android 10: Android 10 has no Wireless debugging. Plug the phone in and choose Use Wi-Fi instead… in the ⋯ menu under its picture (or in Settings › Phones): Pinky has the phone's adb listen on the network (adb tcpip, port 5555), connects to it at its Wi-Fi address and says when you can unplug it. It connects again by itself when the phone is back on the network, also at a new address. While it is on, any computer on the same network can try to connect to the phone: if the phone asks Allow USB debugging? when you are not connecting it yourself, tap Cancel, and use it only on Wi-Fi you trust. It lasts until the phone restarts; then plug it in once and choose Use Wi-Fi again. Stop the Wi-Fi connection in the same menu turns it off (details).

  • iPhone: connected over USB or Wi-Fi (above) and prepared by Pinky (above); iPads work the same way. What Pinky can do depends on the iOS version and on how Pinky connects, which you can choose for each iPhone in Settings › Phones (Automatic picks by version, as below):

    iOSHowWhat worksTested on
    27 and laterXcode's Device Hub protocol; nothing installed on the phoneEverything but pinching. Typing pastes the text and puts your clipboard backiPhone 13 mini, iOS 27.0.1
    17.4 and later, with Pinky on the iPhonePinky on the iPhone, Pinky's app with WebDriverAgent in it (or Pinky Helper, installed before), installed once on a Mac with Xcode, from Pinky's window or with pinkyctl helper install (how): automatic on iOS 17.4 to 26, your choice on 27Everything, and the phone shares no screen, so banking apps that refuse screen sharing keep working (DBS digibank and China Merchants Bank in testing). Slower than Device Hub: a home screen reads in about 7 s instead of under 0.5 s, a tap takes 0.5 to 0.8 s. Now and then iOS asks for the passcode on the phone before it starts. The live picture works on macOS and WindowsWith Pinky on the iPhone: installed on an iPhone 13 mini, iOS 27.0.1, its testing service started and stopped from the computer. With Pinky Helper: iPhone 13 mini, iOS 27.0.1, with it chosen; iPhone XS Max, iOS 18.7.11, on Windows: the live picture over its cable and Wi-Fi, and its keys and swipes; iOS 18.5 and 26.5 Simulators
    17.4 to 26, without itThe developer services alone; nothing installedWatching (a few frames a second, macOS and Windows), reading the screen (placed by OCR, macOS only) and opening apps and links. No tapping, swiping, typing or Home: the phone offers no input without Pinky on the iPhoneThe same services on iOS 27.0.1; not yet on a phone below iOS 27
    17.3 and earlierNot supported: before 17.4 the connection needs administrator rights, and iOS 16 and earlier need a developer disk image that current Xcode no longer includes

    Pinky on the iPhone carries Appium's WebDriverAgent and is signed with your own Apple ID. The signature lasts 7 days with a free Apple ID and a year with a paid developer account. Pinky reads on the iPhone when it runs out: two days before, the phone's page and its checkup remind you to install it again (Install again in Pinky, or pinkyctl helper install, on a Mac with Xcode), and once it has run out the phone shows as needing setup and says why, instead of failing to start it (how).

  • Screen sharing on iPhone: while Pinky streams an iPhone's screen, iOS tells apps that the screen is being shared, and some banking apps (DBS digibank and China Merchants Bank among them) refuse to run or warn you. iOS also keeps the camera and microphone from apps then, so the camera shows black and scanning a code fails. It works the other way round too: while an app uses the camera or microphone (a call or FaceTime, Camera, Voice Memos), iOS 27 doesn't let Pinky show the iPhone over Device Hub. Its page then says Camera or microphone in use and what to do, and Pinky connects by itself once the call ends or the app closes. Pinky streams it while the phone's page or tile is open in Pinky, while an agent works on it, and for 30 seconds after; then such apps work again. Over CoreDevice, agents cannot use them. Install Pinky on the iPhone as well, and leave the phone on Automatic (Settings › Phones): tasks use CoreDevice, and Pinky moves a task to Pinky on the iPhone, which shares no screen, when it opens DBS digibank or China Merchants Bank, or when the agent asks for it; the phone goes back to CoreDevice after the task. Or connect the iPhone through Pinky on the iPhone for every task.

  • Simulators and emulators: an iOS Simulator (on a Mac with Xcode) or an Android emulator (from Android Studio) can be a phone too. Add phone › Virtual phone lists the ones on the computer: Start starts one, and once it runs it shows up as a phone, marked Simulator or Emulator; Shut down stops it. An Android emulator Pinky starts has no sound, so it never switches a Bluetooth headset to its microphone. Only you start them: agents have no tool for it. The live picture, recordings, approvals and rules work as on a phone. Pinky finds the Android SDK the way Android Studio does (ANDROID_HOME, then ANDROID_SDK_ROOT, then where Android Studio installs it), and an emulator then works like an Android phone on a cable. For Simulators, Pinky builds Appium's WebDriverAgent with your Xcode the first time: from the source of one release, whose files it checks before building, unsigned and without an Apple ID. That takes 20 seconds to a few minutes, and the build is kept until Xcode changes. Pinky creates no Simulators or emulators and downloads no system images: create them in Xcode (Window › Devices and Simulators) or in Android Studio's Device Manager (details).

  • Locked phones: Pinky never keeps a phone awake. It wakes the screen before a step; save the phone's PIN in Settings › Phones to unlock it from the computer with Touch ID. Agents never see the PIN. On Android this is checked on AOSP-style lock screens (LineageOS on a Mi 10 Pro, the Android 10, 16 and 17 emulators); the lock screens of Xiaomi, Samsung, OPPO, OnePlus, vivo, Honor and Huawei are only covered by tests made from what is known of them, and where Pinky cannot read the PIN pad with confidence it enters nothing (details).

  • Pinching: agents pinch to zoom maps, photos and pages in and out, and turn them with two fingers. You can too, on the phone's picture in Pinky: pinch on the trackpad (on Linux, under Wayland only), or drag with Option held (Alt on Windows and Linux), as in Xcode's Simulator, and a second finger moves opposite the pointer across the screen's centre. Like any touch of yours, it pauses the agent. iPhones pinch through Pinky on the iPhone. On iOS 27 left on Automatic, Pinky moves to it for a pinch, an agent's or yours (your first pinch only starts the move, which takes a few seconds), and back afterwards; without it they cannot pinch, and agents are told so.

  • Dragging: agents drag with phone_drag: press and hold to pick something up, move through the points they name, rest where needed, and let go. They move app icons to another home screen page (resting near the screen's edge turns the page) or into a folder, reorder lists and move sliders. The rules and approvals treat a drag like a swipe, checking what lies under every point the finger touches, and the approval's screenshot draws the whole route. It works on Android and on iPhones through Device Hub or Pinky on the iPhone. Tried on an Android emulator and an iOS Simulator, not yet on a phone.

  • Files: on Android, agents copy files between the phone's Pinky folder (/sdcard/Pinky, the only place on the phone they may reach) and a folder on the computer, and copying to the phone asks you first. Pictures copied there show in the phone's gallery and photo pickers, so an agent can attach them in a chat app. An agent on another computer cannot reach that folder, so it sends Pinky the file first: small files in the call, larger ones to a one-time link Pinky gives it. Copying the file to the phone then asks you as usual (details). Not on iPhones.

  • Screenshots and reports for bug reports: an agent testing an app can save a screenshot as a file, and, as the task ends, the task's report (its steps with screenshots, as HTML and JSON), to put in a bug report or a pull request. They go into the phone's folder on the computer, on iPhones too, and saving asks nothing, as nothing on the phone changes. They show only what the agent may see: codes covered, nothing of a locked phone or a blocked app, even one you allowed for the task. The task's screen recording covers neither codes nor blocked apps, so it goes to the agent only when you allow it: when the agent exports a recorded task, Pinky asks you whether it gets the recording too (an MP4 next to the report), every time, and no preset or Always allow answers that for you. If you decline or don't answer, the agent gets the report alone. An agent on another computer gets a one-time link for each file (details).

  • Links: agents open links with phone_launch: web pages, an app's own links (myapp://…), and links for calls, texts and email. Before anything opens, Pinky finds the app the phone would open the link in, and treats the link as opening that app and as tapping what it stands for: a blocked app's links stay blocked, links into apps outside the task are refused, and a payment link waits for you like a Pay button. Links that read files on the phone, run code or run shortcuts (file:, content:, intent:, javascript:, data:, Shortcuts) are always refused, and so is a link the phone would ask you to pick an app for. The approval and Activity name the link and the app. On an iPhone a web link opens in Safari; through Pinky on the iPhone, links need WebDriverAgent 4.11 or later (details).

  • Apps you build: agents can install an app from the phone's folder on the computer (an APK, or the split APKs of one app, on Android; an .ipa or .app development-signed for that iPhone), update it, uninstall it and force-quit it, so a coding agent can put its build on the phone, open it and check it. Installing and uninstalling ask you, with the app's name, id, version and who signed it; Allow for this task lets the agent install its next builds of the same app, signed the same way, without asking again, and More options › Always allow does so in later tasks too, for that agent and phone, until you take it back in Settings › Safety. A build signed by someone else, or another app, still asks, and uninstalling asks every time. Pinky's own apps, system apps, finance apps, password managers and apps you blocked can't be installed over, uninstalled or stopped (details).

  • App logs: an agent testing an app can read that app's own log lines and crash reports, to see why it failed. The first time in a task, Pinky asks you (Allow for this task covers the rest of it, and More options › Always allow stops asking for that agent, phone and app until you take it back in Settings › Safety), unless the app is a development build (a debug build on Android, an app Xcode installed on an iPhone). Agents get only that app's lines, never other apps' or the system's, and never the logs of blocked, banking, wallet or password-manager apps, the phone's own apps or Pinky's. History keeps how many lines were read, not the lines. An iPhone keeps no log history Pinky can read, so there Pinky listens from the agent's first read until the task ends (details).

  • Testing an app: agents can flip the switches developers test with: turn the screen, switch between light and dark appearance, simulate a location, and open an app in another language and region. These change the phone's settings, so on a real phone you approve them first (Allow for this task covers the rest of the task, and More options › Always allow stops asking for that agent on that phone until you take it back in Settings › Safety); on emulators and Simulators they go through at once unless you chose to approve more than payments. Pinky puts everything back when the task ends, and leaves alone what you changed yourself meanwhile. Rotation and appearance work on Android and on iPhones with Pinky on the iPhone; a simulated location on Android emulators, iOS Simulators and iPhones with Pinky on the iPhone; another language on Android 13 and later and on iPhones (details). You can turn the screen yourself too, with Rotate in the ⋯ menu under its picture (on an iPhone or iPad, Pinky on the iPhone installed: on iOS 27 Pinky moves to it for the turn, and agents' turns and pinches move their task to it too): like a touch on the picture, it pauses an agent working on the phone's screen, but not one working on a background display. Rotation was tried on a Samsung Galaxy A12 (Android 13), a Pixel 9a (Android 17), an iPhone 12 Pro Max (iOS 18), an iPhone Air (iOS 27) and an iPad mini (iPadOS 27); the rest on an Android emulator and an iOS Simulator, not yet on a phone.

  • A phone in its own window: Open in a window in the phone's ⋯ menu under its picture (also in its right-click menu in the sidebar and on its tile in All phones) opens a window with only the phone's live screen and its keys (Home; Back and Recents on Android), to keep beside your other work as macOS's iPhone Mirroring does, for iPhones, iPads and Android phones alike. You use it as the picture on the phone's page: a click, typing or a scroll there takes over and pauses an agent, and the bar under the screen then shows Hand back. The window keeps the screen's shape as you resize it and turns with the phone; it shares the phone's one stream with Pinky's main window, also while that is closed. When the phone is offline, paused or connecting, the window says so, with Show in Pinky; it closes when you remove the phone. Opened again, it comes to the front. The pin in its bar, Keep on top, keeps it above other apps' windows; it is off at first.

  • Removing a phone: Remove this phone… in the phone's ⋯ menu (also on its page while it is offline, on its tile in All phones, in its right-click menu in the sidebar and in Settings › Phones) takes it off the list and deletes its saved PIN and its settings. Its tasks, screenshots and recordings stay in Activity unless you tick the box to delete them too, and a task running on it stops. A phone on a cable comes back at once, as a new phone, until you unplug it. A phone on Wi-Fi is disconnected and stays off the list, even when adb connects it again by itself; to add it back, pair it again in Add phone or plug it in. An iPhone or iPad on Wi-Fi stays off the list until you plug it in. Pinky does not unpair the phone from your computer: its USB or wireless debugging pairing, or the iPhone's trust, stays for other apps (details).

  • Pausing a phone: Pause connection in the phone's ⋯ menu (also in its right-click menu in the sidebar and on its tile in All phones) keeps the phone in Pinky but stops its screen stream and Pinky's connection to it: an iPhone's tunnel and WebDriverAgent, an Android phone's scrcpy and its connection to Pinky on the phone. A task on it ends, agents are told it is paused, and Pinky does not reconnect it over Wi-Fi. It stays paused when Pinky restarts. Resume it with Resume on its page or Resume connection in its right-click menu, or plug it in by cable. A phone paused while plugged in stays paused until you unplug it and plug it in again, so pausing a phone that charges does not undo itself. The phone page's header says when the phone is streaming its screen to Pinky; an iPhone stops 30 seconds after you last look at it or use it. All phones shows an iPhone that no task works on with its last picture rather than live, so leaving Pinky there does not keep the iPhone awake or sharing its screen (details).

  • Approvals away from the computer: with the web mirror served through Tailscale (Settings › Phones › Web mirror), turn on Answer approvals in the browser, click Make a link next to Add a phone and open the link on your own phone. The phone makes a passkey for this computer and shows a code; when Settings shows the same code, say which phone the browser is on and click Allow. While an agent uses that phone, and for 30 seconds after, the page there answers nothing: whoever drives the phone could tap Allow. The page then lists the steps waiting for you, with the screenshot and what the agent wants to tap, and you tap Allow or Deny twice there; the second tap asks for Face ID, a fingerprint or the phone's passcode. It answers a payment, a send or an agent's question with Allow (this step only) or Deny; a new agent, a blocked app and handoffs stay in Pinky's window. No answer within 60 seconds still means no, and the first answer, on the computer or the phone, counts. Pinky forgets the phones you added when it quits (details). Tried with fake phones, not yet in Safari on an iPhone.

Phones away from home

An Android phone does not have to be on the computer's network. With Tailscale on the computer and on the phone, signed in to the same account, Pinky reaches the phone through it: leave the computer at home and take the phone out, on mobile data or another Wi-Fi. Android runs one VPN at a time, so keep other VPN and proxy apps off on the phone: they turn Tailscale off.

  1. Set the phone up once while it is near the computer, by cable or on the same Wi-Fi: Settings › Phones › Use away from home › Turn on…. Add phone › Android › Phone not on this network? Use Tailscale walks you through Tailscale on both sides and lists the phones on your tailnet.
  2. Pinky has the phone's adb listen on the network (adb tcpip, port 5555) and connects to the phone at its Tailscale address. It uses that connection whenever the phone has no connection on the computer's network, so the phone stays in the list as you leave.
  3. The phone's adb then takes connections on every network the phone joins, from the computers it already trusts; any other computer makes the phone ask. Only the way through Tailscale is encrypted. It lasts until the phone restarts, and Turn off stops it at once. Pinky only reads Tailscale's status and never changes its settings.
  4. Keep this computer awake for phones away (Settings › Phones, on by default) stops the computer's idle sleep while a phone is connected through Tailscale. A MacBook still sleeps when its lid closes.

…view the full README on GitHub.

// faq

What is pinky?

Let AI use your iPhone or Android phone, with you in the loop: any MCP agent from macOS, Windows or Linux, or Pinky itself, right on the phone.. It is open-source on GitHub.

Is pinky free to use?

pinky is open-source under the Apache-2.0 license, so it is free to use.

What category does pinky belong to?

pinky is listed under mcp-servers in the Claudeers registry of Claude-compatible tools.

4 views
★ 2,160 stars
unclaimed
updated 4 days ago

// embed badge

pinky on Claudeers
[![Claudeers](https://claudeers.com/api/badge/pinky.svg)](https://claudeers.com/pinky)

// retro hit counter

pinky hit counter
[![Hits](https://claudeers.com/api/counter/pinky.svg)](https://claudeers.com/pinky)

// reviews

// guestbook

0/500

// related in MCP Servers

🔓

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete…

// mcp-serversf/⟨HTML⟩★ 175,627◷ NOASSERTION[ claude ]
🔓

A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Gemini CLI & Hermes Agent. Only official website: ccswitch.io

// mcp-serversfarion1231/⟨Rust⟩★ 151,540◷ MIT[ claude ]
🔓

🪨 why use many token when few token do trick — Claude Code skill that cuts 65% of tokens by talking like caveman

// mcp-serversJuliusBrussee/⟨JavaScript⟩★ 117,780◷ MIT[ claude ]
🔓

An open-source AI agent that brings the power of Gemini directly into your terminal.

// mcp-serversgoogle-gemini/⟨TypeScript⟩★ 108,744◷ Apache-2.0[ claude ]

// built by

1 of its contributors also build on official projects — claude-cookbooks, claude-quickstarts

→ see how pinky connects across the ecosystem