Shipping v2.3.2 · 82 tools · Requires Xcode 16+

Xcode, the way your agent wants to use it.

An MCP server and CLI that gives AI agents full control over Xcode. Build, test, debug, and deploy your iOS and macOS apps without leaving your agent.

Get started Star on GitHub

$brew install getsentry/xcodebuildmcp/xcodebuildmcp

Tools

Workflows

Clients

MIT

Licence

What's inside#

XcodeBuildMCP gives AI coding agents up-to 82 tools across 16 workflows for iOS, iPadOS, macOS, watchOS, tvOS, and visionOS development. Build, test, debug, and deploy your iOS and macOS apps without leaving your agent.

Project discovery

Find .xcodeproj, .xcworkspace, and Swift packages automatically.

Build, test, clean

Structured build, test, and clean for simulators, devices, and macOS targets.

Build and run

One tool call compiles, installs, launches, and streams logs, no multi-step dance for the agent to get wrong.

Simulator lifecycle

Boot, install, launch, capture logs, record video, and reset state.

Physical devices

Install and launch on paired iPhones, iPads, Apple Watches, and Vision Pros, over USB or Wi-Fi.

LLDB debugging

Attach, set breakpoints, inspect frames and variables, run raw LLDB commands.

UI automation

Tap, swipe, type, gesture, and inspect the view hierarchy with precise coordinates.

Code coverage

Per-target summaries and function-level uncovered-line reports from xcresult.

Swift Package Manager

Build, test, and run Swift packages, executables included, with background processes managed through the daemon.

Session defaults

Set workspace, scheme, and simulator once. Saves tokens on every turn and cuts the agent mistakes caused by re-supplying project details on each call.

Two modes, one binary#

shell

# Started by your MCP client via stdio
xcodebuildmcp mcp

The MCP server speaks Model Context Protocol over stdio. The CLI exposes every tool directly for scripting, CI, and manual debugging. Both share the same code, the same config file, and the same per-workspace daemon.

Why XcodeBuildMCP#

Agents shelling out to xcodebuild get brittle, verbose, and inconsistent results. XcodeBuildMCP gives them:

Stable tool names and flags, versioned per release.
Structured outputs with pre-parsed build diagnostics, durable preflight/footer sections, and JSONL streams on demand.
Session defaults that eliminate repeated scheme/project/simulator boilerplate across tool calls.
Two optional agent skills (xcodebuildmcp init) that prime Claude Code, Cursor, and Codex with the right conventions.
Per-workspace daemon for stateful operations (log capture, debugging, video) with automatic start/stop.

You know what we do for a living.

XcodeBuildMCP ships with Sentry for internal runtime errors only. User project failures (build, test, config) are never sent, and tool arguments/outputs are never captured. Opt out any time with XCODEBUILDMCP_SENTRY_DISABLED=true. See Privacy & Telemetry.