1. Home
  2. XcodeBuildMCP
  3. XcodeBuildMCP for VS Code: Setup & Config

Data as of

XcodeBuildMCP for VS Code: Setup & Config

XcodeBuildMCP provides an MCP server and CLI for VS Code working on iOS and macOS projects.

What you can do with XcodeBuildMCP in VS Code

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.
  • Use stateful debugging and log capture through a workspace daemon.

Before you start: XcodeBuildMCP in VS Code

  • 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 VS Code configuration

  1. Choose VS Code configuration scope

    For XcodeBuildMCP, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add XcodeBuildMCP to VS Code

    Use the XcodeBuildMCP entry below in servers. Keep XcodeBuildMCP's documented stdio connection fields and your other VS Code entries.

  3. Check XcodeBuildMCP in VS Code

    XcodeBuildMCP: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

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

Troubleshooting XcodeBuildMCP in VS Code

  • Make npx xcodebuildmcp@latest (Node.js/npm) available in the workspace, container, or remote environment hosting XcodeBuildMCP. Start through VS Code's MCP controls; inspect output and trust prompts.
  • XcodeBuildMCP uses stdio here: VS Code 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 VS Code troubleshooting lives in the /clients/vscode guide.

XcodeBuildMCP — details. VS Code guide

Frequently asked questions

For XcodeBuildMCP, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's XcodeBuildMCP example uses stdio.

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

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.

Configure Xcode code signing before using the device tools.