Skill Detail

Build, test, and inspect Apple apps through MCP with XcodeBuildMCP

Connect coding agents to Xcode build, test, simulator, and project-inspection tools through XcodeBuildMCP's MCP server or CLI.

Developer ToolsMCP
Developer Tools MCP Security Reviewed
โญ 5.7k GitHub stars โฌ‡ 44.5k/wk npm
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill build-test-and-inspect-apple-apps-through-mcp-with-xcodebuildmcp Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Xcode 16 or later, Node.js 18 or later for npm install, MCP-compatible client
Install & setup
Install with Homebrew using `brew tap getsentry/xcodebuildmcp && brew install xcodebuildmcp`, or with npm using `npm install -g xcodebuildmcp@latest`. Verify with `xcodebuildmcp –help`, then connect the MCP server to your client or run `xcodebuildmcp init` to install the optional agent skills.
Author
Sentry
Publisher
Organization
Last updated
May 23, 2026
Quick brief

Use XcodeBuildMCP when an agent is working on iOS or macOS code and needs structured access to build, test, simulator, and Xcode project operations. The operator installs the package, connects an MCP-capable client or uses the CLI directly, and lets the agent run Xcode-focused checks with evidence instead of guessing from source files alone. Inputs are a local Apple-platform project, selected scheme or simulator context, and a build, test, inspect, or device-management task; outputs are reviewable command results, logs, diagnostics, and next-step evidence for the coding agent. The scope boundary is Apple-platform development operations exposed through MCP and the companion CLI, not a generic Sentry or Xcode listing.

How it works

What this skill actually does

Inputs and prerequisites: Xcode 16 or later, Node.js 18 or later for npm install, MCP-compatible client.

Setup notes: Install with Homebrew using `brew tap getsentry/xcodebuildmcp && brew install xcodebuildmcp`, or with npm using `npm install -g xcodebuildmcp@latest`. Verify with `xcodebuildmcp –help`, then connect the MCP server to your client or run `xcodebuildmcp init` to install the optional agent skills.

Source and verification boundary: use https://www.xcodebuildmcp.com as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a MCP workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.