getsentry xcodebuildmcp
OFFICIALLABSCO SUMMARY
The two documented skills exist to prime an agent to use XcodeBuildMCP itself — a Model Context Protocol server and CLI, installable via Homebrew or npm, for building, testing, running, and debugging iOS, macOS, watchOS, tvOS, and visionOS projects. One primes the agent for the MCP server's tools, the other for direct CLI use; the README recommends installing whichever mode you actually use. The other eleven skills — warden, warden-sweep, and nine more named for specific review boundaries (docs, packaging, rendering, runtime, snapshot fixtures, structured output, tool contracts, test boundaries) — never appear in the README at all.
This package serves two different audiences doing two different things. An iOS or macOS developer wanting an agent that can drive Xcode builds should install XcodeBuildMCP itself and its two documented skills. The other eleven only matter if you are contributing changes to the XcodeBuildMCP codebase and need warden's automated review sweep or one of the boundary-specific checks — they assume commit access to this repository, not just an installed tool.
READ THE FULL ANALYSIS
XcodeBuildMCP itself is a real, working tool, not a stub. It targets macOS 14.5+ and Xcode 16+, ships two install paths (a Homebrew tap or a global npm install), and its CLI covers commands like xcodebuildmcp simulator build end to end per its own documented usage — the thin instructional layer the two skills add sits on top of something that already works standalone.
One disclosed dependency worth knowing before you install. The README states that XcodeBuildMCP sends internal runtime error telemetry to Sentry, with opt-out instructions documented separately — it is disclosed, not hidden, but it is also not something either of the two skills mentions.
ALSO IN THIS PACKAGE
contacts
reminders
weather
sentry
Official Sentry MCP server for investigating issues, error reports, traces, and performance monitoring data from AI coding agents.
http · https://mcp.sentry.dev/mcpxcodebuildmcp-dev
stdio · node ../../build/cli.js mcpXcodeBuildMCP
A server providing tools for Xcode project management, simulator management, and app utilities.
stdio · npx -y xcodebuildmcp@latest mcpXcodeBuildMCP-Dev
stdio · node --inspect=9999 --trace-warnings ${workspaceFolder}/build/cli.js mcpXcodeBuildMCP
stdio · node ../../build/cli.js mcpWHAT'S INSIDE
13 showing · 13 totalNothing else to set up — install it and go.
warden
A second pair of eyes on your own work, run before anybody else sees it: it reads only the part you changed and separates what has to be dealt with now from what can wait.
warden-sweep
For when the problem is not today's change but everything that piled up before it — every file gets read, every suspicion gets checked a second time, and whatever survives arrives as a separate proposed fix you can take or throw away.
xcodebuildmcp
Building and running an iPhone or Mac app normally means a handful of arcane Apple command-line tools; this replaces them with a set an assistant can actually drive, and it remembers which project and which simulator you are on so you stop repeating yourself.
xcodebuildmcp-cli
One command, installed in a line from Homebrew or npm, covering the whole loop of building an iPhone or Mac app, putting it on a simulator and watching what it does — and it lists its own commands, so nothing has to be memorised.
xcodebuildmcp-docs-command-review
Release notes are full of commands, and some of them stopped working versions ago; this reads the entries that changed and flags any a person would copy out and run today, while leaving alone the old ones clearly marked as the before half of an upgrade example.
xcodebuildmcp-docs-release-review
Documentation drifts away from the thing it describes one release at a time; this takes a change to the docs, the release notes or the release script and asks whether all three still agree with each other and with the software.
xcodebuildmcp-packaging-resource-review
Something that works perfectly on the machine it was built on can reach a user missing a file it quietly depended on; this reads a change to how the thing gets packaged up and asks what would be absent by the time it lands.
xcodebuildmcp-rendering-streaming-review
One rule, checked on every change to how results get printed: the code doing the actual work must never behave differently depending on who is reading the output, a person at a terminal or another program.
xcodebuildmcp-runtime-boundary-review
Three different front doors lead into this tool — another program, a person typing a command, a background service — and all three are meant to arrive at the same counter at the back; this reads a change to the routing and checks none of them has been given a private shortcut.
xcodebuildmcp-snapshot-fixture-review
When a test fails you can fix the code, or you can quietly edit the answer the test was checking against; this looks at a change to those recorded answers and asks which of the two actually happened.
xcodebuildmcp-structured-output-review
Other programs read the data this one hands back, and they break the moment its shape changes; the rule is that a new shape gets a new version number instead of overwriting the old one, and this checks a change kept to it.
xcodebuildmcp-test-boundary-review
A test that genuinely builds an app and genuinely talks to a phone is slow, unreliable, and fails on everyone else's machine; this reads the tests that changed and checks the outside world was faked rather than actually called.
xcodebuildmcp-tool-contract-review
Each tool here is described in one file, written in another, and listed on a menu somewhere else; when one of the three moves and the others do not, the tool goes missing or answers to the wrong name, so this checks they still line up.
HOW TO GET IT
npx skills add getsentry/xcodebuildmcpnpx skills add getsentry/xcodebuildmcp --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.