XcodeBuildMCP
Drive Xcode builds, simulators, and project discovery from your agent on macOS via a local stdio MCP package instead of memorizing xcodebuild flags.
Overview
com.xcodebuildmcp/XcodeBuildMCP is a MCP server for the Build phase that exposes Xcode project, simulator, and app utility operations to your agent over local stdio.
What is this MCP server?
- stdio MCP via npx xcodebuildmcp (npm registry package 2.6.2)
- Workflow slices configurable with XCODEBUILDMCP_ENABLED_WORKFLOWS (simulator, device, project-discovery)
- Optional incremental builds via INCREMENTAL_BUILDS_ENABLED and experimental xcodemake path
- Environment toggles for debug logging and Sentry reporting (XCODEBUILDMCP_SENTRY_DISABLED)
- Package version 2.6.2 on npm identifier xcodebuildmcp
- stdio local transport (not hosted remote)
- Workflow filter via XCODEBUILDMCP_ENABLED_WORKFLOWS comma list
Community signal: 5.9k GitHub stars.
What problem does it solve?
Indie iOS developers lose flow context when they bounce between the agent and Terminal to run xcodebuild, pick simulators, and probe project settings manually.
Who is it for?
Solo builders on macOS actively developing Xcode-based mobile or desktop apps who want agent-driven builds and simulator control.
Skip if: Windows/Linux-only workflows, pure backend API services with no Apple target, or teams that refuse local Xcode installs.
What do I get? / Deliverables
After registering the stdio server with npx xcodebuildmcp, your agent can invoke workflow-scoped tools to build, explore projects, and manage simulators from the same chat session.
- Agent-invokable Xcode build and simulator workflows
- Configurable workflow loading at MCP startup
- Faster edit-build-run loops without leaving the agent
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the server exists to manipulate Xcode projects, run builds, and manage simulators while you are implementing the iOS or macOS product. Frontend fits native Apple UI work—the tooling targets app targets, simulators, and Xcode project structure rather than backend APIs or infra deploys.
How it compares
Local Xcode devtools MCP over stdio, not a cloud deploy or cross-platform Flutter skill.
Common Questions / FAQ
Who is com.xcodebuildmcp/XcodeBuildMCP for?
It is for macOS developers building with Xcode who want MCP-aware agents to manage projects, simulators, and related app utilities during implementation.
When should I use com.xcodebuildmcp/XcodeBuildMCP?
Use it in the Build phase while you are compiling, debugging on simulators or devices, and navigating Xcode project structure from your agent.
How do I add com.xcodebuildmcp/XcodeBuildMCP to my agent?
Add an MCP server entry with stdio transport, command npx and package xcodebuildmcp@2.6.2, set optional env vars like XCODEBUILDMCP_ENABLED_WORKFLOWS, and ensure Xcode is installed on the Mac host.