Xcodebuildmcp
Drive Apple-platform build, test, simulator, device, LLDB debug, and UI automation through XcodeBuildMCP instead of raw xcodebuild and simctl.
Overview
XcodeBuildMCP is an agent skill for the Build phase that routes iOS, macOS, watchOS, tvOS, and visionOS build, test, run, debug, and UI automation through XcodeBuildMCP tools.
Install
npx skills add https://github.com/cameroncooke/xcodebuildmcp --skill xcodebuildmcpWhat is this skill?
- Official XcodeBuildMCP skill—prefer MCP tools over raw xcodebuild, xcrun, simctl
- Session defaults for project, scheme, simulator, and device to cut repetitive parameters
- Simulator and physical device workflows: build, test, install, launch, logs
- LLDB attach, breakpoints, stack/variables; UI automation taps, swipes, screenshots, view hierarchy
- SwiftPM build/test/run; project scaffolding for new iOS/macOS templates
- Capabilities span session defaults, simulator, device, macOS, logs, LLDB, UI automation, SwiftPM, and scaffolding per SK
Adoption & trust: 653 installs on skills.sh; 5.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent keeps running brittle raw xcodebuild and simctl commands instead of a consistent Apple build and debug workflow.
Who is it for?
Indie iOS/macOS developers using MCP-enabled agents who want simulator-first loops with an upgrade path to device signing and LLDB.
Skip if: Cross-platform Android/Flutter-only shops, hosted CI-only pipelines with no local Xcode, or teams unwilling to enable extra MCP workflow capabilities.
When should I use this skill?
Doing iOS/macOS/watchOS/tvOS/visionOS work: build, test, run, debug, log, or UI automation—use XcodeBuildMCP tools instead of raw xcodebuild, xcrun, or simctl.
What do I get? / Deliverables
Your agent uses configured XcodeBuildMCP defaults to build, test, capture logs, and debug on simulators or devices with fewer misfires.
- Built and runnable app on simulator or device
- Test runs, log captures, and optional UI automation artifacts (screenshots, hierarchy inspect)
Recommended Skills
Journey fit
How it compares
MCP integration skill for local Apple toolchains—not a cloud CI recipe or App Store launch checklist.
Common Questions / FAQ
Who is xcodebuildmcp for?
Solo and indie builders doing Apple-platform app work with AI agents that can call XcodeBuildMCP instead of manual Xcode CLI strings.
When should I use xcodebuildmcp?
During Build when you compile, run on simulators or devices, capture logs, attach LLDB, automate UI checks, or scaffold SwiftPM/Xcode projects.
Is xcodebuildmcp safe to install?
It orchestrates local build and signing actions; review the Security Audits panel on this Prism page and limit device signing profiles to what you trust the agent to use.
SKILL.md
READMESKILL.md - Xcodebuildmcp
# 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_defaults` before the first build/run/test action in a session. - Use `discover_projs` only 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.