xcodebuildmcp
Automates Xcode build, test, and device management tasks via XcodeBuildMCP.
Install
mkdir -p .claude/skills/xcodebuildmcp && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3761" && unzip -o skill.zip -d .claude/skills/xcodebuildmcp && rm skill.zipInstalls to .claude/skills/xcodebuildmcp
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Official skill for XcodeBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).Key capabilities
- →Configure project and simulator defaults
- →Build and test apps on simulators and devices
- →Stream logs from simulators and devices
- →Attach LLDB debugger
- →Perform UI automation tasks
How it works
It interfaces with XcodeBuildMCP to manage build cycles and simulator states, requiring a session context to be established before execution.
Inputs & outputs
When to use xcodebuildmcp
- →Running automated UI tests on a simulator
- →Capturing device logs for debugging
- →Building and deploying to physical devices
- →Configuring project schemes and build settings
About this skill
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.
When not to use it
- →Directly using raw xcodebuild commands
- →Speculative project discovery
Prerequisites
Limitations
- →Requires explicit workflow configuration for advanced features
- →Simulator tools are the only default-enabled features
How it compares
It abstracts raw CLI tools into a managed session, preventing repetitive parameter entry and handling simulator state automatically.
Compared to similar skills
xcodebuildmcp side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| xcodebuildmcp (this skill) | 24 | 3mo | No flags | Advanced |
| ios-simulator-skill | 27 | 2mo | Review | Advanced |
| build-iphone-apps | 14 | 8mo | Review | Advanced |
| developing-ios-apps | 1 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by cameroncooke
View all by cameroncooke →You might also like
ios-simulator-skill
conorluddy
21 production-ready scripts for iOS app testing, building, and automation. Provides semantic UI navigation, build automation, accessibility testing, and simulator lifecycle management. Optimized for AI agents with minimal token output.
build-iphone-apps
glittercowboy
Build professional native iPhone apps in Swift with SwiftUI and UIKit. Full lifecycle - build, debug, test, optimize, ship. CLI-only, no Xcode. Targets iOS 26 with iOS 18 compatibility.
developing-ios-apps
daymade
Develops iOS applications with XcodeGen, SwiftUI, and SPM. Triggers on XcodeGen project.yml configuration, SPM dependency issues, device deployment problems, code signing errors, camera/AVFoundation debugging, iOS version compatibility, or "Library not loaded @rpath" framework errors. Use when building iOS apps, fixing Xcode build failures, or deploying to real devices.
ios-testing-validation
AriDevari
Validate iOS changes in Naviari_IOS. Use when: running narrow xcodebuild checks, planning XCTest or manual verification, validating visually sensitive SwiftUI work, checking reusable-view regressions, or recording slice-level evidence after iOS edits.
qa
dutradotdev
>
build-macos-apps
glittercowboy
Build professional native macOS apps in Swift with SwiftUI and AppKit. Full lifecycle - build, debug, test, optimize, ship. CLI-only, no Xcode.