A practical guide to XcodeBazelMCP, an MCP server and CLI for Bazel-based Apple development across builds, tests, simulators, devices, and debugging.
Press enter or click to view image in full size
TL;DR
XcodeBazelMCP exposes Bazel-based Apple workflows through an MCP server and a CLI.
It targets iOS, macOS, tvOS, watchOS, visionOS, and Swift Package Manager workflows.
The useful mental model is: workspace first, target second, workflow third.
The tool is strongest when you want repeatable build, run, test, simulator, device, and debugging operations from an AI-capable client.
Treat it as automation infrastructure, not magic. Your Bazel graph, Xcode install, simulator state, and device setup still matter.
Hook
Most iOS teams do not lose time because they forgot how to build an app. They lose time in the seams: finding the right Bazel target, booting the right simulator, passing the correct flags, rerunning one failing test, grabbing logs, installing on a physical device, or explaining all of that context to an AI coding tool.
That gap gets wider in Bazel-based Apple projects. Xcode is no longer the only source of truth. Your app is a target, your build graph is a queryable model, and “run the…
