cd /news/ai-agents/diygod-pinky-mcp-agents-that-drive-y… · home › topics › ai-agents › article
[ARTICLE · art-171152] src=explainx.ai ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

DIYgod Pinky: MCP Agents That Drive Your Phone With You in the Loop

DIYgod's open-source project Pinky, created November 6, 2026, reached roughly 2,288 GitHub stars by mid-November 2026 by letting any MCP agent on macOS, Windows or Linux drive a real iPhone or Android phone with a human approving mirrored actions. Pinky ships its own adb build when platform tools are missing, reuses system adb when Android Studio or Homebrew already installed it, and documents per-brand Android setup for Xiaomi, Samsung and Pixel plus Wi-Fi pairing failures, macOS Local Network permission, Windows USB drivers and Linux udev packages. The project's README recommends a dedicated handset or user profile, MCP tool allowlists and session recording, since Pinky is remote-control infrastructure exposed to indirect prompt injection.

by read8 min views3 publishedNov 17, 2026
DIYgod Pinky: MCP Agents That Drive Your Phone With You in the Loop
Image: Explainx (auto-discovered)

DIYgod/pinky is a fast-growing open-source bridge that lets desktop MCP agents operate a real iPhone or Android phone while a human stays in the loop — screen mirror, taps, typing, and OEM-specific Android debugging guides included. Trending metadata in mid-November 2026 showed roughly 2,288 stars on a repo created November 6, 2026, putting it beside Qwen Code and FFmpeg skills for agents in the agent harness wave.

Pinky matters because mobile apps are where bank auth, 2FA, and super-app workflows live, yet most computer-use demos still target browsers on laptops. Pinky exports that surface to MCP — the same protocol we track in Google Stitch skills and Bedrock agentic retrieve.

TL;DR #

Piece What Pinky does
Host macOS, Windows, or Linux desktop app
Protocol MCP in and out — attach your agent
Target Android (adb USB/Wi-Fi) +iPhone flows in README
Loop Human approves mirrored actions
Remote Tailscale path documented for away-from-home phones

What the README promises #

DIYgod describes Pinky as: “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.”

Core workflow:

  1. Install Pinky on the desktop (project ships updaters for Mac/Windows/Linux archives per README).
  2. Add phone — wizard surfacesper-brand Android steps (Xiaomi security toggles, Samsung drivers, Pixel paths).
  3. Optional companion app — “Pinky on the phone” for faster screen parsing and multilingual keyboard injection.
  4. Checkup menu — per-device diagnostics when adb permissions or OEM switches block automation.

Pinky ships its own adb build when platform tools are missing, but reuses system adb when Android Studio or Homebrew already installed — sharing the adb server so Pinky and Studio coexist.

Android setup depth (why stars piled on) #

Mobile agent bridges usually die on OEM quirks. Pinky’s README spends real pixels on:

  • Wi-Fi pairing failures — guest networks, AP isolation, “pair with code” fallback.
  • macOS Local Network permission — silent failure mode without the privacy toggle.
  • Windows drivers — Google, Samsung, or OEM USB drivers called out explicitly.
  • Linux udev — package names per distro.
  • Anti-spoofing — marks trusted phones so random LAN adb endpoints cannot impersonate yours.

That operational honesty is why builders star it faster than yet another “vision model clicks UI” slide deck.

Threat model for agents on phones #

Event bell triggering coordinated automation as an agent-on-phone metaphor

Pinky is not malware — it is remote control infrastructure. Pair it with lessons from:

Practical rules:

  • Dedicated handset or user profile — no primary banking SIM.
  • MCP tool allowlists — block shell, filesystem, and screenshot export except explicit tasks.
  • Session recording — mirror is proof in incident reviews.
  • Never approve Pinky drivingrecruiter “fix my audio” scripts — same ClickFix DNA as crypto intrusions.

How to try Pinky this week #

  1. Clone github.com/DIYgod/pinky and readAdd phone for your OEM.
  2. Wire Claude Code or another MCP client using patterns fromMCP comparison guide if you maintain a registry.
  3. Run a benign task — reorder a test calendar event, not production payroll.
  4. Compare latency vs native mobile assistants ; log tokens if you bill API usage.

What developers ask on GitHub Issues (setup pain) #

Why does Wi-Fi pairing find zero devices on Mac? Pinky’s README blames missing Local Network permission — macOS fails silently. Open System Settings → Privacy & Security → Local Network and enable Pinky.

Why did adb see unauthorized? Revoke USB debugging authorizations on the phone, replug, tap Allow — same as Android Studio docs.

Can Pinky run without the on-phone companion app? README says the companion makes screen reading much faster and enables multilingual typing; expect degraded UX without it.

Does Pinky support iOS the same as Android? Marketing covers both platforms; Android documentation is deeper because adb exposes more inspection hooks. Treat iOS flows as read the latest README before production.

Is DIYgod trustworthy for security? DIYgod is a prolific maintainer (RSSHub, etc.). Popularity is not audit — review source before enterprise rollout.

Token and API cost considerations #

Phone agents burn tokens when every screen mirror becomes a vision or DOM snapshot. Mitigations:

  • Crop mirror regions to the app you automate (when Pinky supports region tools per README updates).
  • Cache plans — ask the model for a step list, then approve batched taps.
  • Local models via Ollama for planning, cloud for hard steps — same hybrid pattern asTensorFold local inference .

Compliance notes for EU and US teams #

Automating banking or health apps may violate terms of service even when technically feasible. Pinky does not grant legal permission to bypass app restrictions. Pair legal review with university library scraping ethics lessons: capability ≠ entitlement.

Compared to other computer-use paths #

Approach Surface Pinky difference
Browser-only agents DOM Cannot reach native banking apps
Android emulator Virtual device Misses real NFC/SMS
Pinky Physical phone Real push notifications + OEM security
Official Claude mobile First-party app Less MCP composability

iPhone path (high level) #

The GitHub README markets both mobile platforms. Android documentation is longer because adb exposes richer diagnostics. For iOS, expect device trust flows similar to other screen-mirror tools: pairing, developer mode, and companion-app installs. Always read the latest README section — Pinky’s first weeks saw 1,400+ commits, so screenshots in this post may lag releases.

MCP wiring sketch #

Two MCP connectors bridging a desktop agent and a phone workflow

Typical Claude Code mcp.json pattern (illustrative — verify ports in Pinky docs):

{
  "mcpServers": {
    "pinky": {
      "url": "http://127.0.0.1:PORT/sse"
    }
  }
}

Replace PORT with Pinky’s live server. Restrict stdio vs SSE per your firewall. Use MCP security guidance before exposing the socket beyond localhost.

When Pinky beats cloud device farms #

Scenario Pinky angle
2FA on real SIM Physical device receives SMS
Super-app testing WeChat, Grab, regional wallets
Push notification triggers Agent waits for user-visible events
Screenshot-heavy QA Human sees mirror before tap

When you only need browser automation, Vercel agent-desktop stays simpler.

Tailscale and remote debugging #

Pinky’s README documents Tailscale so a laptop at home can drive a phone in another site — useful for QA teams distributed across countries. Threat model expands: Tailscale ACLs must limit which peers can hit Pinky’s port, or any compromised laptop becomes a remote tap on a developer’s 2FA device.

Stars and velocity caveat #

Trending feeds listed ~2,288 stars with repo age ~11 days at mid-November 2026. Star velocity can reflect DIYgod’s existing audience from RSSHub and adjacent tools, not only organic discovery. Re-check github.com/DIYgod/pinky before citing live counts in investor slides.

Integration with Claude Code and Codex #

Because Pinky exposes MCP, it composes with the same hosts covered in Claude HTML artifacts and Qwen Code terminal agents. Pattern: plan on desktop, execute taps on phone, human approves transfer dialogs in the mirror.

Failure modes #

  • Guest Wi-Fi isolation — pairing succeeds on USB, fails on LAN.
  • OEM killing background adb — Xiaomi power savers.
  • Prompt injection in mirrored apps — malicious page asks agent to approve transfer.

OEM debugging checklist (condensed from README) #

Samsung devices may need driver reinstall after Windows Update. Xiaomi users must enable USB debugging (Security settings) or Pinky Checkup flags red. Pixel owners typically use Google’s USB driver. Linux users install udev packages before first plug. Each step exists because phone agents fail at adb, not at MCP — budget onboarding time in sprint plans.

Roadmap watch #

Pinky’s commit velocity suggests rapid OEM checklist updates. Subscribe to release notes if you depend on Wi-Fi pairing for CI farms. Breaking changes to adb packaging could affect headless Mac Mini phone farms used in mobile QA consultancies.

Accessibility and human-in-the-loop UX #

Pinky’s mirror is inherently visual. Teams needing screen-reader-first workflows should not replace VoiceOver/TalkBack testing with agents — use Pinky for regression on sighted flows only, and keep manual accessibility audits in the loop per platform guidelines.

Why human-in-the-loop still wins for payments #

Financial apps use device binding and step-up auth precisely because remote desktop attacks exist. Pinky does not bypass those controls — it automates the human’s hands. Fraud teams should still monitor for new device enrollment when engineers test automation.

Comparison to official mobile assistants #

Siri and Gemini on-device assistants run with OS sandboxing. Pinky runs with developer privileges you grant via adb. The threat model is closer to MDM remote control than to chatbots. Document Pinky in your asset inventory today if auditors ask which tools can touch mobile MFA devices during compliance reviews.

Accurate as of November 17, 2026. Setup steps paraphrase the DIYgod/pinky README; star counts are from trending metadata and change hourly on GitHub.

── more in #ai-agents 4 stories · sorted by recency
── more on @diygod 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/diygod-pinky-mcp-age…] indexed:0 read:8min 2026-11-17 · —