xcodebuildmcp-cli
Standardizes Xcode build, test, and debug workflows via the CLI.
Install
mkdir -p .claude/skills/xcodebuildmcp-cli && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1680" && unzip -o skill.zip -d .claude/skills/xcodebuildmcp-cli && rm skill.zipInstalls to .claude/skills/xcodebuildmcp-cli
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 the XcodeBuildMCP CLI. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).Key capabilities
- →Build and run iOS/macOS/watchOS/tvOS/visionOS apps
- →Execute UI automation tests
- →Capture build logs and diagnostic data
- →Manage simulators and devices
- →Discover project workflows
How it works
The skill acts as a wrapper for the XcodeBuildMCP CLI, providing a unified interface for build, test, and run operations across Apple platforms.
Inputs & outputs
When to use xcodebuildmcp-cli
- →Building iOS apps
- →Running UI tests
- →Capturing build logs
About this skill
XcodeBuildMCP CLI
Use XcodeBuildMCP tools via the xcodebuildmcp executable instead of raw xcodebuild, xcrun, or simctl.
Step 1: Ensure the CLI Exists
Check availability:
xcodebuildmcp --help
If missing, install with one of:
brew tap getsentry/xcodebuildmcp
brew install xcodebuildmcp
npm install -g xcodebuildmcp@latest
Re-check after install:
xcodebuildmcp --help
Step 2: Use Help-First Discovery
Discover workflows and arguments from the CLI itself:
xcodebuildmcp --help
xcodebuildmcp tools
xcodebuildmcp <workflow> --help
xcodebuildmcp <workflow> <tool> --help
Use this discovery path instead of memorizing static tool lists.
Step 3: Keep Execution Minimal
- Choose the smallest command sequence that satisfies the request.
- Prefer direct workflow commands over manual multi-step chains unless explicitly requested.
- For simulator run intent, prefer the combined
build-and-runcommand. - Do not chain
buildthenbuild-and-rununless explicitly requested.
Capability Overview
xcodebuildmcp supports:
- simulator and device build/test/run
- debugging and log capture
- UI automation
- project discovery and scaffolding
- session defaults and workflow configuration
Exit Criteria
- CLI presence is verified or installation steps are provided.
- Commands are discovered via
--help/tools. - Session defaults are checked before first build/run/test action.
When not to use it
- →When raw xcodebuild calls are explicitly required
Prerequisites
Limitations
- →Requires Xcode environment
- →Limited to workflows supported by the CLI
How it compares
It replaces manual, complex xcodebuild chains with simplified, discovery-based workflow commands.
Compared to similar skills
xcodebuildmcp-cli side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| xcodebuildmcp-cli (this skill) | 3 | 5mo | Review | Intermediate |
| agent-production-validator | 3 | 6mo | Review | Advanced |
| django-verification | 5 | 4mo | Review | Intermediate |
| validate-delivery | 1 | 5mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by cameroncooke
View all by cameroncooke →You might also like
agent-production-validator
ruvnet
Agent skill for production-validator - invoke with $agent-production-validator
django-verification
affaan-m
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.
validate-delivery
avifenesh
Use when validating task completion before shipping. Runs tests, build, and requirement checks. Returns pass/fail with fix instructions.
deployment-e2e-testing
dotnet
Guide for writing Aspire deployment end-to-end tests. Use this when asked to create, modify, or debug deployment E2E tests that deploy to Azure.
release-testing
mono
Run integration tests to verify SkiaSharp NuGet packages work correctly before publishing. Use when user asks to: - Test/verify packages before release - Run integration tests - Test on specific device (iPad, iPhone, Android emulator, Mac, Windows) - Verify SkiaSharp rendering works - Check if packages are ready for publishing - Run smoke/console/blazor/maui tests - Continue with release - Test version X Triggers: "test the release", "verify packages", "run tests on iPad", "check ios tests", "test mac catalyst", "run android tests", "continue", "test 3.119.2-preview.2".
validate
iPlug2
Validate iPlug2 plugin builds using format-specific validators (auval, pluginval, vstvalidator, clap-validator) (project)