据 AlphaMoat 统计,截至 2026-09,xcodebuildmcp 累计下载 3,781 次、获 2 个星标,在全部 5,078 个 AI 技能中排名第 2,798 位,在「开发编程」分类(577 个)中排名第 363 位。

累计安装

116

累计下载

3,781

星标

全站排名

#2,798

全站前 56% · 「开发编程」前 63%

平台	累计安装	累计下载	星标	评论
ClawHub ↗	116	3,441	2	-
SkillHub ↗	116	3,781	2	—

各平台的计数口径不同,统计时间不一致。

这个技能是做什么的

该流程建议先发现项目与方案、设置会话默认值、执行任务并验证结果；擦除模拟器或清理等破坏性操作应在用户明确要求时才进行。核对目标设备，保护日志和截屏，并审查固定版本的依赖。

资料发布于 2026-10-29

可以用来做什么

在模拟器上运行或测试应用

什么时候用

需要通过 XcodeBuildMCP 操作 Xcode 项目、设备或模拟器时

示例提示词

以下是根据技能文档生成的示例,不代表实际运行结果。

总结此工作流的主要步骤，并指出哪些操作属于破坏性操作。

月度数据趋势

累计下载3,781

星标2

2026-09 起统计方法调整:同名技能按作者分别统计,并覆盖全部技能。图中虚线为调整前的月份,与之后的数据不直接比较,也不计算跨越调整的增长。

月份	累计下载	环比	星标
2026-09	3,781	—	2
2026-08	3,360	+2.6%	2
2026-07	3,276	+6.6%	2
2026-06	3,073	+4.2%	2
2026-05	2,948	—	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.