Skip to main content
hc
Submit
mcpSource-backed
XcodeBuildMCP logo

XcodeBuildMCP Server

MCP server and CLI for AI-assisted iOS and macOS development with Xcode project discovery, simulator management, builds, tests, app utilities, and device workflows.

by Sentry · submitted by oktofeesh1·added 2026-06-05·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/mcp/xcodebuildmcp-server
Source URLs
https://xcodebuildmcp.com/docs, https://github.com/getsentry/XcodeBuildMCP, https://www.xcodebuildmcp.com
Brand
XcodeBuildMCP
Brand domain
xcodebuildmcp.com
Brand asset source
brandfetch
Safety notes
XcodeBuildMCP can build, test, launch, inspect, and manage simulator or device app workflows., Device operations may depend on code signing, provisioning profiles, bundle identifiers, and Apple developer account configuration., Build and test logs can reveal secrets, internal endpoints, customer fixtures, signing errors, and unreleased product details., Require human review before allowing an agent to change signing settings, delete derived data, run device workflows, or modify project configuration.
Privacy notes
Project paths, scheme names, bundle identifiers, build logs, simulator logs, test output, screenshots, crash data, and device details may be sent to the MCP client and model., The README says XcodeBuildMCP uses Sentry for internal runtime error telemetry and links to opt-out instructions., Review telemetry settings and model-provider retention before using the tool on proprietary or regulated apps.
Author
Sentry
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

15 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

5 to clear

Platforms

4 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Have accounts and credentials ready first.

0/5 ready
Account & credentials1Install & runtime1Configuration1General215 minutes

Safety & privacy surface

Safety & privacy surface

4 safety and 3 privacy notes across 5 risk areas. Review closely: credentials & tokens, third-party handling.

5 areas
  • SafetyGeneralXcodeBuildMCP can build, test, launch, inspect, and manage simulator or device app workflows.
  • SafetyLocal filesDevice operations may depend on code signing, provisioning profiles, bundle identifiers, and Apple developer account configuration.
  • SafetyCredentials & tokensBuild and test logs can reveal secrets, internal endpoints, customer fixtures, signing errors, and unreleased product details.
  • SafetyExecution & processesRequire human review before allowing an agent to change signing settings, delete derived data, run device workflows, or modify project configuration.
  • PrivacyThird-party handlingProject paths, scheme names, bundle identifiers, build logs, simulator logs, test output, screenshots, crash data, and device details may be sent to the MCP client and model.
  • PrivacyExecution & processesThe README says XcodeBuildMCP uses Sentry for internal runtime error telemetry and links to opt-out instructions.
  • PrivacyThird-party handlingReview telemetry settings and model-provider retention before using the tool on proprietary or regulated apps.

Safety notes

  • XcodeBuildMCP can build, test, launch, inspect, and manage simulator or device app workflows.
  • Device operations may depend on code signing, provisioning profiles, bundle identifiers, and Apple developer account configuration.
  • Build and test logs can reveal secrets, internal endpoints, customer fixtures, signing errors, and unreleased product details.
  • Require human review before allowing an agent to change signing settings, delete derived data, run device workflows, or modify project configuration.

Privacy notes

  • Project paths, scheme names, bundle identifiers, build logs, simulator logs, test output, screenshots, crash data, and device details may be sent to the MCP client and model.
  • The README says XcodeBuildMCP uses Sentry for internal runtime error telemetry and links to opt-out instructions.
  • Review telemetry settings and model-provider retention before using the tool on proprietary or regulated apps.

Prerequisites

  • macOS 14.5 or later.
  • Xcode 16 or later.
  • Node.js 18 or later for the npm or npx path, unless installing through Homebrew.
  • Xcode project, workspace, simulator, or device target the agent is authorized to build and test.
  • Code signing configured in Xcode for physical-device workflows.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
15 minutes
Difficulty
intermediate
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "XcodeBuildMCP": {
      "command": "npx",
      "args": ["-y", "xcodebuildmcp@latest", "mcp"]
    }
  }
}

About this resource

Content

XcodeBuildMCP is a Model Context Protocol server and CLI for iOS and macOS projects. It gives AI coding agents a structured way to discover Xcode projects, build and test schemes, manage simulators, launch apps, inspect logs, and work with device-oriented app utilities.

The package ships as one tool with two modes: an MCP server for AI agents and a CLI for direct terminal use. The docs include drop-in configs for Claude Code, Codex, Cursor, Claude Desktop, VS Code, Windsurf, Kiro, Trae, Xcode agents, and other clients.

Source Review

These sources were reviewed on 2026-06-05. Prefer the live documentation for current client snippets, tool names, Xcode requirements, telemetry settings, device signing guidance, and CLI behavior.

Features

  • MCP server and CLI modes from the same package.
  • Project and workspace discovery for iOS and macOS codebases.
  • Simulator build, test, launch, and app utility workflows.
  • Device workflows when signing is configured.
  • Tools reference and workflow docs for common Xcode tasks.
  • Optional agent skills for MCP and CLI usage.
  • Homebrew and npm installation paths.

Installation

Install globally with npm:

npm install -g xcodebuildmcp@latest
xcodebuildmcp mcp

Or configure an MCP client to launch the server on demand:

{
  "mcpServers": {
    "XcodeBuildMCP": {
      "command": "npx",
      "args": ["-y", "xcodebuildmcp@latest", "mcp"]
    }
  }
}

Homebrew users can install from the documented tap and run xcodebuildmcp mcp directly. Follow the client docs for Claude Code, Codex, Cursor, Claude Desktop, VS Code, Windsurf, Kiro, Trae, and Xcode agent setup.

Use Cases

  • Ask an agent to discover an Xcode workspace and available schemes.
  • Build and test an iOS app on a simulator from a coding assistant.
  • Launch an app, inspect logs, and iterate on UI or integration failures.
  • Run CLI workflows directly when debugging agent-generated commands.
  • Use device workflows after provisioning and signing are configured.

Safety and Privacy

Xcode build and test output often contains sensitive implementation details. Review build logs, test logs, screenshots, crash output, and device metadata before sharing them outside approved systems. Keep signing and provisioning changes under human control.

The project documents Sentry runtime error telemetry. Review the privacy docs and opt-out settings before using XcodeBuildMCP on confidential applications or regulated projects.

Duplicate Check

No getsentry/XcodeBuildMCP entry or source URL was found in content/mcp. This entry is separate from generic terminal, filesystem, and browser automation MCP servers because it focuses on Xcode, iOS, macOS, simulator, and device app workflows.

#xcode#ios#macos#testing#simulator

Source citations

Add this badge to your README

Show that XcodeBuildMCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/xcodebuildmcp-server.svg)](https://heyclau.de/entry/mcp/xcodebuildmcp-server)

How it compares

XcodeBuildMCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field
XcodeBuildMCP logoXcodeBuildMCP Server

MCP server and CLI for AI-assisted iOS and macOS development with Xcode project discovery, simulator management, builds, tests, app utilities, and device workflows.

Open dossier
agent-device logoAgent Device MCP Server

Official MCP server for agent-device, Callstack's device automation CLI for inspecting, controlling, debugging, recording, and collecting evidence from iOS, Android, TV, macOS, Linux, React Native, Expo, Flutter, and native apps.

Open dossier
iOS Simulator MCP Server

MCP server for controlling iOS simulators from AI agents, including simulator discovery, UI taps, typing, swipes, accessibility inspection, screenshots, video recording, app install, and app launch.

Open dossier
HttpRunner logoHttpRunner UIXT MCP Server

MCP server from HttpRunner that exposes UIXT device and browser automation tools for Android, iOS, Harmony, and Web testing through the `hrp mcp-server` command.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandXcodeBuildMCP logoXcodeBuildMCPagent-device logoagent-device—HttpRunner logoHttpRunner
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorSentryCallstackJoshua Yoesdebugtalk
Added2026-06-052026-06-062026-06-052026-06-06
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓XcodeBuildMCP can build, test, launch, inspect, and manage simulator or device app workflows. Device operations may depend on code signing, provisioning profiles, bundle identifiers, and Apple developer account configuration. Build and test logs can reveal secrets, internal endpoints, customer fixtures, signing errors, and unreleased product details. Require human review before allowing an agent to change signing settings, delete derived data, run device workflows, or modify project configuration.✓Agent Device MCP exposes structured tools backed by `AgentDeviceClient`; the docs state it does not expose generic shell execution over MCP. Tools and CLI workflows can open apps, inspect UI, tap, type, scroll, perform gestures, wait, assert state, handle alerts, and close sessions. Evidence workflows can capture screenshots, recordings, logs, traces, network traffic, performance samples, crash context, React profiles, and replay files. Mutating commands should run serially against one session, and separate sessions or devices should be used for parallel work. Prefer dedicated test devices or simulators, and require approval before entering credentials, submitting forms, changing settings, installing apps, sending messages, or touching production accounts.✓Use version 1.3.3 or newer. The upstream security policy documents command-injection vulnerabilities in older versions and states that they were fixed in v1.3.3. The server invokes simulator, IDB, and host commands to tap, type, swipe, screenshot, record video, install apps, launch apps, and stop recordings. Filter high-risk or noisy tools with `IOS_SIMULATOR_MCP_FILTERED_TOOLS` when an agent should only inspect UI state. App install and launch tools can execute simulator app code, change simulator state, and interact with test credentials or local development services. Screenshots and recordings can overwrite or create files in configured output directories; review paths before letting an agent write artifacts.✓HttpRunner UIXT MCP Server can control real devices and browsers through taps, swipes, text input, hardware buttons, selectors, OCR, CV, and AI action tools. App tools can launch, terminate, cold launch, install, uninstall, clear data, and inspect foreground apps on connected devices. Screen tools can capture screenshots, screen recordings, screen size, and UI hierarchy/source data. Media and utility tools can modify test-device albums, close popups, wait randomly, and interact with system UI state. Simulated gesture options and anti-risk-style behavior should be used only in authorized test automation environments. Require human review before running actions against logged-in accounts, payment flows, device settings, production apps, or customer data.
Privacy notes✓Project paths, scheme names, bundle identifiers, build logs, simulator logs, test output, screenshots, crash data, and device details may be sent to the MCP client and model. The README says XcodeBuildMCP uses Sentry for internal runtime error telemetry and links to opt-out instructions. Review telemetry settings and model-provider retention before using the tool on proprietary or regulated apps.✓Screenshots, recordings, traces, logs, network dumps, replay files, reports, UI snapshots, typed input, and React profiles can contain private UI state, tokens, request data, customer information, or credentials. macOS, iOS, Android, and TV automation can expose local app state, notifications, device names, package identifiers, app content, system dialogs, and permission prompts. Network inspection artifacts may include headers, payloads, session identifiers, URLs, and API data; review before sharing or committing. Interactive CLI runs may check npm for newer package versions unless `AGENT_DEVICE_NO_UPDATE_NOTIFIER=1` is set.✓Tool results may expose app screens, accessibility labels, text fields, screenshots, videos, bundle identifiers, simulator UDIDs, file paths, output directories, app paths, and environment variables. Simulator apps may contain test accounts, customer fixtures, tokens, unreleased UI, internal URLs, logs, or private feature flags. MCP transcripts, client logs, screenshots, videos, and saved artifacts can retain sensitive UI and app-state data outside the simulator. Do not share recordings, screenshots, simulator data, app bundles, UDIDs, or output directories from proprietary apps unless the team has approved that disclosure.✓Screenshots, screen recordings, UI hierarchy, package names, foreground app names, OCR text, selector data, and logs can expose sensitive app or account state. Connected device identifiers, serial numbers, app package names, browser pages, and test artifacts may be visible to the MCP client. Input and paste actions can expose credentials, one-time codes, chat text, forms, or clipboard-like data if used on personal sessions. Test reports, MCP responses, and debugging logs may retain captured UI state after the session ends. Keep test devices resettable, avoid personal accounts, and isolate artifacts produced by automated UI runs.
Prerequisites
  • macOS 14.5 or later.
  • Xcode 16 or later.
  • Node.js 18 or later for the npm or npx path, unless installing through Homebrew.
  • Xcode project, workspace, simulator, or device target the agent is authorized to build and test.
  • Node.js 22 or newer and `agent-device` installed globally or project-locally.
  • Xcode tooling for iOS, tvOS, or macOS targets, or Android SDK and ADB for Android targets.
  • Device, simulator, emulator, TV, macOS, or Linux desktop target that the agent is allowed to automate.
  • Required local permissions such as Android device trust, iOS Developer Mode, macOS Accessibility, and Screen Recording where applicable.
  • macOS with Xcode and iOS simulators installed.
  • Node.js and npx available for running the npm package.
  • Facebook IDB installed and available on PATH, or configured through `IOS_SIMULATOR_MCP_IDB_PATH`.
  • A booted simulator, or permission for the agent to open and interact with Simulator.
  • Go 1.23 or newer for building the current v5 CLI from source.
  • A test Android, iOS, Harmony, or browser automation environment configured for HttpRunner UIXT.
  • A trusted MCP client that can launch local stdio servers.
  • Review of ADB, go-ios, WebDriver, OCR, computer-vision, and AI-action dependencies required by your target platform.
Install
npm install -g xcodebuildmcp@latest
claude mcp add --transport stdio --scope user agent-device -- agent-device mcp
claude mcp add ios-simulator -- npx -y ios-simulator-mcp
git clone https://github.com/httprunner/httprunner.git && cd httprunner && go build -o hrp ./cmd/cli
Config
{
  "mcpServers": {
    "XcodeBuildMCP": {
      "command": "npx",
      "args": ["-y", "xcodebuildmcp@latest", "mcp"]
    }
  }
}
{
  "mcpServers": {
    "agent-device": {
      "command": "agent-device",
      "args": ["mcp"]
    }
  }
}
{
  "mcpServers": {
    "ios-simulator": {
      "command": "npx",
      "args": ["-y", "ios-simulator-mcp"],
      "env": {
        "IOS_SIMULATOR_MCP_FILTERED_TOOLS": "screenshot,record_video,stop_recording",
        "IOS_SIMULATOR_MCP_DEFAULT_OUTPUT_DIR": "SIMULATOR_OUTPUT_DIR",
        "IOS_SIMULATOR_MCP_IDB_PATH": "IDB_EXECUTABLE_PATH"
      }
    }
  }
}
{
  "mcpServers": {
    "httprunner-uixt": {
      "command": "hrp",
      "args": [
        "mcp-server"
      ],
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.