⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

v2.7.1

mobilebuildmcp-docs-command-review

getsentry@getsentry⭐ 6.6k stars· last commit 24d ago· 18 open issues

Use when reviewing MobileBuildMCP changelog CLI command references for invalid current guidance while allowing historical migration examples.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐⭐⭐⭐ 6.6k on GitHubGitHub ↗

Very popular

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.

CI npm version License: MIT Node.js Xcode 16 macOS MCP Ask DeepWiki AgentAudit Security pkg.pr.new

Installation

MobileBuildMCP ships as a single package with two modes: a CLI for direct terminal use and an MCP server for AI coding agents. Either install method gives you both.

Option A — Homebrew

brew tap getsentry/xcodebuildmcp
brew install mobilebuildmcp

Option B — npm (Node.js 18+)

npm install -g mobilebuildmcp@latest

Verify either install:

mobilebuildmcp --help

Connect your MCP client

Drop-in config snippets for Cursor, Claude Code, Codex, can be found in the official docs page MCP Clients. Most clients can also run the MCP server on demand via npx -y mobilebuildmcp@latest mcp without a global install.

Requirements

  • macOS 14.5 or later
  • Xcode 16.x or later
  • Node.js 18.x or later (not required for Homebrew installation)

Skills

MobileBuildMCP 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:

mobilebuildmcp init

Or install directly via npx without a global install:

npx -y mobilebuildmcp@latest init

For further information on installing skills, see Agent Skills.

Notes

  • MobileBuildMCP 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 Device Code Signing.

Privacy

MobileBuildMCP uses Sentry for internal runtime error telemetry only. For details and opt-out instructions, see Privacy & Telemetry.

CLI

MobileBuildMCP provides a unified command-line interface. The mcp subcommand starts the MCP server, while all other commands provide direct terminal access to tools:

# Install globally
npm install -g mobilebuildmcp@latest

# Start the MCP server (for MCP clients)
mobilebuildmcp mcp

# List available tools
mobilebuildmcp tools

# Build for simulator
mobilebuildmcp simulator build --scheme MyApp --project-path ./MyApp.xcodeproj

# Prepare portable test products without running tests
mobilebuildmcp simulator build --scheme MyApp --project-path ./MyApp.xcodeproj --simulator-name "iPhone 17" --build-for-testing --test-products-path ./MyApp.xctestproducts

# Run previously prepared test products
mobilebuildmcp simulator test --test-products-path ./MyApp.xctestproducts --simulator-name "iPhone 17"

Check for updates and upgrade in place:

mobilebuildmcp upgrade --check
mobilebuildmcp upgrade --yes

The CLI uses a per-workspace daemon for stateful operations (log capture, debugging, etc.) that auto-starts when needed. See the CLI guide for full documentation.

Documentation

Licence

This project is licensed under the MIT License - see the LICENSE file for details. For third-party licensing notices see the THIRD_PARTY_LICENSES file for details. For npm package attributions see the THIRD_PARTY_PACKAGE_LICENSES file for details.

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • .agents/skills/mobilebuildmcp-docs-command-review/SKILL.md2.0 KBff4422e930a7upstream ↗
    ---
    name: mobilebuildmcp-docs-command-review
    description: Use when reviewing MobileBuildMCP changelog CLI command references for invalid current guidance while allowing historical migration examples.
    allowed-tools: Read Grep Glob
    ---
    
    # MobileBuildMCP Docs Command Review
    
    Review changed changelog entries for CLI command references that would mislead users or agents.
    
    ## What to inspect
    
    - `CHANGELOG.md`
    - `manifests/tools/*.yaml` and `manifests/workflows/*.yaml` when you need to verify current CLI workflow/tool names
    - `src/cli/**` only when command wiring is unclear from manifests
    
    ## Issue criteria
    
    Report a finding only when a command reference is presented as current guidance and appears invalid for the current CLI surface.
    
    ### High severity
    
    - A changelog bullet, example, or migration instruction tells users to run a removed or invalid `mobilebuildmcp` command as the current path.
    - A Breaking change mentions a removed command but does not give a valid replacement.
    - A command reference uses the wrong workflow/tool pairing in a way a user or agent would likely copy.
    
    ### Medium severity
    
    - A command reference is ambiguous enough that users may not know whether it is historical or current.
    - A migration example gives the right replacement but does not clearly label the old command as "Before", "old", "removed", or equivalent.
    
    ## Explicitly allowed
    
    Do not report removed commands when they are clearly historical context, especially in:
    
    - Breaking-change migration sections
    - "Before" examples paired with valid "After" examples
    - Already-released changelog sections describing past behavior
    
    Example that should not be reported:
    
    ```markdown
    Before:
    mobilebuildmcp logging start-sim-log-cap
    
    After:
    mobilebuildmcp simulator build-and-run
    ```
    
    ## Output
    
    For each finding, include:
    
    - Severity
    - File and line
    - The command reference
    - Why it reads as current guidance
    - Suggested replacement wording or command
    
    If all command references are historical or valid, report no findings.
    
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/getsentry-mobilebuildmcp-agents-skills-mobilebuildmcp-docs-command-review.md

// REPO STATS

6.6k stars
18 open issues
Last commit: 24d ago