XcodeBuildMCP
An MCP server and standalone CLI that give coding agents access to Xcode builds, tests, simulators, devices, debugging, and UI automation.
Project overview
XcodeBuildMCP is a local MCP server and CLI for Apple-platform development. It exposes Xcode project discovery, build and test commands, simulator and device control, LLDB debugging, and UI automation to coding agents. The project is more than a thin wrapper around one command: its repository contains 82 tool manifests organized into 15 workflows, so teams can enable only the surfaces they need. It is most useful when an agent must observe the real Xcode toolchain instead of reasoning from source files alone.
Core capabilities
Build and test across Apple targets
Simulator, physical-device, and macOS workflows expose build, run, test, clean, app-path, and reusable prepared-test operations. Physical devices still depend on code signing configured in Xcode.
Simulator and application control
The tool manifests cover listing, booting, opening, and shutting down simulators as well as installing, launching, stopping, and collecting logs from applications.
UI automation and accessibility inspection
Agents can capture screenshots and accessibility hierarchies, then tap, swipe, type, press buttons, and perform gestures in supported simulators.
LLDB and Xcode diagnostics
Debugging and Xcode IDE workflows expose debugger sessions, breakpoints, execution control, diagnostics, and selected IDE-backed operations.
Workflow-scoped tool exposure
Configuration can enable built-in or custom workflows, limiting the tools visible to an agent. The README states that only the simulator workflow is enabled by default.
Setup and connection
Install the Homebrew binary or launch the npm package, add the stdio server command to the MCP host, then verify discovery before enabling broader workflows.
Let an AI Agent install it
Send this prompt to Codex, Claude Code, or another AI agent that can work with your local environment.
Help me install and configure XcodeBuildMCP from https://github.com/getsentry/XcodeBuildMCP. Read the README, release notes, LICENSE, SECURITY policy, and config example first. Confirm macOS and Xcode versions, choose Homebrew unless I specifically need npm, and show the MCP config before writing it. Keep the initial workflow scope minimal, disable Sentry telemetry if required by my policy, and do not run builds, control devices, delete DerivedData, or overwrite configuration without explaining the exact command and target. Verify connection with help or read-only discovery and report every changed file and result.- macOS 14.5 or newer
- Xcode 16.x or newer
- Node.js 18 or newer when using npm or npx
- An MCP host with stdio configuration support
- Xcode code signing configured before using physical-device tools
{"mcpServers":{"XcodeBuildMCP":{"command":"xcodebuildmcp","args":["mcp"]}}}- 1Confirm the local toolchain
Check that the Mac meets the documented OS requirement and that Xcode 16.x or newer is installed. Configure code signing in Xcode before any physical-device task.
- 2Choose an installation path
For Homebrew, run `brew tap getsentry/xcodebuildmcp` followed by `brew install xcodebuildmcp`. For npm, Node.js 18 or newer is required and the documented launch command is `npx -y xcodebuildmcp@latest mcp`.
- 3Add the stdio MCP configuration
Configure the host to run `xcodebuildmcp mcp`, or use `npx` with the arguments `-y`, `xcodebuildmcp@latest`, and `mcp`. Decide whether to disable Sentry runtime diagnostics.
- 4Verify before broadening access
Restart the host, confirm the server and tools appear, and begin with help, project discovery, or simulator listing. Enable additional workflows only when the current task needs them.
Restart the MCP host and confirm that XcodeBuildMCP connects. Start with project discovery or `xcodebuildmcp --help`, then select a harmless sample project and list schemes or simulators before attempting a build or UI action.
- Homebrew avoids the Node.js prerequisite
- Only the simulator workflow is enabled by default
- Set XCODEBUILDMCP_SENTRY_DISABLED=true or sentryDisabled: true to disable telemetry
- Review v2.7.0 schema and configuration changes before upgrading an existing integration
Use cases
Build and test an iOS change
An agent can discover the project and scheme, select a simulator, build the app, run tests, and inspect structured results without manually translating every xcodebuild flag.
Reproduce a simulator UI failure
UI automation tools can inspect accessibility state, capture screenshots, perform gestures, and collect logs while the agent follows a repeatable reproduction path.
Debug a macOS or device process
With the relevant workflow and local permissions enabled, the agent can launch targets, attach LLDB, manage breakpoints, and inspect execution state.
Reuse prepared tests in automation
Version 2.7.0 can produce portable `.xctestproducts` packages and run them later without rebuilding, while still creating a fresh `.xcresult`.
Assessment
XcodeBuildMCP has unusually broad and inspectable coverage for Apple-platform agent workflows: its tools, workflow boundaries, configuration schema, tests, changelog, release notes, and security policy are all public. Homebrew offers a clean path without Node.js, and custom workflow exposure helps reduce the visible tool surface. The cost of that power is meaningful local authority over builds, processes, simulators, devices, and UI input. Teams also need to account for default Sentry runtime diagnostics and the breaking schema v3 change in v2.7.0. This catalog review did not install or execute the project.
Why it may be useful
- Broad Xcode coverage organized into explicit workflow manifests
- Homebrew, npm, MCP, CLI, configuration, and upgrade paths are documented
- Active release and commit history with public tests and security guidance
- Workflow selection can keep the exposed tool set smaller
What to know first
- Only works where a compatible macOS and Xcode toolchain is available
- Agent actions can affect builds, simulators, apps, processes, and local files
- Runtime error telemetry is enabled by default unless explicitly disabled
- Existing structured-output consumers may need changes for v2.7.0 schema v3
README
XcodeBuildMCP
Overview
An MCP server and standalone CLI that give coding agents access to Xcode builds, tests, simulators, devices, debugging, and UI automation. MCP server and CLI tools for Xcode, enabling agentic workflows for iOS and macOS development.
Getting started
- Install the Homebrew binary or launch the npm package, add the stdio server command to the MCP host, then verify discovery before enabling broader workflows.
- The repository presents XcodeBuildMCP as both an MCP server and a standalone CLI. MCP clients can launch it through the Homebrew binary or `npx -y xcodebuildmcp@latest mcp`, while the CLI exposes the same tool surface as discoverable commands.
- Its 15 workflow manifests cover simulator and physical-device builds, macOS applications, project discovery and scaffolding, Swift packages, UI automation, LLDB debugging, Xcode IDE integration, coverage, diagnostics, utilities, and session management. The bundled skills recommend setting session defaults once and using the smallest relevant workflow set.
- Restart the MCP host and confirm that XcodeBuildMCP connects. Start with project discovery or `xcodebuildmcp --help`, then select a harmless sample project and list schemes or simulators before attempting a build or UI action.
Configuration
{"mcpServers":{"XcodeBuildMCP":{"command":"xcodebuildmcp","args":["mcp"]}}}