de en es ja ko ru zh

Xcode-Studio-MCP

Name: Xcode-Studio-MCP
Author: kevinswint

by kevinswint

Overview Schema Source Related Servers Discussions Admin

Local

xcode-studio-mcp

Einheitlicher MCP-Server für Xcode + iOS-Simulator – Erstellen, Bereitstellen, Screenshots erstellen und Interaktion mit Ihrer iOS-App über Claude Code, Codex, Cursor oder einen beliebigen MCP-Client.

In Swift geschrieben. Einzelne Binärdatei. Keine Node/Python-Laufzeitumgebung erforderlich.

Warum existiert dieses Projekt?

Heutzutage benötigen Sie 2-3 separate Tools, um den vollständigen iOS-Entwicklungszyklus mit einem KI-Agenten durchzuführen. xcode-studio-mcp kombiniert diese in einem einzigen Tool:

Write code → Build → Deploy to Simulator → Screenshot → Tap/Type → Verify

Tools

Tool	Beschreibung
`xcode_build`	Erstellt ein Xcode-Projekt mit strukturierter Fehlerausgabe (Datei, Zeile, Spalte, Schweregrad, Nachricht)
`xcode_run`	Erstellt und startet eine App im iOS-Simulator
`simulator_screenshot`	Erfasst den Simulator-Bildschirm als PNG-Bild
`simulator_tap`	Tippt auf x,y-Koordinaten auf dem Simulator-Bildschirm
`simulator_type`	Gibt Text in das aktuell fokussierte Feld ein
`simulator_describe`	Ruft den Barrierefreiheitsbaum des aktuellen Bildschirms ab (JSON)

Related MCP server: xcforge

Tool-Parameter

`xcode_build`

Parameter	Erforderlich	Beschreibung
`project_path`	Ja	Pfad zum Xcode-Projektverzeichnis, `.xcodeproj` oder `.xcworkspace`
`scheme`	Nein	Build-Schema (wird automatisch erkannt, falls weggelassen)
`configuration`	Nein	`Debug` (Standard) oder `Release`
`destination`	Nein	Build-Ziel (standardmäßig der gestartete Simulator)

`xcode_run`

Parameter	Erforderlich	Beschreibung
`project_path`	Ja	Pfad zum Xcode-Projekt
`bundle_identifier`	Ja	App-Bundle-ID (z. B. `com.example.MyApp`)
`scheme`	Nein	Build-Schema (automatisch erkannt)
`simulator_udid`	Nein	Ziel-Simulator (standardmäßig der gestartete)

`simulator_screenshot`

Parameter	Erforderlich	Beschreibung
`simulator_udid`	Nein	Ziel-Simulator (standardmäßig der gestartete)

`simulator_tap`

Parameter	Erforderlich	Beschreibung
`x`	Ja	X-Koordinate
`y`	Ja	Y-Koordinate
`duration`	Nein	Haltedauer in Sekunden (für langes Drücken)
`simulator_udid`	Nein	Ziel-Simulator

`simulator_type`

Parameter	Erforderlich	Beschreibung
`text`	Ja	Einzugebender Text
`simulator_udid`	Nein	Ziel-Simulator

`simulator_describe`

Parameter	Erforderlich	Beschreibung
`simulator_udid`	Nein	Ziel-Simulator

Schnellstart

Voraussetzungen

macOS mit installiertem Xcode

Für UI-Interaktions-Tools (tap, type, describe):

brew tap facebook/fb && brew install idb-companion
pip3 install fb-idb

Build

git clone https://github.com/kevinswint/xcode-studio-mcp.git
cd xcode-studio-mcp
swift build -c release

Claude Code konfigurieren

Fügen Sie dies zu Ihren Claude Code MCP-Einstellungen hinzu:

{
  "mcpServers": {
    "xcode-studio-mcp": {
      "command": "/path/to/xcode-studio-mcp/.build/release/XcodeStudioMCP"
    }
  }
}

Beispiel-Workflow

You: Build and run my app at ~/Projects/MyApp
Claude: [calls xcode_build] Build succeeded with 0 errors
        [calls xcode_run] App launched (PID 12345)
        [calls simulator_screenshot] Here's what the app looks like...
        [calls simulator_describe] I can see a "Sign In" button and email/password fields
        [calls simulator_tap] Tapped the email field
        [calls simulator_type] Typed "test@example.com"
        [calls simulator_screenshot] Here's the current state...

Architektur

┌─────────────────────────────┐
│     MCP Protocol Layer      │  stdio transport (Swift MCP SDK)
├─────────────────────────────┤
│   Tool Implementations      │  6 tools, structured error output
├──────────┬──────────────────┤
│ xcodebuild│  simctl  │  idb │  native process calls
│  wrapper  │  wrapper │ CLI  │
└──────────┴──────────┴──────┘

In Swift geschrieben, ohne Abhängigkeiten von Node/Python-Laufzeitumgebungen (idb CLI wird nur für UI-Interaktions-Tools benötigt).

Roadmap

v0.1 (aktuell): Core-Build + Simulator-Tools
v1.0: Semantische UI-Navigation („Tippe auf den Anmelden-Button“), visueller Vergleich, Bearbeitung von Xcode-Projektdateien, zusammengesetzte Operationen, SwiftUI-Vorschau-Erfassung

Mitwirken

Pull Requests sind willkommen. Die Codebasis besteht aus ca. 750 Zeilen Swift, organisiert in Tools, Services und Models.

Lizenz

MIT

Available Tools

6 tools

simulator_describeA

Get the accessibility tree of the current iOS Simulator screen as JSON. Useful for finding UI elements to interact with. Requires idb (pip3 install fb-idb).

Inputs: simulator_udid.

simulator_screenshotA

Capture a screenshot of the iOS Simulator screen. Returns the image as base64-encoded PNG.

Inputs: simulator_udid.

simulator_tapA

Tap at specific coordinates on the iOS Simulator screen. Requires idb (pip3 install fb-idb).

Inputs: x (required), y (required), duration, simulator_udid.

simulator_typeA

Type text into the currently focused field on the iOS Simulator. Requires idb (pip3 install fb-idb).

Inputs: text (required), simulator_udid.

xcode_buildB

Build an Xcode project or workspace. Returns structured diagnostics with file, line, column, severity, and message for each error/warning.

Inputs: project_path (required), configuration, destination, scheme.

xcode_runA

Build an Xcode project and launch the app in the iOS Simulator. Returns build errors if the build fails, or a success message with the launched process ID.

Inputs: bundle_identifier (required), project_path (required), configuration, scheme, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

TDQS

A3.7/5.0

Scored 2026-09-09 19:45 across 6 tools

Disambiguation5/5

Each tool targets a distinct action: building, running, and simulator interactions (screenshot, tap, type, describe) are clearly separated. There is no overlap in purpose, making it easy for an agent to select the correct tool.

Naming Consistency3/5

Tools are grouped into two clear namespaces: 'xcode_' for build/run and 'simulator_' for simulator interactions. However, the same verb 'run' is used for xcode_run (launch app) while the simulator tools use direct action verbs (tap, type, describe). The pattern is readable but not perfectly uniform.

Tool Count5/5

With only 6 tools, the set is well-scoped for core Xcode build/run and simulator interaction workflows. Each tool serves a distinct purpose, and no tool feels redundant or missing at this scale.

Completeness4/5

The set covers building, running, and basic UI interaction (via describe/tap/type). A minor gap is the lack of a tool to terminate the running app, and no way to list available simulators, but agents can work around this for common tasks.

Maintenance

ActivityInactive

ResponsivenessLimited data

Resources

Related MCP Connectors

NoMacB
app.nomac
Cloud iPhones and Macs with Xcode for AI agents: build, run and test iOS apps, use the screen.
CI/CD & DevOps Code Execution Developer Tools
331
https://mcp.nomac.app/mcp
NoMac Simulator
app.nomac
Cloud iPhone Simulators for AI agents: build the Xcode project, read the screen, tap by label, test.
Developer Tools Testing & QA Tools
1
https://mcp.nomac.app/simulator
NoMac Session
app.nomac
The cloud Mac alone, with Xcode, for AI agents: run commands, build and test, use the screen.
Cloud Platforms Command Line Developer Tools
1
https://mcp.nomac.app/session
AgentCloud — Hosted iOS Simulator MCP
so.agentcloud
Build, run, and inspect iOS apps in disposable hosted Simulators from cloud coding agents.
Code Execution Testing & QA Tools
1
https://api.agentcloud.so/mcp

Related MCP Servers

SilbercueSwiftofficial
Developer Tools Testing & QA Tools
Silbercue
A
license
Not graded
quality
B
maintenance
High-performance MCP server for iOS development and test automation. Gives AI coding assistants direct access to iOS simulators with sub-20ms screenshots, UI interaction, building, testing, and an intelligent operator mode.
Updated 3 months ago (2026-08-27 10:18 UTC)
10
MIT
xcforge
Developer Tools Testing & QA Tools
justinthevoid
A
license
Not graded
quality
B
maintenance
MCP server and CLI for iOS development — build, test, automate, and diagnose from any AI agent or terminal.
Updated a month ago (2026-10-10 18:40 UTC)
2
MIT
ios-sim-mcp
Testing & QA Tools Developer Tools
artmamedov
A
license
Not graded
quality
D
maintenance
A Model Context Protocol (MCP) server for iOS Simulator automation. Enables AI assistants to visually interact with iOS apps running in the simulator.
Updated 10 months ago (2026-01-18 22:55 UTC)
36 npm
1
MIT
xcode-pilot-mcp
Developer Tools CI/CD & DevOps Testing & QA Tools
sitharaj88
A
license
B
quality
C
maintenance
A comprehensive MCP server for iOS/macOS development that gives AI assistants full control over Xcode build, test, simulator management, and app deployment.
Updated 3 months ago (2026-08-17 15:22 UTC)
65
22 npm
2
MIT

Projekt	Was es tut	Unterschied
XcodeBuildMCP	Nur Build + Test	Keine Simulator-UI-Interaktion
mobile-mcp	Plattformübergreifende Simulator-UI	Keine Xcode-Build-Unterstützung
ios-simulator-mcp	Simulator über IDB	Kein Build, hängt für alles von IDB ab