Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Drive iOS Simulators, iPhones, Android devices and macOS apps: UI snapshots, live viewer, recording.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"sim-mirror": {
"command": "uvx",
"args": [
"sim-mirror",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add sim-mirror -- uvx sim-mirror mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"sim-mirror": {
"command": "uvx",
"args": [
"sim-mirror",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"sim-mirror": {
"type": "stdio",
"command": "uvx",
"args": [
"sim-mirror",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 AndrewKochulab 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(3.0.1)于5天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Aiterm MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Persistent terminals and one launcher for Claude, Codex, Grok, Cursor, and Antigravity harnesses.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Mirror and drive iOS Simulators, real iPhones and Android devices from Claude Code, CLI agents and the browser.
*A real session, sped up four times. The whole recording runs 1m 39s.*
A live iOS Simulator -- or your own iPhone, over its cable, or an Android emulator or phone -- in any browser tab or web page, an animated cursor that shows exactly what your AI agent is about to tap, and token-efficient UI snapshots so agents read the screen as compact text instead of screenshots. Record any screen as an MP4 or a GIF for a pull request. Works with Claude Code, Codex, Cursor and any other MCP client.
Status: 3.0. The agent tools, the viewer, the protocol and the embedding API are stable, and a check holds every
release to what SimMirror promises not to break. 2.0 brought real iPhones and iPads beside the
simulators -- live over the cable, driven through WebDriverAgent -- and records any screen as an MP4 or a GIF. 2.1
reads and touches apps turned to landscape, keeps taps off what a tab bar covers, builds the worktree the agent works
in, and adds observe mode for walkthroughs on accounts an agent must not change. 2.2 adds Android emulators and
phones, with the same viewer, cursor and tools. 2.3 attaches a real device again by itself once a pulled cable is
back, tells an agent why it cannot touch one, and checks one before a run with
sim_device health. 2.4 leaves a
phone a person took back alone, records as long as it ran, reads long screens without locking WebDriverAgent up, waits
for exact words, and lets one agent at a time drive a real device. 2.5 adds concise agent workflow skills and
reliable tool outcomes. 2.6 records at 30, 60 or 120 frames a second, at a real device's own width, says when a
recording stutters, crops one to a region, keeps refs through a selection change, and guards switches in observe
mode. 3.0 adds macOS apps -- one app and window at a time, captured and driven from inside the app, never the
person's pointer or keyboard -- and a CEF host adapter that lets a Chromium Embedded app be read and driven fully,
in the background. It removes nothing 1.x or 2.x promised.
web component, with touch, scrolling, typing, hardware buttons and light and dark mode.Claude Code, with the plugin (tools, a skill that teaches snapshot-first use, and /sim-mirror:open):
/plugin marketplace add AndrewKochulab/sim-mirror
/plugin install sim-mirror@sim-mirror
Any MCP client, as a stdio server:
claude mcp add sim-mirror -- uvx --from sim-mirror==3.0.1 sim-mirror mcp
Configurations for Codex, Cursor and other clients. The plugin includes four workflow skills; the release also packages them for Codex and Cursor.
The command, for sim-mirror open, doctor and the rest:
uv tool install sim-mirror==3.0.1
brew install andrewkochulab/tap/sim-mirror
The viewer library, for your own pages: npm install @andrewkochulab/sim-mirror (npm). SimMirror itself is on PyPI and in a Homebrew tap.
Requirements: an Apple Silicon Mac, Xcode 26 or later, and uv or Homebrew. Nothing else: SimMirror drives a simulator with its own helper, which comes in the package. A real iPhone needs Developer Mode, and an Apple development team to be touched. Details in Installation.
sim-mirror doctor # check this Mac, ending with a real tap on a simulator
sim-mirror open # this project's simulator, live in a browser tab
Then ask your agent:
Open Settings → General → About and tell me which iOS version this simulator runs. Use sim_snapshot rather than
screenshots.
With an iPhone plugged in, unlocked and in Developer Mode:
Switch to my iPhone, build and run the app on it, walk through sign-up and record it as a GIF.
The first time, press Set up touch in the viewer: it builds WebDriverAgent with your project's own signing team.
Getting started explains what happens along the way.
Live viewer. H.264 through WebCodecs where the page can decode it, JPEG otherwise, negotiated per connection. Touch, drag, scroll, typing and paste, Home and Lock, light and dark, and a device picker. It reconnects by itself after a blip and says plainly when the simulator is off.
Agent cursor. Every agent gesture -- tap, long press, swipe, drag, typing -- reaches the viewer before it lands, and the viewer's own pointer glides there first (agent.cursor_lead_ms). Never the Mac's pointer.
Screen understanding. A snapshot is a few lines -- e2 button "General" (201,319) -- with refs that stay with their elements across scrolls, a digest, and diffs. sim_act plays up to 20 steps in one call and waits for text, its absence, or the screen to settle -- past a spinner or a pulsing dot that never stops. An app turned to landscape is read and touched in its own points, sim_device rotate turns a simulator, and a tap on what a tab bar, a toolbar or the keyboard covers is refused with how to reach it. See Screen understanding.
Observe mode. For a walkthrough on an account the agent must not change, agent.observe refuses a tap on what reads like Delete, Save, Send or Sign out -- in English and a dozen other languages, or styled destructive by its app -- unless the call confirms it. See Security.
Reading pixels. A screen whose accessibility says nothing -- a game, a canvas, an app still loading -- reads as the text macOS's Vision finds in it, with refs to tap and text to wait for, and the viewer can outline what was read (perception.ocr). See Read from pixels.
App SDK. An app under development can link SimMirrorKit, a small Swift package, and call SimMirror.start(): in a Debug build on the simulator it shares its own UIKit and SwiftUI views, so an icon-only button, a card with a tap gesture or a hand-drawn control reads by name, and .simMirror("Settings") names a SwiftUI view. Optional, and nothing of it is in a Release build. See The app SDK.
Real devices. A cabled iPhone or iPad shows up beside the simulators, and an agent can switch to it (sim_device list and choose): its live screen over the cable; its apps, logs, look and location through Xcode's devicectl; and touching, typing and its element tree through WebDriverAgent, set up once with a click and signed by your project's own team -- a tap lands in about a third of a second. It is reached only over the cable, and what SimMirror changes on it is put back when it is let go. See Real devices.
Android. Android emulators and phones sit beside the simulators, with the same viewer, cursor and tools: adb lists, starts and drives them, scrcpy's server -- set up once with a click -- shows the screen live, UI Automator reads it for snapshots, and sim_build_run and sim_test build a Gradle project with its own wrapper. A phone is never started or shut down, and what SimMirror changes on it is put back. See Android.
Recording. The viewer's Record button, sim_record or sim-mirror record keep a device's screen as an MP4, a GIF or both, with each touch drawn where it landed and a 9:41 status bar, and preset: "pr" keeps one small enough for a pull request. See Recording.
Connectors. SimMirror's own native helper gives full control with nothing to install; idb_companion still can, and the simctl connector mirrors the screen view-only when neither is there, and says why. auto uses the fastest that works and falls back when one fails. More connectors plug in through an entry point. See Connectors.
Embedding. An iframe with a one-shot ticket, the element themed with CSS custom properties, or SimMirror inside a Python application with its own sign-in.
Settings panel. sim-mirror open --settings puts every setting a click away in the viewer, a tab per section, saved for one project or all of them and applied before it says so. Settings that decide what runs or who may reach the daemon wait for a code from sim-mirror settings confirm. See The settings panel.
Doctor. Checks Xcode, its Simulator frameworks, runtimes, the native helper and idb_companion, Device Hub and the desktop session, the text reader and an app's shared hierarchy, then proves a tap reaches a simulator. See the doctor.
Security. Loopback only, a Host allowlist, exact Origin checks, CORS and framing only for origins you list, hashed scoped tokens, and one-shot codes in URL fragments. See Security.
Build and test. sim_build_run and sim_test build with xcodebuild for the agent's simulator, install and launch, and answer with only what failed and where -- each failing test named so it can be run again alone, and on another simulator when asked -- and with the folder, branch and commit they built. They build the git worktree the agent works in, with the configuration its scheme runs. Off by default, since they run commands: `sim-mirror c
只显示了开头部分;其余内容请在仓库中阅读