How do I install the Xcodebuildmcp skill?

Run npx skillmds add om-scogo/xcodebuildmcp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Xcodebuildmcp safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Xcodebuildmcp?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Xcodebuildmcp free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Xcodebuildmcp?

om-scogo (@om-scogo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Xcodebuildmcp by om-scogo — Agent Skill

Name: Xcodebuildmcp
Rating: 4.2 (5 reviews)
Author: om-scogo

File contents

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.

---name: xcodebuildmcpdescription: Official skill for XcodeBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).---# XcodeBuildMCPUse 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 templatesOnly 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.

Frequently asked questions