Server facts
XcodeBuildMCP MCP Server
Project
- Author
- cameroncooke
- Repository
- github.com/cameroncooke/XcodeBuildMCP
- Website
- www.xcodebuildmcp.com
- License
- MIT
- Category
- Developer Tools
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 6,488
- Last commit
- Data as of
Tags
- Agent Cli
- Build Tools
- Ios Development
- Macos Development
- Xcode
Overview
XcodeBuildMCP packages an MCP server and a command-line interface for agent workflows on iOS and macOS projects. Both modes come from the same installation, so users can either connect an AI coding client or invoke operations directly in a terminal. The README demonstrates a simulator build command and describes a per-workspace daemon for stateful CLI work such as debugging and log capture. That daemon starts when needed. Optional agent skills provide instructions for using the MCP tools or navigating the CLI, with the CLI skill recommended for direct command-line use.
Installation is available through Homebrew or npm, and most clients can start the MCP mode on demand through npx. The documented requirements are macOS 14.5 or newer and Xcode 16.x or newer. Node.js 18.x or newer is required for the npm route but not for the Homebrew installation. Device tools additionally need code signing configured in Xcode. The project notes that builds request skipped macro validation to avoid errors with Swift Macros, which is a behavior worth understanding when evaluating a build workflow. Runtime error telemetry uses Sentry, with details and opt-out instructions linked separately. The supplied README points to external documentation for the full tool inventory, client-specific configuration, and advanced settings rather than enumerating individual MCP tool names.
Install & configure
Requirements
- macOS 14.5 or newer
- Xcode 16.x or newer
- Node.js 18.x or newer for the npm/npx method
- Xcode code signing for device tools
npx -y xcodebuildmcp@latest mcpThe mcp subcommand starts the server. The init subcommand installs agent skills rather than starting the server. Homebrew provides an alternative installation without Node.js.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"XcodeBuildMCP": {
"command": "npx",
"args": [
"-y",
"xcodebuildmcp@latest",
"mcp"
],
"env": {}
}
}
}Config file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"XcodeBuildMCP": {
"command": "npx",
"args": [
"-y",
"xcodebuildmcp@latest",
"mcp"
],
"env": {}
}
}
}Config file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
{
"servers": {
"XcodeBuildMCP": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"xcodebuildmcp@latest",
"mcp"
],
"env": {}
}
}
}Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"XcodeBuildMCP": {
"command": "npx",
"args": [
"-y",
"xcodebuildmcp@latest",
"mcp"
],
"env": {}
}
}
}Config file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"XcodeBuildMCP": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"xcodebuildmcp@latest",
"mcp"
],
"env": {}
}
}
}Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Use cases
- Connect an AI coding agent to iOS and macOS development tools.
- Build an Xcode project for a simulator from the CLI.
- Use stateful debugging and log capture through a workspace daemon.
- Install agent guidance for MCP or direct CLI workflows.
Strengths
- One package provides both MCP and direct terminal modes.
- Homebrew installation does not require Node.js.
- Automatically starts a workspace daemon for stateful CLI operations.
Limitations
- Requires macOS 14.5 or newer and Xcode 16.x or newer.
- Device tools need Xcode code signing configured.
- Runtime error telemetry is present; opt-out details are linked separately.
XcodeBuildMCP setup notes
- XcodeBuildMCP's stdio example needs a client that launches local processes.