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는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 GitHub 계정 AndrewKochulab 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(3.0.1)은 4일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Python (uv)도 있어야 해요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, SuperCollider
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ 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.
Make sound with SuperCollider: synths, drums, chords, melodies and soundscapes over OSC.
제작자의 저장소에서 쓰인 그대로 가져왔어요. 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
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요