The best MCP servers for Xcode, compared

An MCP server for Xcode gives your coding agent (Claude Code, Cursor, Codex and others) tools to build, test and inspect Apple projects instead of guessing xcodebuild flags. In 2026 there are two kinds: Apple's own bridge, which talks to a running Xcode, and community servers that drive the command-line toolchain. This guide compares the ones we list in the Xcode & builds and Simulator & devices categories, with setup commands copied from each project's own documentation.

Quick comparison

GitHub data checked on 2026-10-16: MobileBuildMCP 6,485 stars (last push 2026-10-09), iOS Simulator MCP 2,193 stars, r-huijts/xcode-mcp-server 386, xcodeproj-mcp-server 133, XC-MCP 100.

1. Apple's Xcode Tools: xcrun mcpbridge

Since Xcode 26.3, Xcode includes an MCP server for external agents. According to Cursor's Xcode integration docs, xcrun mcpbridge translates MCP messages into Xcode's XPC layer and exposes 20 tools in five groups: file operations (XcodeRead, XcodeWrite, XcodeUpdate, XcodeGrep…), build and test (BuildProject, GetBuildLog, RunAllTests, RunSomeTests, GetTestList), diagnostics (Issue Navigator), "intelligence" (RenderPreview for SwiftUI previews, DocumentationSearch across Apple docs and WWDC transcripts, ExecuteSnippet) and XcodeListWindows.

Setup. In Xcode, open Settings → Intelligence and under Model Context Protocol turn on Xcode Tools. Then register the bridge as a stdio server. For Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "xcode-tools": {
      "command": "xcrun",
      "args": ["mcpbridge"]
    }
  }
}

Source: cursor.com/docs/integrations/xcode. Apple's page: Giving external agents access to Xcode.

Watch out: Xcode must be running with a project open. If you get unable to find utility "mcpbridge", your developer directory points at the Command Line Tools; the Cursor docs fix it with sudo xcode-select -s /Applications/Xcode.app/Contents/Developer.

Best for: SwiftUI preview screenshots and Apple doc search from the IDE you already have open.

2. MobileBuildMCP (formerly XcodeBuildMCP)

The project many tutorials still call XcodeBuildMCP now lives at getsentry/MobileBuildMCP; the old GitHub URL redirects there. It ships as one package with a CLI and an MCP server. The CLI docs list workflows for simulator, device, macos, swift-package, debugging (LLDB) and ui-automation. Requirements per the installation docs: macOS 14.5+, Xcode 16+, Node.js 18+ for the npm path.

Claude Code, from the MCP clients page:

claude mcp add MobileBuildMCP -- npx -y mobilebuildmcp@latest mcp

Only the simulator workflow is enabled by default; enable more in .mobilebuildmcp/config.yaml or with mobilebuildmcp setup. Full walkthrough: MobileBuildMCP / XcodeBuildMCP setup guide.

Best for: a headless build-run-test loop that does not need Xcode open, plus device builds and debugging.

3. XC-MCP

XC-MCP wraps xcodebuild, simctl and idb as 77 tools. Its README focuses on context size: tools that produce large output return a summary plus an ID, and the full output stays retrievable for 30 minutes. Setup from the README:

claude mcp add xc-mcp -- npx -y xc-mcp

Requirements per README: macOS 13+, Xcode/Command Line Tools 15+ (26+ for iOS 26/27 simulators); idb tools need brew install facebook/fb/idb-companion facebook/fb/idb-cli. GitHub shows no license for the repo, so check before using it at work.

4. iOS Simulator MCP

ios-simulator-mcp does one thing: interact with a booted simulator. Its tools include ui_describe_all, ui_tap and ui_view, which let an agent check a screen after a change. README setup for Claude Code:

claude mcp add ios-simulator npx ios-simulator-mcp

It runs on macOS only. Pair it with a build server (MobileBuildMCP or XC-MCP); it does not build your app. Alternatives in the same category: mobile-mcp, mcp-server-simulator-ios-idb.

5. xcodeproj MCP Server

xcodeproj-mcp-server edits .xcodeproj files through the tuist/xcodeproj library, so an agent can add files or targets without hand-editing project.pbxproj. The README recommends Apple's container runtime on macOS 26+ and Docker on older systems:

claude mcp add xcodeproj -- container run --rm -i -v '${CLAUDE_PROJECT_DIR:-.}:/workspace' ghcr.io/giginet/xcodeproj-mcp-server:latest /workspace

Which one should you use?

• You keep Xcode open and want previews/doc search: Apple's xcrun mcpbridge.

• You want the agent to build, run and test without Xcode open: MobileBuildMCP.

• Context budget is tight: XC-MCP's summarized outputs, or MobileBuildMCP with only the workflows you need.

• The agent must "see" the UI: add iOS Simulator MCP next to your build server.

• The agent keeps breaking project.pbxproj: add xcodeproj MCP Server.

Many setups combine two: one build server plus one UI server. Every tool definition costs context, so start small.

Make agents use them well

MCP gives the agent hands; skills and rules tell it how to write Swift. Browse SwiftUI agent skills, the Xcode Build Optimization skill and the iOS Simulator Skill.