developer-tools

XcodeBuild MCP

Sentry

by Sentry

By Sentry. MCP server and CLI that provides tools for AI agents working on iOS and macOS Xcode projects. Build, test, li

By Sentry. MCP server and CLI that provides tools for AI agents working on iOS and macOS Xcode projects. Build, test, lint, resolve packages, and manage simulators. 4,500+ GitHub stars.

github stars

4.6K

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

Built by Sentry team4,500+ GitHub starsWorks as both CLI and MCP server

best for

  • / iOS/macOS developers using AI coding assistants
  • / Automating Xcode project builds and testing
  • / AI agents working on Swift/Objective-C projects

capabilities

  • / Build iOS and macOS Xcode projects
  • / Run unit and UI tests
  • / Lint Swift code
  • / Resolve Swift Package Manager dependencies
  • / Manage iOS simulators
  • / Execute xcodebuild commands

what it does

Provides AI agents with tools to build, test, and manage iOS/macOS Xcode projects through command-line integration.

about

XcodeBuild MCP is an official MCP server published by Sentry that provides AI assistants with tools and capabilities via the Model Context Protocol. By Sentry. MCP server and CLI that provides tools for AI agents working on iOS and macOS Xcode projects. Build, test, li It is categorized under developer tools.

how to install

You can install XcodeBuild MCP in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

license

MIT

XcodeBuild MCP is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

readme

XcodeBuild MCP A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects. [![CI](https://github.com/getsentry/XcodeBuildMCP/actions/workflows/ci.yml/badge.svg)](https://github.com/getsentry/XcodeBuildMCP/actions/workflows/ci.yml) [![npm version](https://badge.fury.io/js/xcodebuildmcp.svg)](https://badge.fury.io/js/xcodebuildmcp) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![Node.js](https://img.shields.io/badge/node->=18.x-brightgreen.svg)](https://nodejs.org/) [![Xcode 16](https://img.shields.io/badge/Xcode-16-blue.svg)](https://developer.apple.com/xcode/) [![macOS](https://img.shields.io/badge/platform-macOS-lightgrey.svg)](https://www.apple.com/macos/) [![MCP](https://img.shields.io/badge/MCP-Compatible-green.svg)](https://modelcontextprotocol.io/) [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/getsentry/XcodeBuildMCP) [![AgentAudit Security](https://img.shields.io/badge/AgentAudit-Safe-brightgreen?logo=data:image/svg%2Bxml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNCAyNCI+PHBhdGggZmlsbD0id2hpdGUiIGQ9Ik0xMiAxTDMgNXY2YzAgNS41NSAzLjg0IDEwLjc0IDkgMTIgNS4xNi0xLjI2IDktNi40NSA5LTEyVjVsLTktNHoiLz48L3N2Zz4=)](https://www.agentaudit.dev/skills/xcodebuildmcp) ## Installation XcodeBuildMCP ships as a single package with two modes: a **CLI** for direct terminal use and an **MCP server** for AI coding agents. Both installation methods give you both modes. ### Option A — Homebrew ```bash brew tap getsentry/xcodebuildmcp brew install xcodebuildmcp ``` Use the CLI: ```bash xcodebuildmcp --help ``` MCP client config: ```json "XcodeBuildMCP": { "command": "xcodebuildmcp", "args": ["mcp"] } ``` Upgrade later with `brew update && brew upgrade xcodebuildmcp`. ### Option B — npm / npx (Node.js 18+) **For CLI use**, install globally: ```bash npm install -g xcodebuildmcp@latest xcodebuildmcp --help ``` **For MCP server only**, no global install needed — add directly to your client config: ```json "XcodeBuildMCP": { "command": "npx", "args": ["-y", "xcodebuildmcp@latest", "mcp"] } ``` To pin a specific version, replace `@latest` with an exact version (e.g. `xcodebuildmcp@latest`). ### Client-specific setup The examples below use npx (Option B). If you installed via Homebrew, replace the command with `"command": "xcodebuildmcp", "args": ["mcp"]` instead.
Cursor
Recommended (project-scoped): add `.cursor/mcp.json` in your workspace root: ```json { "mcpServers": { "XcodeBuildMCP": { "command": "npx", "args": ["-y", "xcodebuildmcp@latest", "mcp"] } } } ``` For global Cursor config (`~/.cursor/mcp.json`), use this variant so startup is aligned with the active workspace: ```json { "mcpServers": { "XcodeBuildMCP": { "command": "/bin/zsh", "args": [ "-lc", "cd "${workspaceFolder}" && exec npx -y xcodebuildmcp@latest mcp" ] } } } ``` Or use the quick install link: [![Install MCP Server](https://cursor.com/deeplink/mcp-install-light.svg)](https://cursor.com/en-US/install-mcp?name=XcodeBuildMCP&config=eyJjb21tYW5kIjoibnB4IC15IHhjb2RlYnVpbGRtY3BAbGF0ZXN0IG1jcCJ9)
Claude Code
Run: ```bash claude mcp add XcodeBuildMCP -- npx -y xcodebuildmcp@latest mcp ```
Codex CLI
Run: ```bash codex mcp add XcodeBuildMCP -- npx -y xcodebuildmcp@latest mcp ``` Or add to `~/.codex/config.toml`: ```toml [mcp_servers.XcodeBuildMCP] command = "npx" args = ["-y", "xcodebuildmcp@latest", "mcp"] ```
Claude Desktop
Add to `~/Library/Application Support/Claude/claude_desktop_config.json`: ```json { "mcpServers": { "XcodeBuildMCP": { "command": "npx", "args": ["-y", "xcodebuildmcp@latest", "mcp"] } } } ```
VS Code / VS Code Insiders
Add to your VS Code settings JSON: ```json "mcp": { "servers": { "XcodeBuildMCP": { "command": "npx", "args": ["-y", "xcodebuildmcp@latest", "mcp"] } } } ``` Or use the quick install links: [![Install in VS Code](https://img.shields.io/badge/VS_Code-XcodeBuildMCP-0098FF?style=flat&logo=visualstudiocode&logoColor=ffffff)](vscode:mcp/install?%7B%22name%22%3A%22XcodeBuildMCP%22%2C%22type%22%3A%22stdio%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22xcodebuildmcp%40latest%22%2C%22mcp%22%5D%7D) [![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-XcodeBuildMCP-24bfa5?style=flat&logo=visualstudiocode&logoColor=ffffff)](vscode-insiders:mcp/install?%7B%22name%22%3A%22XcodeBuildMCP%22%2C%22type%22%3A%22stdio%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22xcodebuildmcp%40latest%22%2C%22mcp%22%5D%7D)
Kiro / Kiro CLI
**Workspace-level** (applies only to the current workspace): add `.kiro/settings/mcp.json` in your project root: ```json { "mcpServers": { "XcodeBuildMCP": { "command": "npx", "args": ["-y", "xcodebuildmcp@latest", "mcp"] } } } ``` **User-level** (applies globally across all workspaces): add to `~/.kiro/settings/mcp.json`: ```json { "mcpServers": { "XcodeBuildMCP": { "command": "npx", "args": ["-y", "xcodebuildmcp@latest", "mcp"] } } } ```
Windsurf
Add to `~/.codeium/windsurf/mcp_config.json`: ```json { "mcpServers": { "XcodeBuildMCP": { "command": "npx", "args": ["-y", "xcodebuildmcp@latest", "mcp"] } } } ```
Trae
Add to `~/Library/Application Support/Trae/User/mcp.json`: ```json { "mcpServers": { "XcodeBuildMCP": { "command": "npx", "args": ["-y", "xcodebuildmcp@latest", "mcp"] } } } ```
Xcode (Codex Agent)
Requires Xcode 26.3 or later. Codex agent must be installed and configured in Xcode Settings -> Intelligence -> Open AI. The only way at the time of writing to add an MCP server is to use a project scoped `.codex/config.toml` file in the root of your project workspace: `/path/to/your/project/.codex/config.toml` ```toml [mcp_servers.XcodeBuildMCP] args = [ "-lc", "PATH=/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin; export NVM_DIR="$HOME/.nvm"; [ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"; nvm use --silent >/dev/null 2>&1 || true; npx -y xcodebuildmcp@latest mcp" ] command = "/bin/zsh" enabled = true tool_timeout_sec = 10000 ``` > **NOTE**: > Codex Agent when running in Xcode has a limited PATH by default. The above example should work for most users but if you find the server doesn't start or is not available, it's likely because npx is not found so you might have to adjust the above configuration accordingly.
Xcode (Claude Code Agent)
Requires Xcode 26.3 or later. Claude Code agent must be installed and configured in Xcode Settings -> Intelligence -> Anthropic. Add to the end or replace the existing `mcpServers` object in Xcode's Claude Code agent config at: `~/Library/Developer/Xcode/CodingAssistant/ClaudeAgentConfig/.claude.json` ```json // ... rest of file ... "mcpServers": { "XcodeBuildMCP": { "command": "/bin/zsh", "args": [ "-lc", "PATH=/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin; export NVM_DIR="$HOME/.nvm"; [ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"; nvm use --silent >/dev/null 2>&1 || true; npx -y xcodebuildmcp@latest mcp" ] } } } ``` > **NOTE**: > Claude Code Agent when running in Xcode has a limited PATH by default. The above example should work for most users but if you find the server doesn't start or is not available, it's likely because npx is not found so you might have to adjust the above configuration accordingly.
AdaL CLI
Run the following command inside the AdaL CLI prompt: ```console /mcp add XcodeBuildMCP --command npx --args "-y,xcodebuildmcp@latest,mcp" ```

For other installation options see [Getting Started](docs/GETTING_STARTED.md). ## Requirements - macOS 14.5 or later - Xcode 16.x or later - Node.js 18.x or later (not required for Homebrew installation) ## Skills XcodeBuildMCP now includes two optional agent skills: - **MCP Skill**: Primes the agent with instructions on how to use the MCP server's tools (optional when using the MCP server). - **CLI Skill**: Primes the agent with instructions on how to navigate the CLI (recommended when using the CLI). To install with a global binary: ```bash xcodebuildmcp init ``` Or install directly via npx without a global install: ```bash npx -y xcodebuildmcp@latest init ``` For further information on installing skills, see: [docs/SKILLS.md](docs/SKILLS.md) ## Notes - XcodeBuildMCP requests xcodebuild to skip macro validation to avoid errors when building projects that use Swift Macros. - Device tools require code signing to be configured in Xcode. See [docs/DEVICE_CODE_SIGNING.md](docs/DEVICE_CODE_SIGNING.md). ## Privacy XcodeBuildMCP uses Sentry for internal runtime error telemetry only. For details and opt-out instructions, see [docs/PRIVACY.md](docs/PRIVACY. ---

FAQ

What is the XcodeBuild MCP MCP server?
XcodeBuild MCP is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for XcodeBuild MCP?
This profile displays 68 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.6 out of 5—verify behavior in your own environment before production use.

Use Cases

Extended AI Capabilities

Add new capabilities to Claude beyond text generation

Example

Access external data sources, execute code, interact with tools and services

Transform Claude from chatbot to action-taking agent

Context Enhancement

Provide Claude with access to relevant context and data

Example

Load project documentation, access knowledge bases, query databases

Get more accurate, context-aware responses

Workflow Automation

Automate multi-step workflows combining AI and external tools

Example

Research → Summarize → Create document → Send notification

Complete complex tasks end-to-end without manual steps

Implementation Guide

Prerequisites

  • Claude Desktop 0.7.0+ or Cursor IDE with MCP support
  • Basic understanding of MCP architecture and capabilities
  • Access credentials for integrated services (if required)
  • Willingness to experiment and iterate on configuration

Time Estimate

15-60 minutes depending on server complexity

Installation Steps

  1. 1.Install MCP server: npm install -g [package-name] or via GitHub
  2. 2.Add server configuration to ~/.claude/mcp.json
  3. 3.Provide required credentials and configuration
  4. 4.Restart Claude Desktop to load new server
  5. 5.Test basic functionality with simple prompts
  6. 6.Explore capabilities and experiment with use cases
  7. 7.Document successful patterns for reuse

Troubleshooting

  • MCP server not loading: Check config syntax, verify installation
  • Connection errors: Check network, firewall, credentials
  • Feature not working: Read server docs, check required parameters
  • Performance issues: Monitor resource usage, check for network latency
  • Conflicts with other servers: Check port assignments, namespace collisions

Best Practices

✓ Do

  • +Read server documentation thoroughly before setup
  • +Start with simple use cases to validate functionality
  • +Test in non-production environment first
  • +Monitor resource usage and performance
  • +Keep servers updated for bug fixes and new features
  • +Document configuration for team members
  • +Use environment variables for sensitive configuration

✗ Don't

  • Don't grant overly permissive access to MCP servers
  • Don't skip reading security considerations in docs
  • Don't expose sensitive data without proper controls
  • Don't run untrusted MCP servers without code review
  • Don't ignore error messages—investigate root cause

💡 Pro Tips

  • Combine multiple MCP servers for powerful workflows
  • Create custom MCP servers for your specific needs
  • Share successful configurations with team
  • Use MCP inspector for debugging
  • Join MCP community for tips and troubleshooting

Technical Details

Architecture

Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.

Protocols

  • Model Context Protocol (MCP)
  • JSON-RPC 2.0
  • stdio or HTTP transport

Compatibility

  • Claude Desktop
  • Cursor IDE
  • Custom MCP clients

When to Use This

✓ Use When

Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.

✗ Avoid When

Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.

Integration

  • Tool composition: Chain multiple MCP tools in workflows
  • Context augmentation: Provide AI with relevant external data
  • Action delegation: Let AI execute tasks on external systems
  • Bidirectional sync: Keep AI context and external systems in sync

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.668 reviews
  • Ren White· Dec 24, 2024

    XcodeBuild MCP has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Liam Tandon· Dec 16, 2024

    XcodeBuild MCP is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Yusuf Sharma· Dec 12, 2024

    Strong directory entry: XcodeBuild MCP surfaces stars and publisher context so we could sanity-check maintenance before adopting.

  • Diya Haddad· Dec 8, 2024

    XcodeBuild MCP is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Lucas Chawla· Nov 27, 2024

    We evaluated XcodeBuild MCP against two servers with overlapping tools; this profile had the clearer scope statement.

  • Layla Verma· Nov 23, 2024

    I recommend XcodeBuild MCP for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Olivia White· Nov 15, 2024

    Strong directory entry: XcodeBuild MCP surfaces stars and publisher context so we could sanity-check maintenance before adopting.

  • Diego Abbas· Nov 7, 2024

    We wired XcodeBuild MCP into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Evelyn Torres· Nov 7, 2024

    XcodeBuild MCP reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Liam Srinivasan· Nov 3, 2024

    XcodeBuild MCP has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

showing 1-10 of 68

1 / 7