Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Drive the iOS Simulator via semantic accessibility-tree snapshots. Sub-200ms, no WebDriverAgent.
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": {
"ios-sim": {
"command": "npx",
"args": [
"-y",
"ios-sim-mcp"
]
}
}
}Führe das in deinem Terminal aus
claude mcp add ios-sim -- npx -y ios-sim-mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"ios-sim": {
"command": "npx",
"args": [
"-y",
"ios-sim-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": {
"ios-sim": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ios-sim-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 rmathew1973 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 (0.4.2) kam vor 6 Monaten in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Node.js auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Signoff
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.
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
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.
An MCP server that drives the iOS Simulator the way Chrome's DevTools MCP drives a browser: semantic accessibility-tree snapshots with stable element refs, sub-200ms operations, and no screenshot-and-eyeball-coordinates loops.
Built because every existing iOS-simulator automation tool either crawls (Appium, screenshot-based agents) or requires pre-written scripts. This one lets an LLM drive a simulator interactively — find an element by label or ID, tap it by ref, wait for the UI to settle, repeat — at roughly the speed a human would.
Most existing iOS-sim MCPs work by taking a screenshot, asking the model to identify coordinates, then tapping pixels. That's slow (image bytes in context), expensive (vision tokens), and fragile (any layout shift breaks it).
iOS apps already expose a structured accessibility tree — the same one VoiceOver uses. If you query that tree, you get every interactive element with its label, role, AX identifier, frame, and enabled state. You can find what you want semantically, refer to it by a stable ref, and act on it directly. That's what Chrome MCP does for the DOM, and it's what this does for UIView hierarchies in the iOS Simulator.
Three layers, two shipping today:
| Layer | Status | Tech | What it gives you |
|---|---|---|---|
| 1 — AX tree + actions | ✅ shipping | idb (Facebook's CoreSimulator bridge) | snapshot, find, tap, type, swipe, scroll, launch, screenshot — all ~100ms |
| 2a — Dylib proof-of-life | ✅ shipping | DYLD_INSERT_LIBRARIES via SIMCTL_CHILD_* | constructor runs in the target app before main(); logs lifecycle via os_log |
| 2b — In-process RPC | ✅ shipping | Unix socket + JSON-Lines | round-trip into a running app at ~1ms per call |
| 2c — View introspection | ✅ shipping | Main-thread UIView walk | view_tree, view_hit_test — class hierarchy, frames, responder chains, VC annotations |
| 2d — Network interception | ✅ shipping | URLProtocol + URLSessionConfiguration swizzle | capture every HTTP request/response (headers, bodies, timing) inside the app — no cert install, no mitmproxy |
| 2e — JS eval | ✅ shipping | JSContext + JSExport bridges | eval_js({code}) with app / key_window() / defaults / pasteboard / bundle / process / view-finder helpers — Chrome's Runtime.evaluate equivalent |
| 2f — Network stubbing | ✅ shipping | Same URLProtocol, synthesized response | register canned responses by URL substring + optional method; supports custom status/headers/body + delay_ms for slow-network simulation |
| 3 — System logs | ✅ shipping | xcrun simctl spawn log stream | streaming os_log into a 5000-line ring buffer |
idb talks directly to CoreSimulator's private framework — no WebDriverAgent, no HTTP hop into the simulator process — which is why the per-call latency is closer to a local subprocess than to a network round trip.
idb (brew tap facebook/fb && brew install idb-companion && pipx install fb-idb)curl -fsSL https://bun.sh/install | bash)xcrun simctl boot or open it in Xcode)# Register with Claude Code, one line:
claude mcp add -s user ios-sim -- npx -y ios-sim-mcp
npx will fetch the package on first run. Verify:
claude mcp list | grep ios-sim # ios-sim: ... ✓ Connected
Layer 2 dylib ships prebuilt as a universal binary (arm64 + x86_64) — works on both Apple Silicon and Intel Macs out of the box.
git clone https://github.com/rmathew1973/ios-sim-mcp.git
cd ios-sim-mcp bun install ./dylib/build.sh # builds the Layer 2 dylib (only needed if you'll use inject:true)
Then register:
# Prefer the absolute bun path — clients with a minimal PATH fail on bare `bun`:
claude mcp add -s user ios-sim -- "$HOME/.bun/bin/bun" run "$(pwd)/src/server.ts"
Grok MCP spawn PATH is often just /usr/bin:/bin. Bare bun fails with:
Failed to spawn MCP server 'ios-sim': No such file or directory (os error 2)
Use the absolute bun binary in ~/.grok/config.toml:
[mcp_servers.ios-sim]
command = "/Users/YOU/.bun/bin/bun" args = ["run", "/Users/YOU/Projects/ios-sim-mcp/src/server.ts"] enabled = true startup_timeout_sec = 60
Or:
grok mcp add ios-sim -- "$HOME/.bun/bin/bun" run "$HOME/Projects/ios-sim-mcp/src/server.ts"
Restart the Grok session after changing MCP config. Verify: grok mcp list should show ios-sim connected (not failed).
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": { "ios-sim": { "command": "npx", "args": ["-y", "ios-sim-mcp"] } } }
Or, if installed from source, point at the local path:
{
"mcpServers": { "ios-sim": { "command": "/Users/YOU/.bun/bin/bun", "args": ["run", "/absolute/path/to/ios-sim-mcp/src/server.ts"] } } }
Quit and reopen Claude Desktop.
It's a standard stdio MCP server. Run bun run src/server.ts and pipe JSON-RPC. See test/smoke.ts for a working client example.
| Tool | What it does |
|---|---|
list_simulators | List simulators with UDID, state, OS version |
use_simulator | Pick a specific UDID (auto-selected if only one is booted) |
snapshot | Capture the AX tree, assign refs e1..eN, return compact text rendering. Filters: interactive (default), actionable, all |
find | Search the snapshot by id (AXUniqueId), label, labelContains, role, actionable |
tap | Tap by {ref}, {id}, or {x,y}. Optional duration makes it a long-press |
type_text | Type into the focused field. Optional {ref} or {id} taps-then-types. Auto-routes through paste when the dylib is loaded for byte-perfect input — no iOS autocorrect, no first-letter capitalization. via: "keystroke" forces the typing path; via: "paste" forces the paste path |
paste_text | Byte-perfect text via UIPasteboard + first-responder paste:. Requires the dylib injected. The right answer for emails, passwords, OAuth tokens, anything case-sensitive |
view_tree | Walk the running app's UIView hierarchy on the main thread. Reports class names, frames in window coords, alpha/hidden/interactive, text content, and annotates view-controller boundaries. Strictly richer than snapshot — sees custom-drawn views, transient overlays, SwiftUI internals. Filter by class_filter / ax_id_contains / text_contains. Requires dylib injected |
view_hit_test | "What view actually receives a tap at (x,y)?" Returns the topmost view plus the full responder chain up to UIApplication. The right debugging tool when a tap isn't doing what you expect. Requires dylib injected |
network_start / network_stop / network_status | Install/remove an URLProtocol interceptor + swizzle URLSessionConfiguration so every URLSession-based HTTP request flowing through the app is recorded. Options: max_records, max_body_bytes, filter_url_substring. Requires dylib injected |
network_tail | Return the most recent N captured records. Default: one line per request (id, method, status, timing, sizes, URL). full=true includes headers + body previews inline. Page forward via since_id |
network_get_body | Fetch the full request or response body (up to max_body_bytes, default 256KB) for a specific record id. Returns base64 + UTF-8 decode for text bodies |
network_clear | Drop the ring buffer and all retained bodies |
network_self_test | Fire an HTTP request from inside the app to verify the capture path end-to-end |
network_stub / network_stubs / network_unstub / network_unstub_all | Register canned HTTP responses by URL substring (+ optional method). Synthesizes status/headers/body without forwarding; delay_ms simulates slow networks. Stubbed requests still appear in network_tail with stubbed:true |
eval_js | Run arbitrary JavaScript in a persistent JSContext inside the injected app. Bridged globals: app, key_window(), all_windows(), defaults, pasteboard, bundle, process, notif_center, first_responder(), find_view_by_ax_id, find_view_by_class, find_vc_by_class, post_notification, cls, log. State persists across calls. Requires dylib injected |
eval_js_reset | Drop the JSContext and rebuild bridges on next eval — forgets your defined vars/fns |
key | Press a key by name (RETURN, ESC, DELETE, TAB, SPACE, F1–F12, arrows) or raw HID code |
button | Hardware button: HOME, LOCK, SIDE_BUTTON, SIRI, APPLE_PAY |
swipe | Swipe between two refs/ids/points. Optional duration and delta |
scroll | Reader-perspective scroll: down reveals content below. Optional anchor element |
launch_app | Launch by bundle id. Optional foreground_if_running terminates first |
terminate_app | Terminate by bundle id |
screenshot | PNG to disk or inline. Use sparingly — the AX tree is faster and richer |
await_quiescent | Block until the AX-tree hash is identical for stable_ms (default 250) or timeout_ms (default 5000). Use after launches and navigation instead of sleep |
log_start / log_tail / log_stop / log_clear | Stream os_log into a 5000-line ring buffer. Filter by bundle_id substring, level, or NSPredicate |
> snapshot
e3 Button "Apple Account" #com.apple.settings.primaryAppleAccount @(201,213) e5 Button "General" #com.apple.settings.general @(201,406) e6 Button "Accessibility" #com.apple.settings.accessibility @(201,458) e14 TextField "Search" ="Search" @(201,822) ...
tap {id: "com.apple.settings.general"}
tapped e5/com.apple.settings.general
await_quiescent {stable_ms: 250}
stable hash=8326196f25c8 samples=4 elapsed=1731ms
snapshot
e2 Button "Settings" #BackButton @(38,84) e6 Button "About" #About @(201,418) ...
type_text {ref: "e14", text: "wifi"}
typed 4 chars into e14
Measured on iPhone 17 Pro / iOS 26.5 / M-series Mac:
snapshot: 127–190 mstap: 100 msfind: <1 ms (in-memory against cached snapshot)await_quiescent: 400 ms – 2.5 s (real UI settle time)tap, swipe, type_text, launch_app, button, key) invalidates the cache so stale refs can't survive a state change. find and ref resolution will tell you to re-snapshot rather than acting on old data.e5 in v=10 is not the same element as e5 in v=11. AXUniqueIds (the iOS accessibilityIdentifier) are stable across snapshots and are the preferred way to target a control across UI changes.launch_app, idb returns just the AXApplication root with no children. A naive hash-stability check would return instantly with an empty tree. The implementation resets the stability timer whenever it sees a degenerate snapshot.down means "see what's below" (finger drags up), matching mouse-wheel/page-down conventions, not finger-direction. Default 0.4s gesture duration prevents iOS from interpreting the release point as a tap on the underlying element.This MCP is fastest and most reliable when interactive controls have accessibilityIdentifier set:
Button("Sign In") { ... }
.accessibilityIdentifier("login_submit_button")
Then tap({id: "login_submit_button"})
Nur der Anfang wird gezeigt; den Rest findest du im Repo