xcodebuildmcp▌
cameroncooke/xcodebuildmcp · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Complete iOS/macOS/watchOS/tvOS/visionOS build, test, debug, and UI automation through Xcode without raw command-line tools.
- ›Simulator workflows: build, run, test, install, and launch apps on iOS simulators with state management (boot, erase, location, appearance)
- ›Device and macOS workflows: build, test, install, and launch on physical devices with code signing, plus native macOS app support
- ›Debugging and inspection: LLDB attachment with breakpoints, stack traces, variable inspection
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://github.com/getsentry/XcodeBuildMCP/blob/main/docs/CONFIGURATION.md 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.
How to use xcodebuildmcp on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add xcodebuildmcp
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches xcodebuildmcp from GitHub repository cameroncooke/xcodebuildmcp and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate xcodebuildmcp. Access the skill through slash commands (e.g., /xcodebuildmcp) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★58 reviews- ★★★★★Ganesh Mohane· Dec 28, 2024
xcodebuildmcp reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Aanya Mehta· Dec 20, 2024
Solid pick for teams standardizing on skills: xcodebuildmcp is focused, and the summary matches what you get after install.
- ★★★★★Luis Harris· Dec 8, 2024
We added xcodebuildmcp from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Aarav White· Dec 4, 2024
Useful defaults in xcodebuildmcp — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Alexander Diallo· Nov 27, 2024
Keeps context tight: xcodebuildmcp is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Jin Perez· Nov 23, 2024
xcodebuildmcp has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Emma Park· Nov 11, 2024
I recommend xcodebuildmcp for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Luis Abbas· Oct 26, 2024
Useful defaults in xcodebuildmcp — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Luis Huang· Oct 18, 2024
xcodebuildmcp is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Aanya Menon· Oct 14, 2024
Solid pick for teams standardizing on skills: xcodebuildmcp is focused, and the summary matches what you get after install.
showing 1-10 of 58