Stable tool names, pre-parsed build diagnostics and session defaults are what make an iOS loop survivable for an agent: it stops re-supplying the scheme on every call and stops parsing raw build output.
An MCP server and CLI from Sentry, shipped as one binary. It exposes 82 tools across 15 workflows for iOS, iPadOS, macOS, watchOS, tvOS and visionOS, and every tool is callable from the terminal for scripting and CI. Both modes share the same code, the same config file and the same per-workspace daemon.
- Project discovery for `.xcodeproj`, `.xcworkspace` and Swift packages, then structured build, test and clean for simulators, devices and macOS targets
- Build and run in one call — compile, install, launch and stream logs — instead of a multi-step sequence the agent can get wrong
- Simulator lifecycle: boot, install, launch, capture logs, record video and reset state
- Physical devices over USB or Wi-Fi, including paired iPhones, iPads, Apple Watches and Vision Pros
- LLDB: attach, set breakpoints, inspect frames and variables, and run raw commands
- UI automation: tap, swipe, type, gesture, and inspect semantic element refs read off the view hierarchy
- Swift Package Manager builds, tests and runs, executables included, with long-running processes handled by the daemon
- Code coverage as per-target summaries and function-level uncovered-line reports from xcresult
- Session defaults so workspace, scheme and simulator are set once instead of resupplied on every call
- Two optional agent skills installed by `xcodebuildmcp init` — one that primes an agent on the MCP tools, one on the CLI
macOS 14.5 or later and Xcode 16.x or later. Install with `brew install getsentry/xcodebuildmcp/xcodebuildmcp`, or `npm install -g xcodebuildmcp@latest` on Node.js 18 or newer — Homebrew does not need Node at all. Most clients can also run it on demand with `npx -y xcodebuildmcp@latest mcp`. Loading all 82 tools is a lot of context, so `XCODEBUILDMCP_ENABLED_WORKFLOWS` narrows startup to the workflows you actually use. Device tools need code signing configured in Xcode first. Sentry reporting covers the tool's own runtime errors only — build, test and config failures in your project are never sent and tool arguments and outputs are never captured — and `XCODEBUILDMCP_SENTRY_DISABLED=true` switches it off.
One command — npm install -g xcodebuildmcp@latest