Xcode-Studio-MCP
Unified MCP server for Xcode + iOS Simulator — build, deploy, screenshot, and interact with your iOS app from Claude Code, Cursor, or any MCP client. Built in Swift. Single binary. No Node/Python runtime required.
README
xcode-studio-mcp
Unified MCP server for Xcode + iOS Simulator — build, deploy, screenshot, and interact with your iOS app from Claude Code, Cursor, or any MCP client.
Built in Swift. Single binary. No Node/Python runtime required.
Why This Exists
Today you need 2-3 separate tools to do the full iOS dev loop with an AI agent. xcode-studio-mcp combines them into one:
Write code → Build → Deploy to Simulator → Screenshot → Tap/Type → Verify
Tools
| Tool | Description |
|---|---|
xcode_build |
Build an Xcode project with structured error output (file, line, column, severity, message) |
xcode_run |
Build and launch an app in the iOS Simulator |
simulator_screenshot |
Capture the Simulator screen as a PNG image |
simulator_tap |
Tap at x,y coordinates on the Simulator screen |
simulator_type |
Type text into the currently focused field |
simulator_describe |
Get the accessibility tree of the current screen (JSON) |
Tool Parameters
xcode_build
| Parameter | Required | Description |
|---|---|---|
project_path |
Yes | Path to Xcode project directory, .xcodeproj, or .xcworkspace |
scheme |
No | Build scheme (auto-detected if omitted) |
configuration |
No | Debug (default) or Release |
destination |
No | Build destination (defaults to booted simulator) |
xcode_run
| Parameter | Required | Description |
|---|---|---|
project_path |
Yes | Path to Xcode project |
bundle_identifier |
Yes | App bundle ID (e.g. com.example.MyApp) |
scheme |
No | Build scheme (auto-detected) |
simulator_udid |
No | Target simulator (defaults to booted) |
simulator_screenshot
| Parameter | Required | Description |
|---|---|---|
simulator_udid |
No | Target simulator (defaults to booted) |
simulator_tap
| Parameter | Required | Description |
|---|---|---|
x |
Yes | X coordinate |
y |
Yes | Y coordinate |
duration |
No | Hold duration in seconds (for long press) |
simulator_udid |
No | Target simulator |
simulator_type
| Parameter | Required | Description |
|---|---|---|
text |
Yes | Text to type |
simulator_udid |
No | Target simulator |
simulator_describe
| Parameter | Required | Description |
|---|---|---|
simulator_udid |
No | Target simulator |
Quick Start
Prerequisites
- macOS with Xcode installed
- For UI interaction 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
Configure Claude Code
Add to your Claude Code MCP settings:
{
"mcpServers": {
"xcode-studio-mcp": {
"command": "/path/to/xcode-studio-mcp/.build/release/XcodeStudioMCP"
}
}
}
Example 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...
Architecture
┌─────────────────────────────┐
│ MCP Protocol Layer │ stdio transport (Swift MCP SDK)
├─────────────────────────────┤
│ Tool Implementations │ 6 tools, structured error output
├──────────┬──────────────────┤
│ xcodebuild│ simctl │ idb │ native process calls
│ wrapper │ wrapper │ CLI │
└──────────┴──────────┴──────┘
Built in Swift with zero Node/Python runtime dependencies (idb CLI is only needed for UI interaction tools).
Roadmap
- v0.1 (current): Core build + simulator tools
- v1.0: Semantic UI navigation ("tap the Sign In button"), visual diff, Xcode project file manipulation, compound operations, SwiftUI preview capture
Related Projects
| Project | What It Does | Difference |
|---|---|---|
| XcodeBuildMCP | Build + test only | No simulator UI interaction |
| mobile-mcp | Cross-platform simulator UI | No Xcode build support |
| ios-simulator-mcp | Simulator via IDB | No build, depends on IDB for everything |
xcode-studio-mcp combines build and interact into a single server.
Contributing
PRs welcome. The codebase is ~750 lines of Swift organized into Tools, Services, and Models.
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。