Xcodebuildmcp
- 1 installs
- 6.2k repo stars
- Updated August 4, 2026
- getsentry/xcodebuildmcp
xcodebuildmcp skill documents Official skill for XcodeBuildMCP.
About
xcodebuildmcp skill documents Official skill for XcodeBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).. name: xcodebuildmcp description: Official skill for XcodeBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
- Official skill for XcodeBuildMCP.
- Platform-specific setup patterns for xcodebuildmcp.
- Evidence-backed steps from upstream SKILL.md.
- When-to-use criteria for xcodebuildmcp versus alternatives.
Xcodebuildmcp by the numbers
- 1 all-time installs (skills.sh)
- Ranked #982 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
xcodebuildmcp capabilities & compatibility
- Capabilities
- xcodebuildmcp quick start · xcodebuildmcp when to use guidance · xcodebuildmcp integration patterns
- Works with
- sentry
- Use cases
- code review
What xcodebuildmcp says it does
Use XcodeBuildMCP tools instead of raw `xcodebuild`, `xcrun`, or `simctl`.
Session defaults: Configure project, scheme, simulator, and device defaults to avoid repetitive parameters
npx skills add https://github.com/getsentry/xcodebuildmcp --skill xcodebuildmcpAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 6.2k |
| Last updated | August 4, 2026 |
| Repository | getsentry/xcodebuildmcp ↗ |
How do I use xcodebuildmcp correctly?
Official skill for XcodeBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
Who is it for?
Teams implementing xcodebuildmcp workflows from the catalog.
Skip if: Skip when requirements clearly match a different specialized stack.
When should I use this skill?
User asks about xcodebuildmcp, official skill for xcodebuildmcp. use when doing ios/macos/watchos/tvos/visionos work (bui.
What you get
Working xcodebuildmcp setup with validated configuration and next steps.
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
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kFAQ
What does xcodebuildmcp do?
xcodebuildmcp skill documents Official skill for XcodeBuildMCP.
When should I use xcodebuildmcp?
User asks about xcodebuildmcp, official skill for xcodebuildmcp. use when doing ios/macos/watchos/tvos/visionos work (bui.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.