Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Drive iOS Simulators, iPhones, Android devices and macOS apps: UI snapshots, live viewer, recording.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"sim-mirror": {
"command": "uvx",
"args": [
"sim-mirror",
"mcp"
]
}
}
}Führe das in deinem Terminal aus
claude mcp add sim-mirror -- uvx sim-mirror mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"sim-mirror": {
"command": "uvx",
"args": [
"sim-mirror",
"mcp"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"sim-mirror": {
"type": "stdio",
"command": "uvx",
"args": [
"sim-mirror",
"mcp"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto AndrewKochulab bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (3.0.1) kam vor 4 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Python (uv) auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Detailing Manager
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
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.
Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
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
Nur der Anfang wird gezeigt; den Rest findest du im Repo