# Mobilebuildmcp Cli

> Official skill for the MobileBuildMCP CLI.

Official skill for the MobileBuildMCP CLI. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).

- Page: https://ss33.ai/skills/getsentry/mobilebuildmcp-cli-63608900601
- Publisher: getsentry
- Category: [Software Development](https://ss33.ai/skills/category/software-development-t44z8z) › [Mobile apps](https://ss33.ai/skills/category/software-development-t44z8z/mobile-apps-p8puwc)
- License: MIT
- Source: https://github.com/getsentry/mobilebuildmcp/blob/d13ff0c707b0681769cf31da0eb42c4f94ceafff/skills/mobilebuildmcp-cli/SKILL.md

## Skill

SKILL.md: https://ss33.ai/api/v1/ss33/download/getsentry/mobilebuildmcp-cli-63608900601

# 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.