Mirroir MCP
概览
作者提供的说明(英文原文)
Drive a stock iPhone via iPhone Mirroring: no Developer Mode, Xcode or WDA. LLM-free skill replay.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查;尚未扫描代码
- 使用情况i起步阶段↓ 1988/周 · ★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在你的电脑上运行
- 传输方式: stdio
- 分类: 搜索与 AI 记忆
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 1 项
- 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
- 注册中心没有列出需要填写的密钥。
你需要
- npm已安装 Node.js(用于 npx 命令)
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"mirroir": {
"command": "npx",
"args": [
"-y",
"mirroir-mcp"
]
}
}
}在终端中运行这条命令
claude mcp add mirroir -- npx -y mirroir-mcp或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"mirroir": {
"command": "npx",
"args": [
"-y",
"mirroir-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"mirroir": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mirroir-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 jfarcand 验证,该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与“搜索与 AI 记忆”中的其他服务器比较i
- 星标数多于此分类中其他 5747 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5747 个服务器的 92% 更新
- 基础检查结果等于或优于此分类中其他 5747 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Mirroir MCP 安全吗?
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(0.45.0)于3天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
有什么可以替代它?
同一分类中有:Context7, Codebase Memory, Exa
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
mirroir-mcp
Let your agent use your real iPhone, then replay what it did without an LLM.
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, …):
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:
npx -y mirroir-mcp install # or: brew tap jfarcand/tap && brew install mirroir-mcp
npx -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
test@example.com / 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_skillexplores 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-runis 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-runhas 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.
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
| mirroir | phone-harness | mobile-mcp | Appium | |
|---|---|---|---|---|
| Physical iPhone, no Developer Mode or signing | Yes — stock phone via iPhone Mirroring | Yes — stock phone via iPhone Mirroring | USB-connected, trusted device (see its README) | No — WebDriverAgent via Xcode, Developer Mode |
| App Store apps you can't build | Yes | Yes | Yes | Yes, on a provisioned device |
| Your own iPhone from any MCP client | Yes | No — its MCP server is cloud-only; local phones use its CLI | Yes | Through the separate appium-mcp |
| Replay without an LLM | Yes — compiled skills, mirroir test | Python scripts you write; no recorder or compiled replay | No — the agent drives every run | Yes — test code |
| Distinct drift verdict | Yes — DRIFT, exit 65 | No | No | No — pass / fail |
| One scenario across iPhone + web + HTTP | Yes — mirroir-run | No | No | Via your own test code |
| Android | No — an emulator window can be driven only as a generic macOS window | Yes | Yes | Yes |
| iOS Simulator | No | No | Yes | Yes |
| Hosted cloud phones | No | Yes — Phone Harness Cloud | Yes — Mobile Next Cloud | Via 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.
blockedAppskeeps 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: falseturns 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
| Install | Every install path, per-client setup, updating, uninstalling |
| Onboarding | Setup written for the agent: prerequisites, install, doctor, and a read-only proof |
| Tools Reference | All 39 tools, parameters, and input workflows |
| How mirroir sees the screen | The observe, reason, act loop; OCR, icon detection, AI vision |
| Skills, exploration and CI | APP.md, skills, generate_skill, mirroir test, compiled replay, AI diagnosis, patterns |
mirroir-run | Replay across iPhone, web, HTTP and subprocesses; GitHub Actions; Maestro import |
| Games | Shell and scene, the scene: step, game controls |
| CLI Tools | Recorder, doctor, keyboard layout |
| Configuration | All settings: screen intelligence, input timing, exploration, AI providers |
| FAQ | Security, focus stealing, keyboard layouts, embacle/vision mode |
| Security | Threat model, kill switch, and recommendations |
| Privacy | What mirroir reads, sends and stores |
| Permissions | Fail-closed permission model and config file |
| Known Limitations | Focus stealing, keyboard layout gaps, autocorrect |
| Patterns & Skills | Element patterns, screen recipes, APP.md app descriptions, and the detection pipeline |
| Exploring a New App | Step-by-step playbook for onboarding a new app — APP.md, permissions, components, exploration goal |
| YOLO Icon Detection | Recommended YOLO models, CoreML setup, and configuration |
| Compiled Skills | Zero-OCR skill replay |
| Testing | FakeMirroring, integration tests, and CI strategy |
| Web and iOS in one scenario | How mirroir-run hands iOS blocks to mirroir-mcp, and how cross_surface compares a browser with a phone |
| Cross-surface replay | mirroir-run scenario grammar, .mirroir/ plan, SAMPLE.md, judge profiles, CI |
| Troubleshooting | Debug mode and common issues |
| Contributing | How to add tools, commands, and tests |
| Skills Marketplace | Skill 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.