Xcodebuildmcp
- 770 installs
- 6.2k repo stars
- Updated August 4, 2026
- cameroncooke/xcodebuildmcp
xcodebuildmcp is the official Claude Code skill for XcodeBuildMCP that runs Apple platform build, test, simulator, device, debug, and UI automation commands through structured MCP tools instead of raw xcodebuild or simct
About
xcodebuildmcp is the official skill for XcodeBuildMCP from cameroncooke/xcodebuildmcp, instructing agents to use MCP tools instead of raw xcodebuild, xcrun, or simctl. Capabilities include session defaults for project, scheme, simulator, and device; project discovery to find workspaces and list schemes; simulator workflows to build, run, test, install, and launch apps plus manage boot, erase, location, and appearance; and physical device build, test, install, and launch flows. Developers reach for xcodebuildmcp when doing iOS, macOS, watchOS, tvOS, or visionOS work and want repeatable agent-driven Xcode operations with fewer repetitive CLI parameters.
- Replaces raw xcodebuild, xcrun, and simctl with reliable MCP tools
- Session defaults for project, scheme, simulator, and device to eliminate repetition
- Full simulator workflows: build, run, test, install, launch, boot, erase, location, appearance
- Physical device workflows with code signing
- LLDB debugging, log capture, UI automation with taps, swipes, screenshots, and view hierarchy inspection
Xcodebuildmcp by the numbers
- 770 all-time installs (skills.sh)
- Ranked #250 of 1,039 Mobile Development skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cameroncooke/xcodebuildmcp --skill xcodebuildmcpAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 770 |
|---|---|
| repo stars | ★ 6.2k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | cameroncooke/xcodebuildmcp ↗ |
How do agents run Xcode builds and simulator tests?
Run Xcode build, test, simulator, device, debug, and UI automation commands through a structured agent interface instead of raw terminal calls.
Who is it for?
Apple platform developers using coding agents who need structured XcodeBuildMCP commands for build, test, simulator, and device workflows.
Skip if: Android, Flutter-only, or web developers without Xcode projects or Apple simulator and device targets.
When should I use this skill?
A developer works on iOS, macOS, watchOS, tvOS, or visionOS build, test, simulator, device, debug, or UI automation tasks.
What you get
Built app binaries, simulator or device installs, test run results, and UI automation sessions via XcodeBuildMCP.
- Built app binaries
- Simulator and device test results
Files
XcodeBuildMCP
Use XcodeBuildMCP tools instead of raw xcodebuild, xcrun, or simctl.
Capabilities:
- Session defaults: Configure project, scheme, simulator, and device defaults to avoid repetitive parameters
- Project discovery: Find Xcode projects/workspaces, list schemes, inspect build settings
- Simulator workflows: Build, run, test, install, and launch apps on iOS simulators; manage simulator state (boot, erase, location, appearance)
- Device workflows: Build, test, install, and launch apps on physical devices with code signing
- macOS workflows: Build, run, and test macOS applications
- Log capture: Stream and capture logs from simulators and devices
- LLDB debugging: Attach debugger, set breakpoints, inspect stack traces and variables, execute LLDB commands
- UI automation: Capture screenshots, inspect view hierarchy with coordinates, perform taps/swipes/gestures, type text, press hardware buttons
- SwiftPM: Build, run, test, and manage Swift Package Manager projects
- Project scaffolding: Generate new iOS/macOS project templates
Only simulator workflow tools are enabled by default. If capabilities like device, macOS, debugging, or UI automation are not available, the user must configure XcodeBuildMCP to enable them. See https://xcodebuildmcp.com/docs/configuration for workflow configuration.
Step 1: Establish Session Context
- Call
session_show_defaultsbefore the first build/run/test action in a session. - Use
discover_projsonly when defaults show missing or incorrect project/workspace context. - Do not run discovery speculatively or in parallel with
session_show_defaults. - For simulator run intent, prefer the combined build-and-run tool instead of separate build then run calls.
- Do not chain build-only then build-and-run unless the user explicitly requests both.
Step 2: Understand Workflow-Scoped Tool Availability
- Not all tools are enabled by default; tool availability depends on enabled workflows.
- If a tool is expected but missing, check enabled workflows first.
- Update enabled workflows in
.xcodebuildmcp/config.yaml, then ask user to reload/restart the session to surface refreshes.
Step 3: Report Context Clearly
- Return the active defaults context used for execution (project/workspace, scheme, simulator/device).
- For failures, include the exact failing step and the next actionable command/tool call.
Related skills
Xcode Project SetupAutomatically create and configure a new Xcode project with Swift Package Manager dependencies for iOS or macOS agent projects.74.7k392
Expo Tailwind SetupInstantly configure Tailwind CSS v4 with NativeWind v5 and react-native-css inside an Expo project for universal styling.46.7k2.3kExpo Dev ClientCreate custom development clients for Expo React Native apps that need native modules or Apple-specific targets.45.9k2.3k
Swiftui Expert SkillGet expert guidance when writing, reviewing, or refactoring SwiftUI views, state, performance, and modern iOS/macOS APIs.27.6k3.3k
Flutter Apply Architecture Best PracticesEnforce clean layered architecture when creating or refactoring a Flutter mobile application.25.4k2.7kExpo ModuleCreate custom config plugins that safely modify native Android and iOS projects generated by Expo prebuild.25k2.3kFAQ
What platforms does xcodebuildmcp support?
xcodebuildmcp supports iOS, macOS, watchOS, tvOS, and visionOS work including build, test, run, debug, log, and UI automation. The official skill routes agents to XcodeBuildMCP tools instead of raw terminal commands.
Why use xcodebuildmcp instead of xcodebuild directly?
xcodebuildmcp uses XcodeBuildMCP structured tools with session defaults for project, scheme, simulator, and device. Agents avoid repetitive xcodebuild, xcrun, and simctl parameters while running build, test, and launch workflows.
Is Xcodebuildmcp safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.