Agent Skills › viralcode/openwhale › xcodebuildmcp

xcodebuildmcp

GitHub

用于通过XcodeBuildMCP工具执行iOS/macOS应用的构建、运行、测试及UI自动化，管理模拟器与真机，捕获日志和屏幕媒体，支持LLDB调试。

skills/xcodebuildmcp/SKILL.md viralcode/openwhale

Trigger Scenarios

需要构建或运行iOS/macOS应用在模拟器或真机上运行单元测试控制模拟器设备或进行UI自动化操作获取应用日志或截图

Install

npx skills add viralcode/openwhale --skill xcodebuildmcp -g -y

More Options

Use without installing

npx skills use viralcode/openwhale@xcodebuildmcp

指定 Agent (Claude Code)

npx skills add viralcode/openwhale --skill xcodebuildmcp -a claude-code -g -y

安装 repo 全部 skill

npx skills add viralcode/openwhale --all -g -y

预览 repo 内 skill

npx skills add viralcode/openwhale --list

SKILL.md

Frontmatter

{
    "name": "xcodebuildmcp",
    "description": "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."
}

Xcodebuildmcp

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)

Discover the project/workspace and schemes:
- mcp__xcodebuildmcp__discover_projs
- mcp__xcodebuildmcp__list_schemes
Set session defaults (so subsequent tools don’t need repeated params):
- mcp__xcodebuildmcp__session-set-defaults (workspacePath/projectPath, scheme, simulatorId/deviceId)
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
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.