Mirroir Mcp

io.github.jfarcandPublished by GitHub account jfarcandv0.45.0Updated Nov 6, 2026

Drive a stock iPhone via iPhone Mirroring: no Developer Mode, Xcode or WDA. LLM-free skill replay.

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Drives a stock iPhone through macOS iPhone Mirroring, letting an agent read the screen, tap, type and swipe, then replay recorded runs without an LLM.

What you can do
  • Read the mirrored iPhone screen and inspect what apps show
  • Tap, type, swipe and drag on the phone through the mirror
  • Record a run and generate reusable skill files from it
  • Replay compiled skills from the CLI with no AI in the loop
  • Run one scenario across the phone, a browser and HTTP endpoints, with a drift verdict
  • Play turn-based or tap-driven games frame by frame under a budget
When to use it
Useful when an agent should operate real App Store apps on a physical iPhone without Developer Mode, Xcode or jailbreak, or when a first exploratory run should become a deterministic, token-free replay for CI.
Requirements
macOS 15 or later with an iPhone connected through iPhone Mirroring; installed via npx or Homebrew; macOS Screen Recording and Accessibility permissions; a compatible MCP client. No Developer Mode, Xcode, jailbreak or on-device agent is needed.
Before you install
Gives an AI control of your phone: taps, typing, sending, buying, deleting and settings changes are possible once tools are allowed. Only 12 read-only tools are exposed until you permit more in permissions.json; blockedApps can keep the agent out of sensitive apps. It never presses password or Touch ID sheets, but screen content read by the agent goes to whichever model your client uses. A once-a-day npm version check runs unless updateCheck is disabled.

Installation

In SourceWeft

  1. Open Mirroir Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[mirroir-mcp]

mirroir-mcp

[npm version] [Build] [License] [macOS 15+] [Discord]

Let your agent use your real iPhone, then replay what it did without an LLM.

[An agent reads the commute time in Waze on a real iPhone, then posts it in a Slack channel]

A real run on a real iPhone, sped up: the agent reads the ETA in Waze, then posts it in Slack.

No Developer Mode, no Xcode, no WebDriverAgent, no jailbreak. mirroir-mcp works through macOS iPhone Mirroring, so it reaches any app on your phone, including App Store apps you could never build. It works from any MCP client, with 39 tools.

Quick start

You need macOS 15 or later and an iPhone connected through iPhone Mirroring. Paste this into your coding agent (Claude Code, Codex, Cursor, OpenClaw, …):

text
Set up mirroir-mcp so you can drive my iPhone: follow https://github.com/jfarcand/mirroir-mcp/blob/main/docs/onboarding.md step by step, and finish by reading back what my iPhone screen shows.

Or install it yourself:

bash
npx -y mirroir-mcp install    # or: brew tap jfarcand/tap && brew install mirroir-mcpnpx -y mirroir-mcp doctor     # names anything left to fix

OpenClaw, Claude Desktop, Cursor, VS Code and the other clients: Install.

Then ask for something:

Open Calendar, create a new event called "Dentist" next Tuesday at 2pm.
Open my Expo Go app, tap "LoginDemo", test the login screen with[email protected] / password123. Screenshot after each step.
Start recording, open Instagram, scroll the feed and open my profile, stop recording.

Why mirroir

  • Nothing to install on the phone. The iPhone stays stock: no signing, no provisioning profile, no on-device agent. If iPhone Mirroring shows it, mirroir can drive it.

  • Your Mac stays yours. Taps, typing and swipes reach the mirror without bringing it to the front, so you can keep working. Drags and two-finger gestures bring it forward for a moment, then hand your app back.

  • Explore once, replay without an LLM. generate_skill explores an app and writes SKILL.md files. A compiled skill replays from the CLI with no AI in the loop (mirroir test), so CI runs are deterministic and cost no tokens.

  • One test across phone, web and backend. mirroir-run is our companion test runner, a separate binary. One YAML scenario can drive the iPhone, a browser, HTTP endpoints and subprocesses, then compare what the page and the phone showed. See Web and iOS in one scenario.

  • Drift fails loudly. mirroir-run has a third verdict beside pass and fail: DRIFT, exit code 65, when every assertion held but the output moved past its baseline. Your CI lane decides whether drift blocks a merge.

  • It plays games, too. A scene: step plays a turn-based or tap-driven game, frame by frame, under a hard budget. See Games.

    [The console and a real iPhone side by side during a full chess game: each move is logged as it is played, ending in checkmate against the Maximum bot on Chess.com]

    A real game on a real iPhone: the model reads the board, Stockfish picks the moves, mirroir plays them against Chess.com's strongest bot. The opening runs at 2.5×, the middle game at 45×, the finish at 2×.

How it compares

mirroirphone-harnessmobile-mcpAppium
Physical iPhone, no Developer Mode or signingYes — stock phone via iPhone MirroringYes — stock phone via iPhone MirroringUSB-connected, trusted device (see its README)No — WebDriverAgent via Xcode, Developer Mode
App Store apps you can't buildYesYesYesYes, on a provisioned device
Your own iPhone from any MCP clientYesNo — its MCP server is cloud-only; local phones use its CLIYesThrough the separate appium-mcp
Replay without an LLMYes — compiled skills, mirroir testPython scripts you write; no recorder or compiled replayNo — the agent drives every runYes — test code
Distinct drift verdictYes — DRIFT, exit 65NoNoNo — pass / fail
One scenario across iPhone + web + HTTPYes — mirroir-runNoNoVia your own test code
AndroidNo — an emulator window can be driven only as a generic macOS windowYesYesYes
iOS SimulatorNoNoYesYes
Hosted cloud phonesNoYes — Phone Harness CloudYes — Mobile Next CloudVia third-party device clouds

phone-harness is the closest tool here: it also drives a stock iPhone through iPhone Mirroring, and it adds Android and hosted phones, which mirroir doesn't have. mobile-mcp and Appium cover Android and simulators too. mirroir goes further after the agent's first run: that run becomes a replay that needs no LLM, and a test that tells you when the output moves.

Safety

Giving an AI access to your phone demands defense in depth, so mirroir-mcp is fail-closed.

  • Read-only until you say otherwise. Without a config file, only the 12 read-only tools are exposed. Every tool that changes something stays hidden from the client until you allow it in permissions.json.
  • Sensitive apps can be blocked. blockedApps keeps the AI out of apps like Wallet or Banking, even when other tools are allowed.
  • Passwords stay yours. mirroir never presses a sheet that asks for a password or Touch ID, and it tells agents to ask you before sending, buying, deleting or changing a setting.
  • No root, no daemon, no telemetry. It runs as your user with Screen Recording and Accessibility. The one network call it makes by default is a once-a-day version check against npm (updateCheck: false turns it off). What your agent reads from the screen goes to whichever model your client uses.
  • Kill switch. Close iPhone Mirroring to stop all input instantly.

See Security for the full threat model.

Documentation

InstallEvery install path, per-client setup, updating, uninstalling
OnboardingSetup written for the agent: prerequisites, install, doctor, and a read-only proof
Tools ReferenceAll 39 tools, parameters, and input workflows
How mirroir sees the screenThe observe, reason, act loop; OCR, icon detection, AI vision
Skills, exploration and CIAPP.md, skills, generate_skill, mirroir test, compiled replay, AI diagnosis, patterns
mirroir-runReplay across iPhone, web, HTTP and subprocesses; GitHub Actions; Maestro import
GamesShell and scene, the scene: step, game controls
CLI ToolsRecorder, doctor, keyboard layout
ConfigurationAll settings: screen intelligence, input timing, exploration, AI providers
FAQSecurity, focus stealing, keyboard layouts, embacle/vision mode
SecurityThreat model, kill switch, and recommendations
PermissionsFail-closed permission model and config file
Known LimitationsFocus stealing, keyboard layout gaps, autocorrect
Patterns & SkillsElement patterns, screen recipes, APP.md app descriptions, and the detection pipeline
Exploring a New AppStep-by-step playbook for onboarding a new app — APP.md, permissions, components, exploration goal
YOLO Icon DetectionRecommended YOLO models, CoreML setup, and configuration
Compiled SkillsZero-OCR skill replay
TestingFakeMirroring, integration tests, and CI strategy
Web and iOS in one scenarioHow mirroir-run hands iOS blocks to mirroir-mcp, and how cross_surface compares a browser with a phone
Cross-surface replaymirroir-run scenario grammar, .mirroir/ plan, SAMPLE.md, judge profiles, CI
TroubleshootingDebug mode and common issues
ContributingHow to add tools, commands, and tests
Skills MarketplaceSkill format, plugin discovery, and authoring

Community

Join the Discord server to ask questions, share skills, and discuss ideas. Contributions are welcome: see CONTRIBUTING.md. By submitting a patch, you agree to the Contributor License Agreement; your Git commit metadata serves as your electronic signature.


Why "mirroir"? — It's the old French spelling of miroir (mirror). A nod to the author's roots, not a typo.

Source: README.md at commit 81c01b6

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package did not install.

Version history

8
  1. v0.45.0LatestNov 6, 2026
  2. v0.44.0Nov 5, 2026
  3. v0.43.0Nov 4, 2026
  4. v0.42.0Oct 30, 2026
  5. v0.41.0Oct 29, 2026
  6. v0.40.1Oct 5, 2026
  7. v0.40.0Oct 4, 2026
  8. v0.39.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts