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. DIYgod/pinky https://github.com/DIYgod/pinky?ref=explainx is a fast-growing open-source bridge that lets desktop MCP https://modelcontextprotocol.io/introduction?ref=explainx 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 https://explainx.ai/blog/qwen-code-open-source-terminal-coding-agent-github-trending-guide-2026 and FFmpeg skills for agents https://explainx.ai/blog/ffmpeg-skill-local-video-mcp-coding-agents-github-trending-2026 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 https://explainx.ai/blog/google-stitch-skills-agent-skills-mcp-claude-code-cursor-install-2026 and Bedrock agentic retrieve https://explainx.ai/blog/bedrock-agentic-retrieve-agentcore-memory-multi-user-guide-2026 . 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 surfaces per-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: - Indirect prompt injection https://explainx.ai/blog/what-is-indirect-prompt-injection-ai-agents-guide-2026 — malicious content in apps the agent reads. - GTIG SOMBERMEME settings attacks https://explainx.ai/blog/google-gtig-sombermeme-claude-code-settings-backdoor-november-2026 — trusted config files become execution paths. - Vercel agent-desktop https://explainx.ai/blog/vercel-agent-desktop-accessibility-tree-computer-use-cli-2026 — accessibility-tree agents still exfiltrate secrets when prompts go rogue. 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 driving recruiter “fix my audio” scripts — same ClickFix DNA as crypto intrusions. How to try Pinky this week 1. Clone github.com/DIYgod/pinky https://github.com/DIYgod/pinky?ref=explainx and read Add phone for your OEM. 2. Wire Claude Code or another MCP client using patterns from MCP comparison guide https://explainx.ai/blog/what-is-a2a-agent2agent-protocol-mcp-comparison-guide-2026 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 as TensorFold local inference https://explainx.ai/blog/tensorfold-zig-local-llm-inference-metal-cuda-api-2026 . 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 https://explainx.ai/blog/university-libraries-ai-scraping-bots-open-access-training-data-nov-2026 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 https://explainx.ai/blog/mcp-security-guide-2026 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 https://explainx.ai/blog/vercel-agent-desktop-accessibility-tree-computer-use-cli-2026 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 https://explainx.ai/blog/claude-html-in-canvas-interactive-artifacts-desktop-november-2026 and Qwen Code terminal agents https://explainx.ai/blog/qwen-code-open-source-terminal-coding-agent-github-trending-guide-2026 . 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. Related reading 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.