xcode-ios-builder

by ipavlidakis · View original on ClawHub

Use when the user needs Xcode build/test/run workflows, simulator or device control, UI automation, screenshots/video, logs, or LLDB debugging through XcodeBuildMCP tools. Includes discovery of projects/schemes, session defaults, and common simulator/device workflows.

Module Mobile Dev v1.0.0 Audited 2026-02-07
84 Trust

Permissions

File Read Can read project files
File Write Can write and modify files
Network No network access
Shell Can execute shell commands

Risk Assessment

Elevated Risk

This skill requests 3 of 4 possible permissions. Elevated scope — ensure each permission is justified. Consider running in a sandbox.

Shell access can execute arbitrary commands. Use a sandbox for extra safety.

SKILL.md

Overview

Use the xcodebuildmcp toolset to build/run/test apps, manage simulators/devices, automate UI, and capture logs/screen media. Default to a safe, repeatable flow: discover → set defaults → execute → verify.

Prereqs & MCP Setup

This skill assumes the XcodeBuildMCP server is installed and exposed to your MCP client so the tools appear (e.g., mcp__xcodebuildmcp__build_run_sim). If the tools are missing, follow the setup steps in:

  • references/mcp-setup.md (requirements + MCP client config examples)

Example Requests

  • "Build and run the iOS app on the latest simulator and take a screenshot."
  • "Run unit tests on the simulator and share the failing test logs."
  • "Open the simulator, navigate to Settings, and toggle Dark Mode."
  • "Install and launch the app on my connected iPhone."

Quick Start (common flow)

  1. Discover the project/workspace and schemes:

    • mcp__xcodebuildmcp__discover_projs
    • mcp__xcodebuildmcp__list_schemes

  2. Set session defaults (so subsequent tools don’t need repeated params):

    • mcp__xcodebuildmcp__session-set-defaults (workspacePath/projectPath, scheme, simulatorId/deviceId)

  3. Run the task:

    • Build/run: mcp__xcodebuildmcp__build_run_sim or mcp__xcodebuildmcp__build_run_macos
    • Tests: mcp__xcodebuildmcp__test_sim / mcp__xcodebuildmcp__test_macos / mcp__xcodebuildmcp__test_device

  4. Verify and gather evidence:

    • mcp__xcodebuildmcp__screenshot (sim)
    • mcp__xcodebuildmcp__start_sim_log_cap → mcp__xcodebuildmcp__stop_sim_log_cap

Task Index

  • Build/Run: iOS simulator, macOS, device installs
  • Testing: simulator/macOS/device
  • Simulator management: list/boot/erase/appearance/location/gestures
  • UI automation: describe UI → tap/type/swipe/gesture
  • Logs & debugging: sim logs, device logs, LLDB attach/breakpoints
  • Media: screenshots, screen recording

Load references/workflows.md for detailed step-by-step sequences and command patterns.

Operating Rules

  • Always call mcp__xcodebuildmcp__describe_ui before coordinate-based taps/swipes/long-press.
  • Prefer mcp__xcodebuildmcp__session-set-defaults early to reduce parameter noise.
  • If user didn’t specify target device/simulator, list options and ask (or pick a sensible default with useLatestOS).
  • Avoid destructive actions (erase sims, clean) unless the user asked for them.
Back to Verified Skills Verify another skill

Related skills in Mobile Dev

Why You Need xcode-ios-builder

iOS development involves constant context switching between your editor and Xcode — building, running tests, managing simulators, and debugging on devices. Each of these workflows requires navigating Xcode's GUI or memorizing xcodebuild flags.

Xcode iOS Builder brings the entire Xcode toolchain into your OpenClaw agent. Build projects, run unit and UI tests, launch simulators, deploy to connected devices, and automate UI interactions — all through natural language commands. No more alt-tabbing to Xcode just to run a test suite.

This skill is essential for iOS and macOS developers who want to stay in their terminal workflow while still having full access to Apple's build and test infrastructure.

Common Use Cases

  • Build and test an iOS project without leaving your terminal or editor
  • Launch a specific iOS simulator and run UI automation tests against it
  • Deploy a debug build to a connected iPhone or iPad for manual testing
  • Run xcodebuild with custom schemes, configurations, and destinations
  • Automate repetitive Xcode workflows like clean-build-test cycles

Frequently Asked Questions

Does this skill require Xcode to be installed?

Yes. This skill wraps the xcodebuild CLI and Simulator tools that ship with Xcode. You need Xcode installed on your Mac for it to work.

Can it run tests on a physical device?

Yes. If a device is connected and configured for development, the skill can target it for builds and test runs, just like xcodebuild would.

Does it support SwiftUI previews?

The skill focuses on build, test, and run workflows. SwiftUI previews are handled by Xcode's preview engine, which requires the Xcode GUI.

Related Guides