XcodeBuildMCP is an MCP server and command-line tool that gives coding agents tools for building and working on iOS and macOS projects. It supports workflows involving Xcode and xcodebuild, including project builds and device-related operations. Its catalogue add-ons provide agent instructions and connections for using the MCP server and CLI.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add getsentry/XcodeBuildMCP --skill xcodebuildmcpgit clone --depth 1 https://github.com/getsentry/XcodeBuildMCPWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/getsentry/xcodebuildmcp/xcodebuildmcp)<a href="https://agentmods.dev/skills/getsentry/xcodebuildmcp/xcodebuildmcp"><img src="https://agentmods.dev/badge/skills/getsentry/xcodebuildmcp/xcodebuildmcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/getsentry/xcodebuildmcp/xcodebuildmcp"><img src="https://agentmods.dev/badge/skills/getsentry/xcodebuildmcp/xcodebuildmcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00045 | $0.00557 |
| Opus 5.5 | $0.00018 | $0.00223 |
| Sonnet 5.5 | $0.00009 | $0.00111 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
xcodebuildmcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XcodeBuildMCP
Use XcodeBuildMCP tools instead of raw xcodebuild, xcrun, or simctl.
Capabilities:
- Session defaults: Configure project, scheme, simulator, and device defaults to avoid repetitive parameters
- Project discovery: Find Xcode projects/workspaces, list schemes, inspect build settings
- Simulator workflows: Build, run, test, install, and launch apps on iOS simulators; manage simulator state (boot, erase, location, appearance)
- Device workflows: Build, test, install, and launch apps on physical devices with code signing
- macOS workflows: Build, run, and test macOS applications
- Log capture: Stream and capture logs from simulators and devices
- LLDB debugging: Attach debugger, set breakpoints, inspect stack traces and variables, execute LLDB commands
- UI automation: Capture screenshots, inspect view hierarchy with coordinates, perform taps/swipes/gestures, type text, press hardware buttons
- SwiftPM: Build, run, test, and manage Swift Package Manager projects
- Project scaffolding: Generate new iOS/macOS project templates
Only simulator workflow tools are enabled by default. If capabilities like device, macOS, debugging, or UI automation are not available, the user must configure XcodeBuildMCP to enable them. See https://xcodebuildmcp.com/docs/configuration for workflow configuration.
Step 1: Establish Session Context
- Call
session_show_defaultsbefore the first build/run/test action in a session. - Use
discover_projsonly when defaults show missing or incorrect project/workspace context. - Do not run discovery speculatively or in parallel with
session_show_defaults. - For simulator run intent, prefer the combined build-and-run tool instead of separate build then run calls.
- Do not chain build-only then build-and-run unless the user explicitly requests both.
Step 2: Understand Workflow-Scoped Tool Availability
- Not all tools are enabled by default; tool availability depends on enabled workflows.
- If a tool is expected but missing, check enabled workflows first.
- Update enabled workflows in
.xcodebuildmcp/config.yaml, then ask user to reload/restart the session to surface refreshes.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 42 lines · 45 tokens per session scan A 65a3f355f6d4
xcodebuildmcp is a skill published in the GitHub repository getsentry/XcodeBuildMCP (6,474 stars, last pushed 7d ago), licensed MIT. It adds 45 tokens to every session and 557 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
melaya-setup
Use for anything involving Melaya. Connecting for the first time; setting up phone or browser control; pairing a phone, installing the app, starting the local runner; driving an Android phone or a browser; building, validating, scheduling or debugging agent pipelines; reading connected services; diagnosing a failed…
rn-expo
The RN/Expo dev-build recipe for adb-mcp — adbreverse before launching (or the dev client silently runs its embedded bundle), appstate to confirm it is on Metro, on the RIGHT Metro, and not serving stale JavaScript after a git checkout, then reloadapp. Use whenever driving a React Native or Expo dev build, or when…
crash-triage
Using logcat to surface the real "Caused by:" root cause hidden behind a generic UI error, plus app lifecycle tools for reproducing failures. Use when an app crashes, shows a generic error dialog, or a task needs to find why a native call failed.
driving
The core observe→locate→act→re-observe loop for driving an Android UI with adb-mcp — true-pixel coordinates, and gotchas like overlays eating taps, keyboards covering buttons, and settle delays. Use whenever tapping, swiping, typing, or otherwise interacting with an Android screen.
getting-started
How to list AVDs, boot an emulator, target a device with the serial argument, and run a first interaction with adb-mcp. Use when starting a new Android automation task, or when no device/emulator is booted yet.
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…