MCP adds iOS and macOS CLI
- Sentry’s XcodeBuildMCP package has emerged as a command-line tool and MCP server for iOS and macOS development, giving external AI agents Xcode-aware tools. - The package ships as `xcodebuildmcp`, installs through Homebrew or npm, and requires macOS 14.5+, Xcode 16.x+, and Node.js 18+ for npm users. - Apple now exposes Xcode tools through its own MCP bridge, putting this tooling inside a broader agent workflow shift. (developer.apple.com)
Model Context Protocol is a standard way for an AI tool to ask software for context and actions, instead of scraping text or guessing from files. Sentry’s XcodeBuildMCP applies that pattern to iOS and macOS projects. (modelcontextprotocol.io) (github.com) XcodeBuildMCP is not an official MCP release from the protocol maintainers. It is an open-source project from Sentry that describes itself as “a Model Context Protocol server and CLI” for work on iOS and macOS projects. (github.com) The tool exposes Xcode-related actions to agents through one package named `xcodebuildmcp`. Its docs say developers can run it as an MCP server with `xcodebuildmcp mcp` or use the same commands directly in Terminal and scripts. (github.com) Sentry’s setup guide lists two install paths: Homebrew with `brew tap getsentry/xcodebuildmcp && brew install xcodebuildmcp`, or npm with `npm install -g xcodebuildmcp@latest`. The same guide says the package needs macOS 14.5 or later and Xcode 16.x or later. (github.com) That matters because Apple has now documented its own Xcode-side bridge for outside agents. Apple says developers can enable “Allow external agents to use Xcode tools” in Xcode settings and connect agents through the `xcrun mcpbridge` command. (developer.apple.com) Apple’s documentation names Claude Code and Codex as examples, with commands that register Xcode as an MCP endpoint from Terminal. That means third-party agent tools no longer have to invent one-off integrations for basic Xcode access. (developer.apple.com) Sentry’s project sits on top of that broader shift by packaging iOS and macOS workflows into one agent-facing interface. Its release notes show recent work on client setup, environment-variable defaults, and fixes for Codex prompts, server shutdown, and CLI reliability. (github.com) The official MCP project has also published a Swift software development kit for building MCP clients and servers in Apple’s language. Its repository says the SDK supports both client and server components and targets Swift 6.0 and Xcode 16 or newer. (github.com) Taken together, the change is less about a new Apple app than a new plumbing layer. Xcode, external agents, and Swift tooling are starting to speak the same protocol for iPhone and Mac development. (developer.apple.com) (github.com)
