據 AlphaMoat 統計,截至 2026-09,xcodebuildmcp 累計下載 3,781 次、獲 2 個星標,在全部 5,078 個 AI 技能中排名第 2,798 位,在「開發程式設計」分類(577 個)中排名第 363 位。

累計安裝

116

累計下載

3781

星標

全站排名

#2,798

全站前 56% · 「開發程式設計」前 63%

平台	累計安裝	累計下載	星標	評論
ClawHub ↗	116	3441	2	-
SkillHub ↗	116	3781	2	—

各平台的計數口徑不同,統計時間不一致。

這個技能是做什麼的

該流程建議先發現專案與方案、設定會話預設值、執行任務並驗證結果；擦除模擬器或清理等破壞性操作應在使用者明確要求時才進行。核對目標裝置，保護日誌和截圖，並審查固定版本的依賴。

資料釋出於 2026-10-29

可以用來做什麼

在模擬器上執行或測試應用

什麼時候用

需要透過 XcodeBuildMCP 操作 Xcode 專案、裝置或模擬器時

示例提示詞

以下是根據技能文件生成的示例,不代表實際執行結果。

總結此工作流的主要步驟，並指出哪些操作屬於破壞性操作。

月度資料趨勢

累計下載3781

星標2

2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。

月份	累計下載	環比	星標
2026-09	3781	—	2
2026-08	3360	+2.6%	2
2026-07	3276	+6.6%	2
2026-06	3073	+4.2%	2
2026-05	2948	—	2

SKILL.md 原文

以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 2026-10-23。

2.7 KB · ClawHub v1.0.0

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

展開全部(共 59 行)


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