XcodeBuildMCP for Cursor: Setup & Config

What you can do with XcodeBuildMCP in Cursor

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

• Use stateful debugging and log capture through a workspace daemon.
• Install agent guidance for MCP or direct CLI workflows.

Before you start: XcodeBuildMCP in Cursor

• 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 Cursor configuration

1. Choose Cursor configuration scope

   For XcodeBuildMCP, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add XcodeBuildMCP to Cursor

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

3. Check XcodeBuildMCP in Cursor

   XcodeBuildMCP: Enable in Cursor’s MCP settings; inspect tools.

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

Troubleshooting XcodeBuildMCP in Cursor

• Cursor must find npx xcodebuildmcp@latest (Node.js/npm) for XcodeBuildMCP. Enable the project/user entry in MCP settings and inspect its tools.
• XcodeBuildMCP uses stdio here: Cursor 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 Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions