Official skill for the MobileBuildMCP CLI. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
Pro shows the line behind each finding and how to fix it
Scanned 9/30/2026
npx -y skills add getsentry/XcodeBuildMCP --skill mobilebuildmcp-cli --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Mobilebuildmcp Cli?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/getsentry-mobilebuildmcp-cli)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: mobilebuildmcp-cli
description: Official skill for the MobileBuildMCP CLI. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
---
# MobileBuildMCP CLI
Use MobileBuildMCP tools via the `mobilebuildmcp` executable instead of raw `xcodebuild`, `xcrun`, or `simctl`.
## Step 1: Ensure the CLI Exists
Check availability:
```bash
mobilebuildmcp --help
```
If missing, install with one of:
```bash
brew tap getsentry/xcodebuildmcp
brew install mobilebuildmcp
```
```bash
npm install -g mobilebuildmcp@latest
```
Re-check after install:
```bash
mobilebuildmcp --help
```
## Step 2: Use Help-First Discovery
Discover workflows and arguments from the CLI itself:
```bash
mobilebuildmcp --help
mobilebuildmcp tools
mobilebuildmcp <workflow> --help
mobilebuildmcp <workflow> <tool> --help
```
Use this discovery path instead of memorizing static tool lists.
## Step 3: Keep Execution Minimal
- Choose the smallest command sequence that satisfies the request.
- Prefer direct workflow commands over manual multi-step chains unless explicitly requested.
- For simulator run intent, prefer the combined `build-and-run` command.
- Do not chain `build` then `build-and-run` unless explicitly requested.
## Capability Overview
`mobilebuildmcp` supports:
- simulator and device build/test/run
- debugging and log capture
- UI automation
- project discovery and scaffolding
- session defaults and workflow configuration
## Exit Criteria
- CLI presence is verified or installation steps are provided.
- Commands are discovered via `--help` / `tools`.
- Session defaults are checked before first build/run/test action.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!