A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
6.1k
Stars
302
Forks
22
Open issues
30
Contributors
AI Analysis
XcodeBuildMCP is a Model Context Protocol (MCP) server and CLI that enables AI agents and developers to automate iOS and macOS project builds through Xcode. It is purpose-built for developers working on Apple platforms who want to integrate Xcode tooling with AI coding agents, and is not suited for non-Apple platform development or general-purpose automation.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Sentry-built MCP server bridges AI coding agents with Xcode build tools for iOS/macOS development
XcodeBuildMCP is a Model Context Protocol server and CLI that exposes Xcode build, simulator, and device operations to AI coding agents (Claude Code, Cursor, Codex, etc.). It solves the practical gap between general-purpose LLM coding assistants and the Apple-specific toolchain (xcodebuild, simulators, device code signing). Built primarily for iOS and macOS developers who use AI-assisted workflows, it allows agents to build, run, and debug Apple platform apps without the developer manually orchestrating xcodebuild commands. Backed by Sentry, it has a dedicated documentation site, Homebrew tap, and npm package.
Created in March 2025, shortly after MCP (Model Context Protocol) gained traction as a standard for connecting LLMs to external tools. Sentry, a company with significant iOS SDK investment, built and open-sourced it — likely to improve their own internal developer tooling and to capture mindshare in the Apple-platform AI dev tools space.
Reached ~6K stars in roughly 15 months, driven by the broader MCP ecosystem boom and genuine scarcity of Apple-platform-specific MCP tooling. The 59 stars in 7 days as of late June 2026 reflects a steady but modest pace — not a viral spike. Growth likely correlates with adoption of AI coding agents among iOS/macOS developers, a demographic that has historically been underserved by AI tooling compared to web/backend developers.
Backed by Sentry (a production-grade company with real iOS SDK users), has a dedicated docs site at xcodebuildmcp.com, npm package, and Homebrew distribution. An AgentAudit security badge suggests third-party tooling awareness. Real-world adoption by individual developers appears plausible given client integrations with Cursor and Claude Code, but independent production usage data at scale is not documented in the README.
Appears to follow a dual-mode design: a single TypeScript package that can run as an MCP server (for agent integration) or as a CLI tool (for direct terminal use). Likely uses Node.js child process spawning to invoke xcodebuild and related Apple CLI tools under the hood. The daemon model mentioned for stateful CLI operations suggests a per-workspace process that persists log capture and debug state across invocations. MCP communication likely uses stdio transport based on how most MCP servers operate.
A CI badge is present in the README indicating automated testing exists, but specific test coverage metrics, frameworks used, or scope of tests are not documented in the README.
Last push was 2026-06-25, one day before the evaluation date — actively maintained. The project has a dedicated documentation website, versioned npm releases, a Homebrew tap, and an upgrade command, all suggesting sustained investment rather than a prototype. CI is visibly configured. Relative to June 2026, this project shows strong maintenance signals.
ADOPT IF: you are an iOS/macOS developer actively using AI coding agents (Claude Code, Cursor, Codex) and want them to autonomously build and run Apple platform projects without manual xcodebuild orchestration. AVOID IF: you work primarily on non-Apple platforms, need Windows/Linux CI integration, or are not yet using MCP-compatible AI agents in your workflow. MONITOR IF: you are an iOS developer curious about AI-assisted development but not yet committed to an MCP-enabled agent workflow — the tooling is maturing fast and adoption friction is decreasing.
Independent dimensions
Mainstream potential
4/10
Technical importance
7/10
Adoption evidence
4/10
- Hard dependency on macOS and Xcode versions — Apple's frequent breaking changes to xcodebuild CLI can disrupt functionality with each Xcode release cycle.
- MCP as a protocol is still relatively young; if competing standards emerge or major AI coding assistants adopt different tool-calling interfaces, the MCP server model could require significant rework.
- The addressable audience (iOS/macOS developers using AI coding agents with MCP support) is currently a subset of a subset — mainstream_potential is limited by platform exclusivity.
- Sentry's backing is a strength for now, but the project's long-term maintenance trajectory depends on whether Apple-platform tooling remains strategically important to Sentry's core business.
- Telemetry via Sentry SDK is built-in; developers working in sensitive or regulated environments need to actively opt out, which may be a barrier in some enterprise contexts.
Likely to remain the de facto MCP server for Apple platform build tooling as AI coding agent adoption grows among iOS developers. Mainstream ceiling is constrained by Apple platform exclusivity, but within that niche it appears well-positioned to consolidate.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://www.xcodebuildmcp.com
- Language
- TypeScript
- License
- MIT
- Last updated
- 24h ago
- Created
- 16mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
[Bug]: xcodemake incremental builds fails
Startup getSnapshot() on the critical path delays the first tools/list ~10s (health-probe clients show 'tools fetch failed')
Warden: code-review
snapshot_ui 'No translation object returned' persists across reboots on iOS 26.5 — root cause is a wedged host CoreSimulatorBridge; kill -9 fixes it
Xcode 27 beta: UI automation still fails because bundled AXe looks for SimulatorKit under PrivateFrameworks
Top contributors
Similar repos
microsoft/azure-devops-mcp
This is an MCP (Model Context Protocol) server integration for Azure DevOps...
mobile-next/mobile-mcp
Mobile MCP is a Model Context Protocol server that enables LLMs and agents to...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
getsentry/XcodeBuildMCP
this
|
6.1k | +36 | TypeScript | 8/10 | 24h ago |
 basementstudio/xmcp
|
1.3k | — | TypeScript | 7/10 | 1w ago |
|
microsoft/azure-devops-mcp
|
1.9k | — | TypeScript | 8/10 | 18h ago |
|
mobile-next/mobile-mcp
|
5.4k | — | TypeScript | 8/10 | 1w ago |
 mcp-use/mcp-use
|
10.3k | — | TypeScript | 8/10 | 12h ago |
|
microsoft/mcp
|
3.4k | — | C# | 7/10 | 2d ago |
mobile-mcp (5.3K stars) targets mobile automation more broadly including UI interaction, while XcodeBuildMCP focuses specifically on the build/compile/run pipeline for Apple platforms. They are partially complementary rather than direct substitutes.
The official MCP servers reference repo (87K stars) provides general-purpose integrations but has no Apple-platform build tooling. XcodeBuildMCP fills a gap the official project does not address.
Azure DevOps MCP targets CI/CD pipeline management in a cloud context. XcodeBuildMCP is local-machine focused and Apple-specific — different problem domains despite both being MCP servers.
Fastlane is the mature standard for iOS build automation but is not MCP-native and not designed for AI agent consumption. XcodeBuildMCP is purpose-built for agent interactions rather than human-authored automation scripts.
mcp-use (10K stars) is a framework for building MCP-using agents, not a domain-specific MCP server. Different abstraction level — mcp-use could consume XcodeBuildMCP as a tool server.
