XcodeBuildMCP by cameroncooke - MCP Server

A Model Context Protocol (MCP) server that provides Xcode-related tools for integration with AI assistants and other MCP clients.

Overview

XcodeBuildMCP is a Model Context Protocol (MCP) server that exposes Xcode operations as tools and resources for AI assistants and other MCP clients. Built with a modern plugin architecture, it provides a comprehensive set of self-contained tools organized into workflow-based directories, plus MCP resources for efficient data access, enabling programmatic interaction with Xcode projects, simulators, devices, and Swift packages through a standardized interface.

xcodebuildmcp2

Using Cursor to build, install, and launch an app on the iOS simulator while capturing logs at run-time.

Why?

The XcodeBuild MCP tool exists primarily to streamline and standardise interaction between AI agents and Xcode projects. By providing dedicated tools for common Xcode operations, it removes reliance on manual or potentially incorrect command-line invocations.

This ensures a reliable and efficient development process, allowing agents to seamlessly leverage Xcode's capabilities while reducing the risk of configuration errors.

Critically, this MCP enables AI agents to independently validate code changes by building projects, inspecting errors, and iterating autonomously. In contrast to user-driven tools like Sweetpad, XcodeBuild MCP empowers agents to automate these workflows effectively.

Features

The XcodeBuildMCP server provides the following tool capabilities:

Xcode project management

Discover Projects: Xcode projects and workspaces discovery
Build Operations: Platform-specific build tools for macOS, iOS simulator, and iOS device targets
Project Information: Tools to list schemes and show build settings for Xcode projects and workspaces
Clean Operations: Clean build products using xcodebuild's native clean action
Incremental build support: Lightning fast builds using incremental build support (experimental, opt-in required)
Project Scaffolding: Create new iOS and macOS projects from modern templates with workspace + SPM package architecture, customizable bundle identifiers, deployment targets, and device families

Swift Package Manager

Build Packages: Build Swift packages with configuration and architecture options
Run Tests: Execute Swift package test suites with filtering and parallel execution
Run Executables: Execute package binaries with timeout handling and background execution support
Process Management: List and stop long-running executables started with Swift Package tools
Clean Artifacts: Remove build artifacts and derived data for fresh builds

Simulator management

Simulator Control: List, boot, and open simulators
App Lifecycle: Complete app management - install, launch, and stop apps on simulators
Log Capture: Capture run-time logs from a simulator
UI Automation: Interact with simulator UI elements
Screenshot: Capture screenshots from a simulator

Device management

Device Discovery: List connected physical Apple devices over USB or Wi-Fi
App Lifecycle: Complete app management - build, install, launch, and stop apps on physical devices
Testing: Run test suites on physical devices with detailed results and cross-platform support
Log Capture: Capture console output from apps running on physical Apple devices
Wireless Connectivity: Support for devices connected over Wi-Fi networks

App utilities

Bundle ID Extraction: Extract bundle identifiers from app bundles across all Apple platforms
App Lifecycle Management: Complete app lifecycle control across all platforms
- Launch apps on simulators, physical devices, and macOS
- Stop running apps with process ID or bundle ID management
- Process monitoring and control for comprehensive app management

MCP Resources

For clients that support MCP resources XcodeBuildMCP provides efficient URI-based data access:

Simulators Resource (xcodebuildmcp://simulators): Direct access to available iOS simulators with UUIDs and states
Devices Resource (xcodebuildmcp://devices): Direct access to connected physical Apple devices with UDIDs and states
Doctor Resource (xcodebuildmcp://doctor): Direct access to environment information such as Xcode version, macOS version, and Node.js version

Getting started

Prerequisites

macOS 14.5 or later
Xcode 16.x or later
Node 18.x or later

Configure your MCP client

Quick install

For a quick install, you can use the following links:

Manual installation

Configure your MCP client (Windsurf, Cursor, Claude Desktop, Claude Code etc.) to use the XcodeBuildMCP server by ammending your client application's MCP configuration.

{
  "mcpServers": {
    "XcodeBuildMCP": {
      "command": "npx",
      "args": [
        "-y",
        "xcodebuildmcp@latest"
      ]
    }
  }
}

Alternative installation method using mise

Alternatively, you can use XcodeBuildMCP without a specific installation of Node.js by using mise to install it:

# macOS (Homebrew)
brew install mise

# Other installation methods
# See https://mise.jdx.dev/getting-started.html

Then configure your MCP client to use mise to install XcodeBuildMCP:

{
  "mcpServers": {
    "XcodeBuildMCP": {
      "command": "mise",
      "args": [
        "x",
        "npm:xcodebuildmcp@1.12.1",
        "--",
        "xcodebuildmcp"
      ]
    }
  }
}

[!NOTE] When using mise avoid using the @latest tag as mise will cache the package and may not update to the latest version automatically, instead prefer an explicit version number.

[!IMPORTANT] Please note that XcodeBuildMCP will request xcodebuild to skip macro validation. This is to avoid errors when building projects that use Swift Macros.

Installing via Smithery

To install XcodeBuildMCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @cameroncooke/XcodeBuildMCP --client claude

MCP Compatibility

XcodeBuildMCP supports both MCP tools, resources and sampling. At time of writing the following editors have varying levels of MCP feature support:

Editor	Tools	Resources	Samplng
VS Code	✅	✅	✅
Cursor	✅	❌	❌
Windsurf	✅	❌	❌
Claude Code	✅	✅	❌
Claude Desktop	✅	✅	❌

Incremental build support

XcodeBuildMCP includes experimental support for incremental builds. This feature is disabled by default and can be enabled by setting the INCREMENTAL_BUILDS_ENABLED environment variable to true:

To enable incremental builds, set the INCREMENTAL_BUILDS_ENABLED environment variable to true:

Example MCP client configuration:

{
  "mcpServers": {
    "XcodeBuildMCP": {
      "command": "npx",
      "args": [
        "-y",
        "xcodebuildmcp@latest"
      ],
      "env": {
        "INCREMENTAL_BUILDS_ENABLED": "true"
      }
    }
  }
}

[!IMPORTANT] Please note that incremental builds support is currently highly experimental and your mileage may vary. Please report any issues you encounter to the issue tracker.

Dynamic Tools

XcodeBuildMCP supports dynamic tool loading to optimize context window usage in AI assistants. This feature is particularly useful for managing the extensive toolset (80+ tools) that XcodeBuildMCP provides.

What is Dynamic Tools?

By default, XcodeBuildMCP loads all available tools at startup (Static Mode), which provides immediate access to the complete toolset but uses a larger context window. Dynamic Tools mode solves this by:

Starting minimal: Only essential tools like discover_tools and discover_projs are available initially
AI-powered discovery: When an AI agent identifies XcodeBuildMCP can help with development tasks, it automatically uses the discover_tools tool
Intelligent loading: The server uses an LLM call to identify the most relevant workflow group and dynamically loads only those tools
Context efficiency: Reduces the initial context footprint from 80+ tools to just 2 discovery tools while maintaining full functionality

How to Enable Dynamic Tools

To enable dynamic tools, set the XCODEBUILDMCP_DYNAMIC_TOOLS environment variable to true:

Example MCP client configuration:

{
  "mcpServers": {
    "XcodeBuildMCP": {
      "command": "npx",
      "args": [
        "-y",
        "xcodebuildmcp@latest"
      ],
      "env": {
        "XCODEBUILDMCP_DYNAMIC_TOOLS": "true"
      }
    }
  }
}

Selective Workflow Loading (Static Mode)

For clients that don't support MCP Sampling but still want to reduce context window usage, you can selectively load only specific workflows using the XCODEBUILDMCP_ENABLED_WORKFLOWS environment variable:

{
  "mcpServers": {
    "XcodeBuildMCP": {
      "command": "npx",
      "args": [
        "-y",
        "xcodebuildmcp@latest"
      ],
      "env": {
        "XCODEBUILDMCP_ENABLED_WORKFLOWS": "simulator,device,project-discovery"
      }
    }
  }
}

Available Workflows:

device (14 tools) - iOS Device Development
simulator (18 tools) - iOS Simulator Development
simulator-management (7 tools) - Simulator Management
swift-package (6 tools) - Swift Package Manager
project-discovery (5 tools) - Project Discovery
macos (11 tools) - macOS Development
ui-testing (11 tools) - UI Testing & Automation
logging (4 tools) - Log Capture & Management
project-scaffolding (2 tools) - Project Scaffolding
utilities (1 tool) - Project Utilities
doctor (1 tool) - System Doctor
discovery (1 tool) - Dynamic Tool Discovery

[!NOTE] The XCODEBUILDMCP_ENABLED_WORKFLOWS setting only works in Static Mode. If XCODEBUILDMCP_DYNAMIC_TOOLS=true is set, the selective workflow setting will be ignored.

Usage Example

Once enabled, AI agents automatically discover and load relevant tools based on context. For example, when you mention working on an iOS app or the agent detects iOS development tasks in your workspace, it will automatically use the discover_tools tool to load the appropriate simulator and project tools needed for your workflow.

Client Compatibility

Dynamic Tools requires MCP clients that support MCP Sampling for the AI-powered tool discovery to function:

Editor	Dynamic Tools Support
VS Code	✅
Cursor	❌ (No MCP Sampling)
Windsurf	❌ (No MCP Sampling)
Claude Code	❌ (No MCP Sampling)
Claude Desktop	❌ (No MCP Sampling)

[!NOTE] For clients that don't support MCP Sampling, XcodeBuildMCP will automatically fall back to Static Mode, loading all tools at startup regardless of the XCODEBUILDMCP_DYNAMIC_TOOLS setting.

Code Signing for Device Deployment

For device deployment features to work, code signing must be properly configured in Xcode before using XcodeBuildMCP device tools:

Open your project in Xcode
Select your project target
Go to "Signing & Capabilities" tab
Configure "Automatically manage signing" and select your development team
Ensure a valid provisioning profile is selected

Note: XcodeBuildMCP cannot configure code signing automatically. This initial setup must be done once in Xcode, after which the MCP device tools can build, install, and test apps on physical devices.

Troubleshooting

If you encounter issues with XcodeBuildMCP, the doctor tool can help identify the problem by providing detailed information about your environment and dependencies.

Doctor Tool

The doctor tool is a standalone utility that checks your system configuration and reports on the status of all dependencies required by XcodeBuildMCP. It's particularly useful when reporting issues.

# Run the doctor tool using npx
npx --package xcodebuildmcp@latest xcodebuildmcp-doctor

The doctor tool will output comprehensive information about:

System and Node.js environment
Xcode installation and configuration
Required dependencies (xcodebuild, AXe, etc.)
Environment variables affecting XcodeBuildMCP
Feature availability status

When reporting issues on GitHub, please include the full output from the doctor tool to help with troubleshooting.

Privacy

This project uses Sentry for error monitoring and diagnostics. Sentry helps us track issues, crashes, and unexpected errors to improve the reliability and stability of XcodeBuildMCP.

What is sent to Sentry?

Only error-level logs and diagnostic information are sent to Sentry by default.
Error logs may include details such as error messages, stack traces, and (in some cases) file paths or project names. You can review the sources in this repository to see exactly what is logged.

Opting Out of Sentry

If you do not wish to send error logs to Sentry, you can opt out by setting the environment variable XCODEBUILDMCP_SENTRY_DISABLED=true.

Example MCP client configuration:

{
  "mcpServers": {
    "XcodeBuildMCP": {
      "command": "npx",
      "args": [
        "-y",
        "xcodebuildmcp@latest"
      ],
      "env": {
        "XCODEBUILDMCP_SENTRY_DISABLED": "true"
      }
    }
  }
}