1. Home
  2. XcodeBuildMCP
  3. XcodeBuildMCP for Claude Desktop: Setup & Config

Data as of

XcodeBuildMCP for Claude Desktop: Setup & Config

XcodeBuildMCP provides an MCP server and CLI for Claude Desktop working on iOS and macOS projects.

What you can do with XcodeBuildMCP in Claude Desktop

Choose it for Xcode agent tooling available through either MCP or a unified terminal CLI.

  • Connect an AI coding agent to iOS and macOS development tools.
  • Build an Xcode project for a simulator from the CLI.

Before you start: XcodeBuildMCP in Claude Desktop

  • 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

The mcp subcommand starts the server. The init subcommand installs agent skills rather than starting the server. Homebrew provides an alternative installation without Node.js.

XcodeBuildMCP Claude Desktop configuration

  1. Choose Claude Desktop configuration scope

    For XcodeBuildMCP, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

  2. Add XcodeBuildMCP to Claude Desktop

    Use the XcodeBuildMCP entry below in mcpServers. Keep XcodeBuildMCP's documented stdio connection fields and your other Claude Desktop entries.

  3. Check XcodeBuildMCP in Claude Desktop

    XcodeBuildMCP: Fully quit and reopen Claude Desktop; check developer diagnostics.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

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

Troubleshooting XcodeBuildMCP in Claude Desktop

  • Fully quit and reopen Claude Desktop for XcodeBuildMCP. If npx xcodebuildmcp@latest (Node.js/npm) is missing, check the desktop process's PATH, which may differ from your terminal.
  • XcodeBuildMCP uses stdio here: Claude Desktop must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Requires macOS 14.5 or newer and Xcode 16.x or newer.
  • Known limitation: Device tools need Xcode code signing configured.
  • Known limitation: Runtime error telemetry is present; opt-out details are linked separately.
  • General Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

XcodeBuildMCP — details. Claude Desktop guide

Frequently asked questions

Claude Desktop loads XcodeBuildMCP from claude_desktop_config.json: ~/Library/Application Support/Claude/ on macOS, or %APPDATA%\Claude\ on Windows. Open it via Settings → Developer → Edit Config when available.

Claude Desktop's XcodeBuildMCP example uses stdio.

XcodeBuildMCP's Claude Desktop configuration invokes npx xcodebuildmcp@latest (Node.js/npm).

No. The README uses init to install agent skills. The mcp subcommand starts the MCP server.

No. Node.js 18.x or newer is required for the npm method, but the Homebrew installation does not require it.

The README requires macOS 14.5 or later and Xcode 16.x or later.