agentleFS
Sign inStart free
cameroncookecameroncooke/XcodeBuildMCP/skills/mobilebuildmcp-cli/SKILL.md

mobilebuildmcp-cli

Skill6.5k starsChanged 50 days agoMITView on GitHub

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

  • Installs packages

2 other projects use a version of this.

Trending

Quiet since May.about the whole repository

Dec 2025: 1 mentionJan 2026: 4 mentionsFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the cameroncooke/XcodeBuildMCP repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about cameroncooke/XcodeBuildMCP

The biggest 5 of 21 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 21

Talked about on GitHub and Bluesky (21 times).

On GitHub · 17

12 more on GitHub

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use MobileBuildMCP tools via the mobilebuildmcp executable instead of raw xcodebuild, xcrun, or simctl.

    line 8
  2. Distinctive:

    If missing, install with one of:

    line 17
  3. Distinctive:

    Use this discovery path instead of memorizing static tool lists.

    line 42
  4. Distinctive:

    Prefer direct workflow commands over manual multi-step chains unless explicitly requested.

    line 47
  5. Very specific:

    Do not chain build then build-and-run unless explicitly requested.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

MobileBuildMCP CLI

Use MobileBuildMCP tools via the mobilebuildmcp executable instead of raw xcodebuild, xcrun, or simctl.

Step 1: Ensure the CLI Exists

Check availability:

mobilebuildmcp --help

If missing, install with one of:

brew tap getsentry/xcodebuildmcp
brew install mobilebuildmcp
npm install -g mobilebuildmcp@latest

Re-check after install:

mobilebuildmcp --help

Step 2: Use Help-First Discovery

Discover workflows and arguments from the CLI itself:

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free