[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"similar-getsentry--XcodeBuildMCP":3,"tool-getsentry--XcodeBuildMCP":61},[4,18,26,36,44,53],{"id":5,"name":6,"github_repo":7,"description_zh":8,"stars":9,"difficulty_score":10,"last_commit_at":11,"category_tags":12,"status":17},4358,"openclaw","openclaw\u002Fopenclaw","OpenClaw 是一款专为个人打造的本地化 AI 助手，旨在让你在自己的设备上拥有完全可控的智能伙伴。它打破了传统 AI 助手局限于特定网页或应用的束缚，能够直接接入你日常使用的各类通讯渠道，包括微信、WhatsApp、Telegram、Discord、iMessage 等数十种平台。无论你在哪个聊天软件中发送消息，OpenClaw 都能即时响应，甚至支持在 macOS、iOS 和 Android 设备上进行语音交互，并提供实时的画布渲染功能供你操控。\n\n这款工具主要解决了用户对数据隐私、响应速度以及“始终在线”体验的需求。通过将 AI 部署在本地，用户无需依赖云端服务即可享受快速、私密的智能辅助，真正实现了“你的数据，你做主”。其独特的技术亮点在于强大的网关架构，将控制平面与核心助手分离，确保跨平台通信的流畅性与扩展性。\n\nOpenClaw 非常适合希望构建个性化工作流的技术爱好者、开发者，以及注重隐私保护且不愿被单一生态绑定的普通用户。只要具备基础的终端操作能力（支持 macOS、Linux 及 Windows WSL2），即可通过简单的命令行引导完成部署。如果你渴望拥有一个懂你",349277,3,"2026-04-06T06:32:30",[13,14,15,16],"Agent","开发框架","图像","数据工具","ready",{"id":19,"name":20,"github_repo":21,"description_zh":22,"stars":23,"difficulty_score":10,"last_commit_at":24,"category_tags":25,"status":17},3808,"stable-diffusion-webui","AUTOMATIC1111\u002Fstable-diffusion-webui","stable-diffusion-webui 是一个基于 Gradio 构建的网页版操作界面，旨在让用户能够轻松地在本地运行和使用强大的 Stable Diffusion 图像生成模型。它解决了原始模型依赖命令行、操作门槛高且功能分散的痛点，将复杂的 AI 绘图流程整合进一个直观易用的图形化平台。\n\n无论是希望快速上手的普通创作者、需要精细控制画面细节的设计师，还是想要深入探索模型潜力的开发者与研究人员，都能从中获益。其核心亮点在于极高的功能丰富度：不仅支持文生图、图生图、局部重绘（Inpainting）和外绘（Outpainting）等基础模式，还独创了注意力机制调整、提示词矩阵、负向提示词以及“高清修复”等高级功能。此外，它内置了 GFPGAN 和 CodeFormer 等人脸修复工具，支持多种神经网络放大算法，并允许用户通过插件系统无限扩展能力。即使是显存有限的设备，stable-diffusion-webui 也提供了相应的优化选项，让高质量的 AI 艺术创作变得触手可及。",162132,"2026-04-05T11:01:52",[14,15,13],{"id":27,"name":28,"github_repo":29,"description_zh":30,"stars":31,"difficulty_score":32,"last_commit_at":33,"category_tags":34,"status":17},1381,"everything-claude-code","affaan-m\u002Feverything-claude-code","everything-claude-code 是一套专为 AI 编程助手（如 Claude Code、Codex、Cursor 等）打造的高性能优化系统。它不仅仅是一组配置文件，而是一个经过长期实战打磨的完整框架，旨在解决 AI 代理在实际开发中面临的效率低下、记忆丢失、安全隐患及缺乏持续学习能力等核心痛点。\n\n通过引入技能模块化、直觉增强、记忆持久化机制以及内置的安全扫描功能，everything-claude-code 能显著提升 AI 在复杂任务中的表现，帮助开发者构建更稳定、更智能的生产级 AI 代理。其独特的“研究优先”开发理念和针对 Token 消耗的优化策略，使得模型响应更快、成本更低，同时有效防御潜在的攻击向量。\n\n这套工具特别适合软件开发者、AI 研究人员以及希望深度定制 AI 工作流的技术团队使用。无论您是在构建大型代码库，还是需要 AI 协助进行安全审计与自动化测试，everything-claude-code 都能提供强大的底层支持。作为一个曾荣获 Anthropic 黑客大奖的开源项目，它融合了多语言支持与丰富的实战钩子（hooks），让 AI 真正成长为懂上",149489,2,"2026-04-10T11:32:46",[14,13,35],"语言模型",{"id":37,"name":38,"github_repo":39,"description_zh":40,"stars":41,"difficulty_score":32,"last_commit_at":42,"category_tags":43,"status":17},2271,"ComfyUI","Comfy-Org\u002FComfyUI","ComfyUI 是一款功能强大且高度模块化的视觉 AI 引擎，专为设计和执行复杂的 Stable Diffusion 图像生成流程而打造。它摒弃了传统的代码编写模式，采用直观的节点式流程图界面，让用户通过连接不同的功能模块即可构建个性化的生成管线。\n\n这一设计巧妙解决了高级 AI 绘图工作流配置复杂、灵活性不足的痛点。用户无需具备编程背景，也能自由组合模型、调整参数并实时预览效果，轻松实现从基础文生图到多步骤高清修复等各类复杂任务。ComfyUI 拥有极佳的兼容性，不仅支持 Windows、macOS 和 Linux 全平台，还广泛适配 NVIDIA、AMD、Intel 及苹果 Silicon 等多种硬件架构，并率先支持 SDXL、Flux、SD3 等前沿模型。\n\n无论是希望深入探索算法潜力的研究人员和开发者，还是追求极致创作自由度的设计师与资深 AI 绘画爱好者，ComfyUI 都能提供强大的支持。其独特的模块化架构允许社区不断扩展新功能，使其成为当前最灵活、生态最丰富的开源扩散模型工具之一，帮助用户将创意高效转化为现实。",108322,"2026-04-10T11:39:34",[14,15,13],{"id":45,"name":46,"github_repo":47,"description_zh":48,"stars":49,"difficulty_score":32,"last_commit_at":50,"category_tags":51,"status":17},6121,"gemini-cli","google-gemini\u002Fgemini-cli","gemini-cli 是一款由谷歌推出的开源 AI 命令行工具，它将强大的 Gemini 大模型能力直接集成到用户的终端环境中。对于习惯在命令行工作的开发者而言，它提供了一条从输入提示词到获取模型响应的最短路径，无需切换窗口即可享受智能辅助。\n\n这款工具主要解决了开发过程中频繁上下文切换的痛点，让用户能在熟悉的终端界面内直接完成代码理解、生成、调试以及自动化运维任务。无论是查询大型代码库、根据草图生成应用，还是执行复杂的 Git 操作，gemini-cli 都能通过自然语言指令高效处理。\n\n它特别适合广大软件工程师、DevOps 人员及技术研究人员使用。其核心亮点包括支持高达 100 万 token 的超长上下文窗口，具备出色的逻辑推理能力；内置 Google 搜索、文件操作及 Shell 命令执行等实用工具；更独特的是，它支持 MCP（模型上下文协议），允许用户灵活扩展自定义集成，连接如图像生成等外部能力。此外，个人谷歌账号即可享受免费的额度支持，且项目基于 Apache 2.0 协议完全开源，是提升终端工作效率的理想助手。",100752,"2026-04-10T01:20:03",[52,13,15,14],"插件",{"id":54,"name":55,"github_repo":56,"description_zh":57,"stars":58,"difficulty_score":32,"last_commit_at":59,"category_tags":60,"status":17},4721,"markitdown","microsoft\u002Fmarkitdown","MarkItDown 是一款由微软 AutoGen 团队打造的轻量级 Python 工具，专为将各类文件高效转换为 Markdown 格式而设计。它支持 PDF、Word、Excel、PPT、图片（含 OCR）、音频（含语音转录）、HTML 乃至 YouTube 链接等多种格式的解析，能够精准提取文档中的标题、列表、表格和链接等关键结构信息。\n\n在人工智能应用日益普及的今天，大语言模型（LLM）虽擅长处理文本，却难以直接读取复杂的二进制办公文档。MarkItDown 恰好解决了这一痛点，它将非结构化或半结构化的文件转化为模型“原生理解”且 Token 效率极高的 Markdown 格式，成为连接本地文件与 AI 分析 pipeline 的理想桥梁。此外，它还提供了 MCP（模型上下文协议）服务器，可无缝集成到 Claude Desktop 等 LLM 应用中。\n\n这款工具特别适合开发者、数据科学家及 AI 研究人员使用，尤其是那些需要构建文档检索增强生成（RAG）系统、进行批量文本分析或希望让 AI 助手直接“阅读”本地文件的用户。虽然生成的内容也具备一定可读性，但其核心优势在于为机器",93400,"2026-04-06T19:52:38",[52,14],{"id":62,"github_repo":63,"name":64,"description_en":65,"description_zh":66,"ai_summary_zh":66,"readme_en":67,"readme_zh":68,"quickstart_zh":69,"use_case_zh":70,"hero_image_url":71,"owner_login":72,"owner_name":73,"owner_avatar_url":74,"owner_bio":75,"owner_company":76,"owner_location":76,"owner_email":77,"owner_twitter":78,"owner_website":79,"owner_url":80,"languages":81,"stars":101,"forks":102,"last_commit_at":103,"license":104,"difficulty_score":32,"env_os":105,"env_gpu":106,"env_ram":106,"env_deps":107,"category_tags":113,"github_topics":114,"view_count":32,"oss_zip_url":76,"oss_zip_packed_at":76,"status":17,"created_at":122,"updated_at":123,"faqs":124,"releases":154},6396,"getsentry\u002FXcodeBuildMCP","XcodeBuildMCP","A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.","XcodeBuildMCP 是一款专为 iOS 和 macOS 开发打造的智能辅助工具，它基于模型上下文协议（MCP）构建，充当了 AI 编程助手与苹果开发环境之间的桥梁。在传统的移动开发中，让 AI 准确理解复杂的项目结构、执行编译命令或处理构建错误往往存在障碍，而 XcodeBuildMCP 通过提供标准化的命令行接口和服务器模式，赋予了 AI 代理直接操作 Xcode 项目的能力，从而显著提升了代码构建、调试及项目管理的自动化水平。\n\n这款工具特别适合广大苹果生态开发者，尤其是那些希望将 Cursor、Claude Code 等先进 AI 编码助手融入日常工作的工程师。无论是需要快速排查构建报错，还是希望 AI 协助管理多目标项目配置，XcodeBuildMCP 都能让交互更加流畅自然。其技术亮点在于“双模”设计：既可作为独立的命令行工具供人工直接调用，也能作为后台 MCP 服务器无缝对接各类 AI 客户端。此外，它支持通过 Homebrew 和 npm 灵活安装，并针对主流开发编辑器提供了开箱即用的配置方案，无需繁琐设置即可享受智能化的开发体验，让构建过程更加高效可靠。","\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fgetsentry_XcodeBuildMCP_readme_75906f550f5c.png\" alt=\"XcodeBuild MCP\" width=\"600\"\u002F>\n\nA Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.\n\n[![CI](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Factions\u002Fworkflows\u002Fci.yml\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Factions\u002Fworkflows\u002Fci.yml)\n[![npm version](https:\u002F\u002Fbadge.fury.io\u002Fjs\u002Fxcodebuildmcp.svg)](https:\u002F\u002Fbadge.fury.io\u002Fjs\u002Fxcodebuildmcp) [![License: MIT](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLicense-MIT-yellow.svg)](https:\u002F\u002Fopensource.org\u002Flicenses\u002FMIT) [![Node.js](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fnode->=18.x-brightgreen.svg)](https:\u002F\u002Fnodejs.org\u002F) [![Xcode 16](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FXcode-16-blue.svg)](https:\u002F\u002Fdeveloper.apple.com\u002Fxcode\u002F) [![macOS](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fplatform-macOS-lightgrey.svg)](https:\u002F\u002Fwww.apple.com\u002Fmacos\u002F) [![MCP](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FMCP-Compatible-green.svg)](https:\u002F\u002Fmodelcontextprotocol.io\u002F) [![Ask DeepWiki](https:\u002F\u002Fdeepwiki.com\u002Fbadge.svg)](https:\u002F\u002Fdeepwiki.com\u002Fgetsentry\u002FXcodeBuildMCP) [![AgentAudit Security](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FAgentAudit-Safe-brightgreen?logo=data:image\u002Fsvg%2Bxml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNCAyNCI+PHBhdGggZmlsbD0id2hpdGUiIGQ9Ik0xMiAxTDMgNXY2YzAgNS41NSAzLjg0IDEwLjc0IDkgMTIgNS4xNi0xLjI2IDktNi40NSA5LTEyVjVsLTktNHoiLz48L3N2Zz4=)](https:\u002F\u002Fwww.agentaudit.dev\u002Fskills\u002Fxcodebuildmcp)\n\n## Installation\n\nXcodeBuildMCP ships as a single package with two modes: a **CLI** for direct terminal use and an **MCP server** for AI coding agents. Both installation methods give you both modes.\n\n### Option A — Homebrew\n\n```bash\nbrew tap getsentry\u002Fxcodebuildmcp\nbrew install xcodebuildmcp\n```\n\nUse the CLI:\n```bash\nxcodebuildmcp --help\n```\n\nMCP client config:\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"xcodebuildmcp\",\n  \"args\": [\"mcp\"]\n}\n```\n\nUpgrade later with `brew update && brew upgrade xcodebuildmcp`.\n\n### Option B — npm \u002F npx (Node.js 18+)\n\n**For CLI use**, install globally:\n```bash\nnpm install -g xcodebuildmcp@latest\nxcodebuildmcp --help\n```\n\n**For MCP server only**, no global install needed — add directly to your client config:\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n}\n```\n\nTo pin a specific version, replace `@latest` with an exact version (e.g. `xcodebuildmcp@latest`).\n\n### Client-specific setup\n\nThe examples below use npx (Option B). If you installed via Homebrew, replace the command with `\"command\": \"xcodebuildmcp\", \"args\": [\"mcp\"]` instead.\n\n\u003Cdetails>\n  \u003Csummary>Cursor\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  Recommended (project-scoped): add `.cursor\u002Fmcp.json` in your workspace root:\n  ```json\n  {\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n      }\n    }\n  }\n  ```\n\n  For global Cursor config (`~\u002F.cursor\u002Fmcp.json`), use this variant so startup is aligned with the active workspace:\n  ```json\n  {\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"\u002Fbin\u002Fzsh\",\n        \"args\": [\n          \"-lc\",\n          \"cd \\\"${workspaceFolder}\\\" && exec npx -y xcodebuildmcp@latest mcp\"\n        ]\n      }\n    }\n  }\n  ```\n\n  Or use the quick install link:\n\n[![Install MCP Server](https:\u002F\u002Fcursor.com\u002Fdeeplink\u002Fmcp-install-light.svg)](https:\u002F\u002Fcursor.com\u002Fen-US\u002Finstall-mcp?name=XcodeBuildMCP&config=eyJjb21tYW5kIjoibnB4IC15IHhjb2RlYnVpbGRtY3BAbGF0ZXN0IG1jcCJ9)\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Claude Code\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  Run:\n  ```bash\n  claude mcp add XcodeBuildMCP -- npx -y xcodebuildmcp@latest mcp\n  ```\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Codex CLI\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  Run:\n  ```bash\n  codex mcp add XcodeBuildMCP -- npx -y xcodebuildmcp@latest mcp\n  ```\n\n  Or add to `~\u002F.codex\u002Fconfig.toml`:\n  ```toml\n  [mcp_servers.XcodeBuildMCP]\n  command = \"npx\"\n  args = [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n  ```\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Claude Desktop\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  Add to `~\u002FLibrary\u002FApplication Support\u002FClaude\u002Fclaude_desktop_config.json`:\n  ```json\n  {\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n      }\n    }\n  }\n  ```\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>VS Code \u002F VS Code Insiders\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  Add to your VS Code settings JSON:\n  ```json\n  \"mcp\": {\n    \"servers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n      }\n    }\n  }\n  ```\n\n  Or use the quick install links:\n\n  [![Install in VS Code](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FVS_Code-XcodeBuildMCP-0098FF?style=flat&logo=visualstudiocode&logoColor=ffffff)](vscode:mcp\u002Finstall?%7B%22name%22%3A%22XcodeBuildMCP%22%2C%22type%22%3A%22stdio%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22xcodebuildmcp%40latest%22%2C%22mcp%22%5D%7D)\n  [![Install in VS Code Insiders](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FVS_Code_Insiders-XcodeBuildMCP-24bfa5?style=flat&logo=visualstudiocode&logoColor=ffffff)](vscode-insiders:mcp\u002Finstall?%7B%22name%22%3A%22XcodeBuildMCP%22%2C%22type%22%3A%22stdio%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22xcodebuildmcp%40latest%22%2C%22mcp%22%5D%7D)\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Kiro \u002F Kiro CLI\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  **Workspace-level** (applies only to the current workspace): add `.kiro\u002Fsettings\u002Fmcp.json` in your project root:\n  ```json\n  {\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n      }\n    }\n  }\n  ```\n\n  **User-level** (applies globally across all workspaces): add to `~\u002F.kiro\u002Fsettings\u002Fmcp.json`:\n  ```json\n  {\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n      }\n    }\n  }\n  ```\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Windsurf\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  Add to `~\u002F.codeium\u002Fwindsurf\u002Fmcp_config.json`:\n  ```json\n  {\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n      }\n    }\n  }\n  ```\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Trae\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  Add to `~\u002FLibrary\u002FApplication Support\u002FTrae\u002FUser\u002Fmcp.json`:\n  ```json\n  {\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n      }\n    }\n  }\n  ```\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Xcode (Codex Agent)\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  Requires Xcode 26.3 or later. Codex agent must be installed and configured in Xcode Settings -> Intelligence -> Open AI.\n\n  The only way at the time of writing to add an MCP server is to use a project scoped `.codex\u002Fconfig.toml` file in the root of your project workspace:\n  `\u002Fpath\u002Fto\u002Fyour\u002Fproject\u002F.codex\u002Fconfig.toml`\n\n  ```toml\n  [mcp_servers.XcodeBuildMCP]\n  args = [\n  \"-lc\",\n  \"PATH=\u002Fopt\u002Fhomebrew\u002Fbin:\u002Fusr\u002Flocal\u002Fbin:\u002Fusr\u002Fbin:\u002Fbin:\u002Fusr\u002Fsbin:\u002Fsbin; export NVM_DIR=\\\"$HOME\u002F.nvm\\\"; [ -s \\\"$NVM_DIR\u002Fnvm.sh\\\" ] && . \\\"$NVM_DIR\u002Fnvm.sh\\\"; nvm use --silent >\u002Fdev\u002Fnull 2>&1 || true; npx -y xcodebuildmcp@latest mcp\"\n  ]\n  command = \"\u002Fbin\u002Fzsh\"\n  enabled = true\n  tool_timeout_sec = 10000\n  ```\n\n  > **NOTE**:\n  > Codex Agent when running in Xcode has a limited PATH by default. The above example should work for most users but if you find the server doesn't start or is not available, it's likely because npx is not found so you might have to adjust the above configuration accordingly.\n\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Xcode (Claude Code Agent)\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  Requires Xcode 26.3 or later. Claude Code agent must be installed and configured in Xcode Settings -> Intelligence -> Anthropic.\n\n  Add to the end or replace the existing `mcpServers` object in Xcode's Claude Code agent config at:\n  `~\u002FLibrary\u002FDeveloper\u002FXcode\u002FCodingAssistant\u002FClaudeAgentConfig\u002F.claude.json`\n\n  ```json\n    \u002F\u002F ... rest of file ...\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"\u002Fbin\u002Fzsh\",\n        \"args\": [\n          \"-lc\",\n          \"PATH=\u002Fopt\u002Fhomebrew\u002Fbin:\u002Fusr\u002Flocal\u002Fbin:\u002Fusr\u002Fbin:\u002Fbin:\u002Fusr\u002Fsbin:\u002Fsbin; export NVM_DIR=\\\"$HOME\u002F.nvm\\\"; [ -s \\\"$NVM_DIR\u002Fnvm.sh\\\" ] && . \\\"$NVM_DIR\u002Fnvm.sh\\\"; nvm use --silent >\u002Fdev\u002Fnull 2>&1 || true; npx -y xcodebuildmcp@latest mcp\"\n        ]\n      }\n    }\n  }\n  ```\n\n  > **NOTE**:\n  > Claude Code Agent when running in Xcode has a limited PATH by default. The above example should work for most users but if you find the server doesn't start or is not available, it's likely because npx is not found so you might have to adjust the above configuration accordingly.\n\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>AdaL CLI\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  Run the following command inside the AdaL CLI prompt:\n  ```console\n  \u002Fmcp add XcodeBuildMCP --command npx --args \"-y,xcodebuildmcp@latest,mcp\"\n  ```\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cbr \u002F>\n\nFor other installation options see [Getting Started](docs\u002FGETTING_STARTED.md).\n\n## Requirements\n\n- macOS 14.5 or later\n- Xcode 16.x or later\n- Node.js 18.x or later (not required for Homebrew installation)\n\n## Skills\n\nXcodeBuildMCP now includes two optional agent skills:\n\n- **MCP Skill**: Primes the agent with instructions on how to use the MCP server's tools (optional when using the MCP server).\n\n- **CLI Skill**: Primes the agent with instructions on how to navigate the CLI (recommended when using the CLI).\n\n\nTo install with a global binary:\n\n```bash\nxcodebuildmcp init\n```\n\nOr install directly via npx without a global install:\n\n```bash\nnpx -y xcodebuildmcp@latest init\n```\n\nFor further information on installing skills, see: [docs\u002FSKILLS.md](docs\u002FSKILLS.md)\n\n## Notes\n\n- XcodeBuildMCP requests xcodebuild to skip macro validation to avoid errors when building projects that use Swift Macros.\n- Device tools require code signing to be configured in Xcode. See [docs\u002FDEVICE_CODE_SIGNING.md](docs\u002FDEVICE_CODE_SIGNING.md).\n\n## Privacy\n\nXcodeBuildMCP uses Sentry for internal runtime error telemetry only. For details and opt-out instructions, see [docs\u002FPRIVACY.md](docs\u002FPRIVACY.md).\n\n## CLI\n\nXcodeBuildMCP provides a unified command-line interface. The `mcp` subcommand starts the MCP server, while all other commands provide direct terminal access to tools:\n\n```bash\n# Install globally\nnpm install -g xcodebuildmcp@latest\n\n# Start the MCP server (for MCP clients)\nxcodebuildmcp mcp\n\n# List available tools\nxcodebuildmcp tools\n\n# Build for simulator\nxcodebuildmcp simulator build --scheme MyApp --project-path .\u002FMyApp.xcodeproj\n```\n\nThe CLI uses a per-workspace daemon for stateful operations (log capture, debugging, etc.) that auto-starts when needed. See [docs\u002FCLI.md](docs\u002FCLI.md) for full documentation.\n\n## Documentation\n\n- Getting started: [docs\u002FGETTING_STARTED.md](docs\u002FGETTING_STARTED.md)\n- CLI usage: [docs\u002FCLI.md](docs\u002FCLI.md)\n- Configuration and options: [docs\u002FCONFIGURATION.md](docs\u002FCONFIGURATION.md)\n- Tools reference: [docs\u002FTOOLS.md](docs\u002FTOOLS.md)\n- Troubleshooting: [docs\u002FTROUBLESHOOTING.md](docs\u002FTROUBLESHOOTING.md)\n- Privacy: [docs\u002FPRIVACY.md](docs\u002FPRIVACY.md)\n- Skills: [docs\u002FSKILLS.md](docs\u002FSKILLS.md)\n- Contributing: [docs\u002Fdev\u002FCONTRIBUTING.md](docs\u002Fdev\u002FCONTRIBUTING.md)\n\n## Licence\n\nThis project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.\nFor third-party licensing notices see the [THIRD_PARTY_LICENSES](THIRD_PARTY_LICENSES) file for details.\nFor npm package attributions see the [THIRD_PARTY_PACKAGE_LICENSES](THIRD_PARTY_PACKAGE_LICENSES.md) file for details.\n","\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fgetsentry_XcodeBuildMCP_readme_75906f550f5c.png\" alt=\"XcodeBuild MCP\" width=\"600\"\u002F>\n\n一个模型上下文协议（MCP）服务器和命令行工具，为在 iOS 和 macOS 项目中工作的智能体提供辅助工具。\n\n[![CI](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Factions\u002Fworkflows\u002Fci.yml\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Factions\u002Fworkflows\u002Fci.yml)\n[![npm version](https:\u002F\u002Fbadge.fury.io\u002Fjs\u002Fxcodebuildmcp.svg)](https:\u002F\u002Fbadge.fury.io\u002Fjs\u002Fxcodebuildmcp) [![License: MIT](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLicense-MIT-yellow.svg)](https:\u002F\u002Fopensource.org\u002Flicenses\u002FMIT) [![Node.js](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fnode->=18.x-brightgreen.svg)](https:\u002F\u002Fnodejs.org\u002F) [![Xcode 16](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FXcode-16-blue.svg)](https:\u002F\u002Fdeveloper.apple.com\u002Fxcode\u002F) [![macOS](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fplatform-macOS-lightgrey.svg)](https:\u002F\u002Fwww.apple.com\u002Fmacos\u002F) [![MCP](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FMCP-Compatible-green.svg)](https:\u002F\u002Fmodelcontextprotocol.io\u002F) [![Ask DeepWiki](https:\u002F\u002Fdeepwiki.com\u002Fbadge.svg)](https:\u002F\u002Fdeepwiki.com\u002Fgetsentry\u002FXcodeBuildMCP) [![AgentAudit 安全](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FAgentAudit-Safe-brightgreen?logo=data:image\u002Fsvg%2Bxml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNCAyNCI+PHBhdGggZmlsbD0id2hpdGUiIGQ9Ik0xMiAxTDMgNXY2YzAgNS41NSAzLjg0IDEwLjc0IDkgMTIgNS4xNi0xLjI2IDktNi40NSA5LTEyVjVsLTktNHoiLz48L3N2Zz4=)](https:\u002F\u002Fwww.agentaudit.dev\u002Fskills\u002Fxcodebuildmcp)\n\n## 安装\n\nXcodeBuildMCP 以单个软件包形式提供两种模式：一种是用于直接在终端使用的 **CLI**，另一种是面向 AI 编码智能体的 **MCP 服务器**。无论采用哪种安装方式，您都可以同时获得这两种模式。\n\n### 选项 A — Homebrew\n\n```bash\nbrew tap getsentry\u002Fxcodebuildmcp\nbrew install xcodebuildmcp\n```\n\n使用 CLI：\n```bash\nxcodebuildmcp --help\n```\n\nMCP 客户端配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"xcodebuildmcp\",\n  \"args\": [\"mcp\"]\n}\n```\n\n后续升级时，运行 `brew update && brew upgrade xcodebuildmcp`。\n\n### 选项 B — npm \u002F npx（Node.js 18+）\n\n**仅用于 CLI**，可全局安装：\n```bash\nnpm install -g xcodebuildmcp@latest\nxcodebuildmcp --help\n```\n\n**仅用于 MCP 服务器**，无需全局安装，直接添加到您的客户端配置中：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n}\n```\n\n如需锁定特定版本，将 `@latest` 替换为具体版本号（例如 `xcodebuildmcp@1.0.0`）。\n\n### 客户端特定设置\n\n以下示例使用 npx（选项 B）。如果您通过 Homebrew 安装，请将命令替换为 `\"command\": \"xcodebuildmcp\", \"args\": [\"mcp\"]`。\n\n\u003Cdetails>\n  \u003Csummary>Cursor\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  推荐做法（项目范围）：在工作区根目录下添加 `.cursor\u002Fmcp.json`：\n  ```json\n  {\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n      }\n    }\n  }\n  ```\n\n  对于全局 Cursor 配置文件 (`~\u002F.cursor\u002Fmcp.json`)，可以使用以下变体，以便启动时与当前活动的工作区保持一致：\n  ```json\n  {\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"\u002Fbin\u002Fzsh\",\n        \"args\": [\n          \"-lc\",\n          \"cd \\\"${workspaceFolder}\\\" && exec npx -y xcodebuildmcp@latest mcp\"\n        ]\n      }\n    }\n  }\n  ```\n\n  或者使用快速安装链接：\n\n[![安装 MCP 服务器](https:\u002F\u002Fcursor.com\u002Fdeeplink\u002Fmcp-install-light.svg)](https:\u002F\u002Fcursor.com\u002Fen-US\u002Finstall-mcp?name=XcodeBuildMCP&config=eyJjb21tYW5kIjoibnB4IC15IHhjb2RlYnVpbGRtY3BAbGF0ZXN0IG1jcCJ9)\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Claude Code\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  运行以下命令：\n  ```bash\n  claude mcp add XcodeBuildMCP -- npx -y xcodebuildmcp@latest mcp\n  ```\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Codex CLI\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  运行以下命令：\n  ```bash\n  codex mcp add XcodeBuildMCP -- npx -y xcodebuildmcp@latest mcp\n  ```\n\n  或者将以下内容添加到 `~\u002F.codex\u002Fconfig.toml`：\n  ```toml\n  [mcp_servers.XcodeBuildMCP]\n  command = \"npx\"\n  args = [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n  ```\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Claude Desktop\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  将以下内容添加到 `~\u002FLibrary\u002FApplication Support\u002FClaude\u002Fclaude_desktop_config.json`：\n  ```json\n  {\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n      }\n    }\n  }\n  ```\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>VS Code \u002F VS Code Insiders\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  将以下内容添加到您的 VS Code 设置 JSON 文件中：\n  ```json\n  \"mcp\": {\n    \"servers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n      }\n    }\n  }\n  ```\n\n  或者使用快速安装链接：\n\n  [![在 VS Code 中安装](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FVS_Code-XcodeBuildMCP-0098FF?style=flat&logo=visualstudiocode&logoColor=ffffff)](vscode:mcp\u002Finstall?%7B%22name%22%3A%22XcodeBuildMCP%22%2C%22type%22%3A%22stdio%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22xcodebuildmcp%40latest%22%2C%22mcp%22%5D%7D)\n  [![在 VS Code Insiders 中安装](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FVS_Code_Insiders-XcodeBuildMCP-24bfa5?style=flat&logo=visualstudiocode&logoColor=ffffff)](vscode-insiders:mcp\u002Finstall?%7B%22name%22%3A%22XcodeBuildMCP%22%2C%22type%22%3A%22stdio%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22xcodebuildmcp%40latest%22%2C%22mcp%22%5D%7D)\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Kiro \u002F Kiro CLI\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  **工作区级别**（仅适用于当前工作区）：在项目根目录下添加 `.kiro\u002Fsettings\u002Fmcp.json`：\n  ```json\n  {\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n      }\n    }\n  }\n  ```\n\n  **用户级别**（适用于所有工作区）：将以下内容添加到 `~\u002F.kiro\u002Fsettings\u002Fmcp.json`：\n  ```json\n  {\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n      }\n    }\n  }\n  ```\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Windsurf\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  将以下内容添加到 `~\u002F.codeium\u002Fwindsurf\u002Fmcp_config.json`：\n  ```json\n  {\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n      }\n    }\n  }\n  ```\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Trae\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  将以下内容添加到 `~\u002FLibrary\u002FApplication Support\u002FTrae\u002FUser\u002Fmcp.json`：\n  ```json\n  {\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n      }\n    }\n  }\n  ```\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Xcode（Codex Agent）\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  需要 Xcode 26.3 或更高版本。Codex 代理必须在 Xcode 设置 -> 智能 -> Open AI 中安装并配置。\n\n  截至撰写本文时，添加 MCP 服务器的唯一方法是在项目工作区根目录下使用项目范围的 `.codex\u002Fconfig.toml` 文件：\n  `\u002Fpath\u002Fto\u002Fyour\u002Fproject\u002F.codex\u002Fconfig.toml`\n\n  ```toml\n  [mcp_servers.XcodeBuildMCP]\n  args = [\n  \"-lc\",\n  \"PATH=\u002Fopt\u002Fhomebrew\u002Fbin:\u002Fusr\u002Flocal\u002Fbin:\u002Fusr\u002Fbin:\u002Fbin:\u002Fusr\u002Fsbin:\u002Fsbin; export NVM_DIR=\\\"$HOME\u002F.nvm\\\"; [ -s \\\"$NVM_DIR\u002Fnvm.sh\\\" ] && . \\\"$NVM_DIR\u002Fnvm.sh\\\"; nvm use --silent >\u002Fdev\u002Fnull 2>&1 || true; npx -y xcodebuildmcp@latest mcp\"\n  ]\n  command = \"\u002Fbin\u002Fzsh\"\n  enabled = true\n  tool_timeout_sec = 10000\n  ```\n\n  > **注意**：\n  > Codex Agent 在 Xcode 中运行时，默认 PATH 有限。上述示例对大多数用户应有效，但如果发现服务器无法启动或不可用，很可能是由于找不到 npx，您可能需要相应调整上述配置。\n\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>Xcode（Claude Code Agent）\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  需要 Xcode 26.3 或更高版本。Claude Code 代理必须在 Xcode 设置 -> 智能 -> Anthropic 中安装并配置。\n\n  将以下内容添加到 Xcode 的 Claude Code 代理配置文件末尾，或替换现有的 `mcpServers` 对象，路径为：\n  `~\u002FLibrary\u002FDeveloper\u002FXcode\u002FCodingAssistant\u002FClaudeAgentConfig\u002F.claude.json`\n\n  ```json\n    \u002F\u002F ... 文件其余部分 ...\n    \"mcpServers\": {\n      \"XcodeBuildMCP\": {\n        \"command\": \"\u002Fbin\u002Fzsh\",\n        \"args\": [\n          \"-lc\",\n          \"PATH=\u002Fopt\u002Fhomebrew\u002Fbin:\u002Fusr\u002Flocal\u002Fbin:\u002Fusr\u002Fbin:\u002Fbin:\u002Fusr\u002Fsbin:\u002Fsbin; export NVM_DIR=\\\"$HOME\u002F.nvm\\\"; [ -s \\\"$NVM_DIR\u002Fnvm.sh\\\" ] && . \\\"$NVM_DIR\u002Fnvm.sh\\\"; nvm use --silent >\u002Fdev\u002Fnull 2>&1 || true; npx -y xcodebuildmcp@latest mcp\"\n        ]\n      }\n    }\n  }\n  ```\n\n  > **注意**：\n  > Claude Code Agent 在 Xcode 中运行时，默认 PATH 有限。上述示例对大多数用户应有效，但如果发现服务器无法启动或不可用，很可能是由于找不到 npx，您可能需要相应调整上述配置。\n\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n  \u003Csummary>AdaL CLI\u003C\u002Fsummary>\n  \u003Cbr \u002F>\n\n  在 AdaL CLI 提示符下运行以下命令：\n  ```console\n  \u002Fmcp add XcodeBuildMCP --command npx --args \"-y,xcodebuildmcp@latest,mcp\"\n  ```\n  \u003Cbr \u002F>\n\u003C\u002Fdetails>\n\n\u003Cbr \u002F>\n\n更多安装选项请参阅 [入门指南](docs\u002FGETTING_STARTED.md)。\n\n## 系统要求\n\n- macOS 14.5 或更高版本\n- Xcode 16.x 或更高版本\n- Node.js 18.x 或更高版本（通过 Homebrew 安装则无需此要求）\n\n## 技能\n\nXcodeBuildMCP 现在包含两种可选的代理技能：\n\n- **MCP 技能**：为代理预置使用 MCP 服务器工具的指令（在使用 MCP 服务器时为可选项）。\n\n- **CLI 技能**：为代理预置 CLI 导航指令（建议在使用 CLI 时启用）。\n\n\n通过全局二进制安装：\n\n```bash\nxcodebuildmcp init\n```\n\n或者无需全局安装，直接通过 npx 安装：\n\n```bash\nnpx -y xcodebuildmcp@latest init\n```\n\n有关安装技能的更多信息，请参阅：[docs\u002FSKILLS.md](docs\u002FSKILLS.md)\n\n## 注意事项\n\n- XcodeBuildMCP 会请求 xcodebuild 跳过宏验证，以避免在构建使用 Swift Macros 的项目时出现错误。\n- 设备工具需要在 Xcode 中配置代码签名。请参阅 [docs\u002FDEVICE_CODE_SIGNING.md](docs\u002FDEVICE_CODE_SIGNING.md)。\n\n## 隐私政策\n\nXcodeBuildMCP 仅将 Sentry 用于内部运行时错误遥测。有关详细信息及退出说明，请参阅 [docs\u002FPRIVACY.md](docs\u002FPRIVACY.md)。\n\n## CLI\n\nXcodeBuildMCP 提供统一的命令行界面。`mcp` 子命令用于启动 MCP 服务器，而其他所有命令则提供对工具的直接终端访问：\n\n```bash\n# 全局安装\nnpm install -g xcodebuildmcp@latest\n\n# 启动 MCP 服务器（供 MCP 客户端使用）\nxcodebuildmcp mcp\n\n# 列出可用工具\nxcodebuildmcp tools\n\n# 为模拟器构建\nxcodebuildmcp simulator build --scheme MyApp --project-path .\u002FMyApp.xcodeproj\n```\n\nCLI 使用基于工作区的守护进程来执行有状态的操作（日志捕获、调试等），该守护进程会在需要时自动启动。完整文档请参阅 [docs\u002FCLI.md](docs\u002FCLI.md)。\n\n## 文档\n\n- 入门指南：[docs\u002FGETTING_STARTED.md](docs\u002FGETTING_STARTED.md)\n- CLI 使用：[docs\u002FCLI.md](docs\u002FCLI.md)\n- 配置与选项：[docs\u002FCONFIGURATION.md](docs\u002FCONFIGURATION.md)\n- 工具参考：[docs\u002FTOOLS.md](docs\u002FTOOLS.md)\n- 故障排除：[docs\u002FTROUBLESHOOTING.md](docs\u002FTROUBLESHOOTING.md)\n- 隐私政策：[docs\u002FPRIVACY.md](docs\u002FPRIVACY.md)\n- 技能：[docs\u002FSKILLS.md](docs\u002FSKILLS.md)\n- 贡献指南：[docs\u002Fdev\u002FCONTRIBUTING.md](docs\u002Fdev\u002FCONTRIBUTING.md)\n\n## 许可证\n\n本项目采用 MIT 许可证授权——详情请参阅 [LICENSE](LICENSE) 文件。\n第三方许可声明请参阅 [THIRD_PARTY_LICENSES](THIRD_PARTY_LICENSES) 文件。\nnpm 包的归属信息请参阅 [THIRD_PARTY_PACKAGE_LICENSES](THIRD_PARTY_PACKAGE_LICENSES.md) 文件。","# XcodeBuildMCP 快速上手指南\n\nXcodeBuildMCP 是一个基于模型上下文协议（MCP）的服务器和命令行工具，专为 iOS 和 macOS 项目开发设计，旨在辅助 AI 编程助手（Agent）更高效地构建、测试和管理苹果生态项目。\n\n## 环境准备\n\n在开始之前，请确保您的开发环境满足以下要求：\n\n*   **操作系统**：macOS 14.5 或更高版本\n*   **开发工具**：Xcode 16.x 或更高版本\n*   **运行时依赖**：Node.js 18.x 或更高版本（若使用 Homebrew 安装则无需单独安装 Node.js）\n\n## 安装步骤\n\n您可以选择通过 **Homebrew** 或 **npm** 进行安装。两种方式均包含 CLI 命令行工具和 MCP 服务器模式。\n\n### 方式一：使用 Homebrew（推荐）\n\n适合希望统一管理工具链的开发者。\n\n```bash\n# 添加仓库源\nbrew tap getsentry\u002Fxcodebuildmcp\n\n# 安装工具\nbrew install xcodebuildmcp\n```\n\n**验证安装：**\n```bash\nxcodebuildmcp --help\n```\n\n### 方式二：使用 npm \u002F npx\n\n适合习惯 Node.js 生态或需要特定版本控制的开发者。\n\n**全局安装（用于直接使用 CLI）：**\n```bash\nnpm install -g xcodebuildmcp@latest\nxcodebuildmcp --help\n```\n\n> **提示**：如果您仅需在 AI 编辑器中作为 MCP 服务器使用，无需全局安装，可直接在配置中使用 `npx` 调用（见下文配置部分）。\n\n## 基本使用\n\nXcodeBuildMCP 提供两种主要使用场景：直接在终端运行命令，或集成到 AI 编程助手（如 Cursor, Claude Code, VS Code 等）中。\n\n### 1. 终端命令行使用 (CLI)\n\n安装完成后，您可以直接在终端执行构建、列出工具等操作。\n\n**查看可用工具列表：**\n```bash\nxcodebuildmcp tools\n```\n\n**为模拟器构建项目：**\n```bash\nxcodebuildmcp simulator build --scheme MyApp --project-path .\u002FMyApp.xcodeproj\n```\n\n**初始化 Agent 技能（可选）：**\n若需让 AI 更好地理解如何使用该工具，可运行初始化命令注入上下文技能：\n```bash\nxcodebuildmcp init\n# 或者不全局安装直接运行\nnpx -y xcodebuildmcp@latest init\n```\n\n### 2. 集成到 AI 编程助手 (MCP Server)\n\n将以下配置添加到您使用的 AI 客户端配置文件中，即可让 AI 自动调用 XcodeBuildMCP 的能力。\n\n#### Cursor 编辑器\n在项目根目录创建 `.cursor\u002Fmcp.json` 文件：\n```json\n{\n  \"mcpServers\": {\n    \"XcodeBuildMCP\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n    }\n  }\n}\n```\n*(注：若使用 Homebrew 安装，请将 command 改为 `\"xcodebuildmcp\"`，args 改为 `[\"mcp\"]`)*\n\n#### Claude Code\n在终端运行以下命令自动添加：\n```bash\nclaude mcp add XcodeBuildMCP -- npx -y xcodebuildmcp@latest mcp\n```\n\n#### VS Code\n在设置 JSON (`settings.json`) 中添加：\n```json\n\"mcp\": {\n  \"servers\": {\n    \"XcodeBuildMCP\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n    }\n  }\n}\n```\n\n#### 其他客户端 (Claude Desktop, Windsurf, Trae 等)\n大多数客户端支持类似的 JSON 配置结构，核心配置如下：\n```json\n{\n  \"mcpServers\": {\n    \"XcodeBuildMCP\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n    }\n  }\n}\n```\n\n> **注意**：\n> 1. 真机调试工具需要先在 Xcode 中配置好代码签名。\n> 2. 该工具会自动跳过 Swift Macros 的宏验证以避免构建错误。","iOS 开发者在修复一个因依赖版本冲突导致构建失败的复杂项目时，需要频繁查询构建设置、清理缓存并重新编译以验证修复效果。\n\n### 没有 XcodeBuildMCP 时\n- 开发者必须在终端手动输入冗长的 `xcodebuild` 命令，极易因参数拼写错误（如 scheme 名称大小写）导致构建失败。\n- 排查问题时需反复切换上下文，人工查阅 `.xcodeproj` 文件或构建日志来定位具体的配置项，效率极低。\n- AI 编程助手由于缺乏直接访问本地构建系统的权限，只能提供通用的理论建议，无法执行实际的编译操作或读取实时构建状态。\n- 每次修改配置后，都需要手动执行清理派生数据（DerivedData）和重新构建的步骤，流程繁琐且容易遗漏。\n- 在多 Scheme 项目中，难以快速确认当前激活的构建设置是否已同步应用到所有相关目标中。\n\n### 使用 XcodeBuildMCP 后\n- 开发者只需通过自然语言指令让 AI 调用 XcodeBuildMCP，即可自动执行精确的构建命令，彻底消除手动输入参数的错误风险。\n- AI 助手能直接利用工具读取项目真实的构建设置和日志，瞬间定位到具体的冲突依赖或配置缺失项。\n- XcodeBuildMCP 赋予 AI“双手”，使其能自主执行清理缓存、指定 Scheme 编译及运行测试等实际操作，实现从诊断到修复的闭环。\n- 复杂的“清理 - 构建”流程被封装为一步到位的自动化动作，大幅缩短了验证代码修改的反馈周期。\n- 工具可自动遍历并校验多 Scheme 项目的配置一致性，确保所有相关目标均应用了最新的构建策略。\n\nXcodeBuildMCP 通过将底层构建能力转化为 AI 可调用的标准接口，让智能助手真正具备了理解和操作 iOS\u002FmacOS 工程的全栈能力。","https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fgetsentry_XcodeBuildMCP_75906f55.png","getsentry","Sentry","https:\u002F\u002Foss.gittoolsai.com\u002Favatars\u002Fgetsentry_fff9ad16.png","Real-time crash reporting for your web apps, mobile apps, and games.",null,"support@sentry.io","sentry","https:\u002F\u002Fsentry.io","https:\u002F\u002Fgithub.com\u002Fgetsentry",[82,86,90,93,97],{"name":83,"color":84,"percentage":85},"TypeScript","#3178c6",89.4,{"name":87,"color":88,"percentage":89},"JavaScript","#f1e05a",3.8,{"name":91,"color":92,"percentage":10},"Makefile","#427819",{"name":94,"color":95,"percentage":96},"Swift","#F05138",2.1,{"name":98,"color":99,"percentage":100},"Shell","#89e051",1.8,5121,242,"2026-04-10T15:41:10","MIT","macOS","未说明",{"notes":108,"python":109,"dependencies":110},"仅支持 macOS 14.5 及以上版本。若通过 Homebrew 安装则不需要 Node.js，否则需要 Node.js 18+。必须安装 Xcode 16.x 或更高版本。在 Xcode 内部使用 Codex 或 Claude Code Agent 时，可能需要手动配置 PATH 环境变量以确保能找到 npx 命令。设备相关工具需要在 Xcode 中配置代码签名。","不需要",[111,112],"Node.js >= 18.x","Xcode >= 16.x",[13,52],[115,116,117,118,119,120,121],"mcp","mcp-server","model-context-protocol","model-context-protocol-servers","xcode","xcodebuild","tag-production","2026-03-27T02:49:30.150509","2026-04-11T05:02:58.003013",[125,130,135,140,145,150],{"id":126,"question_zh":127,"answer_zh":128,"source_url":129},28974,"为什么在 Claude Code 中添加该 MCP 服务器后会报错 \"tools.x.custom.name: String should have at most 64 characters\"？","这是因为 Anthropic API 对工具名称的长度限制为 64 个字符，而早期的工具名称超出了此限制。该问题已在版本 1.3.7 中修复，维护者缩短了工具名称以符合规范。请升级到最新版本（1.3.7 或更高）即可解决此问题。","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fissues\u002F3",{"id":131,"question_zh":132,"answer_zh":133,"source_url":134},28975,"如何通过 Wi-Fi 在真实硬件设备（而非模拟器）上运行和构建项目？","该功能已在版本 1.10.0 中发布。之前版本可能仅支持 USB 连接或无法正确识别 Wi-Fi 连接的设备状态。请确保将 `xcodebuildmcp` 升级到 1.10.0 或更高版本，即可通过 LLM 聊天直接在通过 Wi-Fi 连接的硬件设备上运行构建命令。","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fissues\u002F54",{"id":136,"question_zh":137,"answer_zh":138,"source_url":139},28976,"如何在 Claude Code 中正确配置全局安装的 XcodeBuildMCP v2.x 版本？","在 v2.x 版本中，启动命令需要包含 `mcp` 子命令。如果您是通过 npm 全局安装的，请在 `~\u002F.claude\u002Fmcp.json` 中使用以下配置：\n```json\n{\n  \"mcpServers\": {\n    \"XcodeBuildMCP\": {\n      \"command\": \"xcodebuildmcp\",\n      \"args\": [\"mcp\"]\n    }\n  }\n}\n```\n注意：不要直接使用旧的 `cli.js` 路径而不加 `mcp` 参数，也不要遗漏子命令，否则会导致重连失败。","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fissues\u002F210",{"id":141,"question_zh":142,"answer_zh":143,"source_url":144},28977,"构建日志输出太长导致 LLM 上下文溢出，如何只过滤出警告和错误信息？","目前社区用户反馈这是一个常见痛点，长日志（有时达 20MB）会消耗大量 Token。虽然官方尚未完全内置自动过滤标志，但建议的临时解决方案是让 Agent 执行构建时将输出重定向到文件，然后使用 `grep` 等命令提取关键错误信息。例如：\n```bash\nxcodebuild ... > tmp\u002Fbuild_output.log 2>&1 && grep -E \"error:|warning:\" tmp\u002Fbuild_output.log\n```\n您可以关注该项目的增强请求（Issue #68），未来可能会增加专门的过滤 flag。","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fissues\u002F68",{"id":146,"question_zh":147,"answer_zh":148,"source_url":149},28978,"该项目是否支持 Model Context Protocol (MCP) 的 Resources 特性？","是的，项目已更新支持 MCP Resources。维护者已实现了针对 `list_devices`、`diagnostic` 和 `swift_package_list` 等工具的 Resource 处理器。这意味着除了传统的 Tool Calling 外，Agent 现在可以通过资源 URI（如 `mcp:\u002F\u002Fxcodebuild\u002Fsimulators`）直接发现数据，从而改善开发体验并保持向后兼容。请确保使用包含这些更新的最新版本。","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fissues\u002F78",{"id":151,"question_zh":152,"answer_zh":153,"source_url":134},28979,"为什么工具显示我的 iPhone 已配对但未连接（Paired but not connected），即使它实际上已通过 Wi-Fi 连接？","这是一个已知的问题，在某些情况下工具检测逻辑过于严格，误报设备未连接。维护者已在后续版本中进行了调查和修复。如果遇到此问题，请首先尝试升级到最新版本（1.10.0+）。如果问题依旧，可以尝试重新插拔 USB 线触发一次握手，或者重启 Xcode 和相关服务，因为底层检测有时需要“暴力”重试才能识别状态。",[155,160,165,170,175,180,185,190,195,200,205,210,215,220,225,230,235,240,245,250],{"id":156,"version":157,"summary_zh":158,"released_at":159},197800,"v2.3.2","## 发布 v2.3.2\n\n### 修复\n\n- 提升了关闭过程中内部遥测的可靠性 ([#302](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fpull\u002F302))。\n\n### 选项 A — Homebrew（无需 Node.js）\n\n安装：\n```bash\nbrew tap getsentry\u002Fxcodebuildmcp\nbrew install xcodebuildmcp\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"xcodebuildmcp\",\n  \"args\": [\"mcp\"]\n}\n```\n\n### 选项 B — npm \u002F npx（Node.js 18+）\n\n安装：\n```bash\nnpm install -g xcodebuildmcp@latest\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n}\n```\n\n📦 **NPM 包**：https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F2.3.2\n","2026-03-31T11:58:45",{"id":161,"version":162,"summary_zh":163,"released_at":164},197801,"v2.3.1","## 发布 v2.3.1\n\n### 修复\n\n- 修复了 MCP 客户端（如 Codex）中不必要的工具确认提示，这些提示会将缺少批准注解视为高风险默认值 ([#297](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fpull\u002F297))。\n\n### 选项 A — Homebrew（无需 Node.js）\n\n安装：\n```bash\nbrew tap getsentry\u002Fxcodebuildmcp\nbrew install xcodebuildmcp\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"xcodebuildmcp\",\n  \"args\": [\"mcp\"]\n}\n```\n\n### 选项 B — npm \u002F npx（Node.js 18+）\n\n安装：\n```bash\nnpm install -g xcodebuildmcp@latest\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n}\n```\n\n📦 **NPM 包**：https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F2.3.1","2026-03-27T17:22:24",{"id":166,"version":167,"summary_zh":168,"released_at":169},197802,"v2.3.0","## 发布 v2.3.0\n\n### 新增\n\n- 添加了对会话默认值的环境变量支持（例如 `XCODEBUILDMCP_WORKSPACE_PATH`、`XCODEBUILDMCP_SCHEME`、`XCODEBUILDMCP_PLATFORM`），以便 MCP 客户端可以在配置中提供启动默认值，而无需项目配置文件（[#268](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fpull\u002F268)，由 [@detailobsessed](https:\u002F\u002Fgithub.com\u002Fdetailobsessed) 提交）。详情请参阅 [docs\u002FCONFIGURATION.md](docs\u002FCONFIGURATION.md#environment-variables)。\n- 为 `xcodebuildmcp setup` 命令添加了 `--format mcp-json` 标志，用于导出基于环境变量的 MCP 客户端配置块，而不是写入 `config.yaml` 文件（[#268](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fpull\u002F268)，由 [@detailobsessed](https:\u002F\u002Fgithub.com\u002Fdetailobsessed) 提交）。\n\n### 变更\n\n- 澄清了配置的分层机制：`session_set_defaults` 会覆盖 `config.yaml`，而 `config.yaml` 又会覆盖环境变量。详情请参阅 [docs\u002FCONFIGURATION.md](docs\u002FCONFIGURATION.md)（[#268](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fpull\u002F268)，由 [@detailobsessed](https:\u002F\u002Fgithub.com\u002Fdetailobsessed) 提交）。\n- 改进了在可选目标（如物理设备）不可用时 `xcodebuildmcp setup` 的可靠性。\n\n### 修复\n\n- 修复了在刷新模拟器元数据时，`.xcodebuildmcp\u002Fconfig.yaml` 文件会在启动时被修改的问题（[#230](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fissues\u002F230)）。\n- 修复了客户端断开连接后可能仍会残留的孤立 MCP 服务器进程问题（[#273](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fissues\u002F273)）。\n- 修复了 `list-schemes` CLI 命令缺少 `--project-path` 和 `--workspace-path` 标志的问题（[#271](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fpull\u002F271)）。\n- 修复了从命令行调用时 Xcode IDE 工作流工具无法正常工作的问题。\n- 修复了 Swift Package 工具在停止时未能正确等待进程退出的问题。\n\n### 方案 A — Homebrew（无需 Node.js）\n\n安装：\n```bash\nbrew tap getsentry\u002Fxcodebuildmcp\nbrew install xcodebuildmcp\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"xcodebuildmcp\",\n  \"args\": [\"mcp\"]\n}\n```\n\n### 方案 B — npm \u002F npx（Node.js 18+）\n\n安装：\n```bash\nnpm install -g xcodebuildmcp@latest\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n}\n```\n\n📦 **NPM 包**：https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F2.3.0","2026-03-16T22:11:40",{"id":171,"version":172,"summary_zh":173,"released_at":174},197803,"v2.2.1","## 发布 v2.2.1\n\n- 修复 AXe 打包问题。\n\n### 选项 A — Homebrew（无需 Node.js）\n\n安装：\n```bash\nbrew tap getsentry\u002Fxcodebuildmcp\nbrew install xcodebuildmcp\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"xcodebuildmcp\",\n  \"args\": [\"mcp\"]\n}\n```\n\n### 选项 B — npm \u002F npx（Node.js 18+）\n\n安装：\n```bash\nnpm install -g xcodebuildmcp@latest\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n}\n```\n\n📦 **NPM 包**：https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F2.2.1\n","2026-03-08T10:10:29",{"id":176,"version":177,"summary_zh":178,"released_at":179},197804,"v2.2.0","## 发布 v2.2.0\n\n### 新增功能\n\n- 新增 `get_coverage_report` 和 `get_file_coverage` 工具，用于从测试结果中检查代码覆盖率——可以查看按目标划分的摘要，也可以深入到特定文件的函数级覆盖率及未覆盖的代码行范围（[#240](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fpull\u002F240)，由 [@irangareddy](https:\u002F\u002Fgithub.com\u002Firangareddy) 提供）。详情请参阅 [docs\u002FTOOLS.md](docs\u002FTOOLS.md)。\n- 为物理设备新增了统一的构建与运行命令，与现有的模拟器工作流保持一致，使代理可以在一步内完成设备应用的构建和启动。\n- 通过 `xcodebuildmcp setup` 命令新增了一个交互式设置向导，引导您创建或更新 `.xcodebuildmcp\u002Fconfig.yaml` 文件——您可以选择工作流、挑选模拟器、设置方案和项目，并配置调试选项，而无需手动编辑 YAML 文件。同时，非交互模式仍适用于 CI 和脚本化场景。详情请参阅 [docs\u002FCONFIGURATION.md](docs\u002FCONFIGURATION.md)。\n\n  ```bash\n  xcodebuildmcp setup\n  ```\n- 在 `init` 命令中新增了 `AGENTS.md` 的生成功能，为您的项目提供规范化的代理工作流说明。\n- 在 `.xcodebuildmcp\u002Fconfig.yaml` 中增加了对自定义工作流的支持。您可以定义自己的工作流名称，并将其映射到明确的工具列表，然后像使用内置工作流一样，在 `enabledWorkflows` 中引用它们。这样，您就可以将代理可见的工具精确限制为您所需的工具。详情请参阅 [docs\u002FCONFIGURATION.md](docs\u002FCONFIGURATION.md#custom-workflows)。\n\n  ```yaml\n  enabledWorkflows: [\"my-workflow\"]\n  customWorkflows:\n    my-workflow:\n      - build_run_sim\n      - record_sim_video\n      - screenshot\n  ```\n- 新增了 AdaL CLI 的安装说明（[#242](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fpull\u002F242)，由 [@Abdulrahmansoliman](https:\u002F\u002Fgithub.com\u002FAbdulrahmansoliman) 提供）。\n\n### 变更\n\n- CLI 现在会自动从会话默认值中填充工具参数。如果您的配置文件设置了方案、项目路径或模拟器，那么每个 CLI 命令都会自动读取这些值，无需在每次调用时重复指定 `--scheme`、`--project-path` 等标志。详情请参阅 [docs\u002FCLI.md](docs\u002FCLI.md)。\n\n  ```yaml\n  # .xcodebuildmcp\u002Fconfig.yaml\n  sessionDefaults:\n    scheme: MyApp\n    projectPath: .\u002FMyApp.xcodeproj\n    simulatorName: iPhone 17 Pro\n  ```\n\n  ```bash\n  # 之前：每个命令都需要显式指定标志\n  xcodebuildmcp simulator build --scheme MyApp --project-path .\u002FMyApp.xcodeproj\n\n  # 现在：标志会自动从会话默认值中填充\n  xcodebuildmcp simulator build\n  ```\n\n  这一功能同样适用于会话默认值配置文件，尤其适用于单体仓库。您可以为每个子项目定义一个配置文件，CLI 将使用当前活动配置文件中的值。如果需要为某个命令覆盖配置文件，可以使用 `--profile` 参数。详情请参阅 [docs\u002FSESSION_DEFAULTS.md](docs\u002FSESSION_DEFAULTS.md#namespaced-profiles)。\n\n  ```yaml\n  # .xcodebuildmcp\u002Fconfig.yaml\n  schemaVersion: 1\n  sessionDefaultsProfiles:\n    calculator:\n      workspacePath: .\u002FiOS_Calculator\u002FCalculatorApp.xcworkspace\n      scheme: CalculatorApp\n      simulatorName: iPhone 17 Pro\n  ```","2026-03-07T21:49:15",{"id":181,"version":182,"summary_zh":183,"released_at":184},197805,"v2.1.0","## 发布 v2.1.0\n\n### 新增功能\n\n- 新增 `xcodebuildmcp init` CLI 命令，用于安装代理技能，取代独立的 `install-skill.sh` 脚本。支持自动检测 AI 客户端（Claude Code、Cursor、Codex），对于不支持的客户端可使用 `--print` 参数输出信息，也可通过 `--uninstall` 参数进行卸载。详情请参阅 [docs\u002FSKILLS.md](docs\u002FSKILLS.md#install)。\n- 新增命名空间会话默认配置文件，允许您保存并切换不同的项目\u002F方案\u002F模拟器配置，而无需每次重新配置。详情请参阅 [docs\u002FSESSION_DEFAULTS.md](docs\u002FSESSION_DEFAULTS.md#namespaced-profiles)。\n- 新增支持在会话默认配置中持久化自定义环境变量（[#235](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fpull\u002F235)，由 [@kamal](https:\u002F\u002Fgithub.com\u002Fkamal) 提供）。详情请参阅 [docs\u002FSESSION_DEFAULTS.md](docs\u002FSESSION_DEFAULTS.md#persisting-defaults)。\n- 新增 Kiro 客户端设置说明（[#222](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fpull\u002F222)，由 [@manojmahapatra](https:\u002F\u002Fgithub.com\u002Fmanojmahapatra) 提供）。\n\n### 变更内容\n\n- 启用 Xcode IDE 工作流时，MCP 启动速度更快——连接后工具可更快可用（[#210](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fissues\u002F210)）。详情请参阅 [docs\u002FXCODE_IDE_MCPBRIDGE.md](docs\u002FXCODE_IDE_MCPBRIDGE.md)。\n- 代理现在对模拟器运行意图使用构建与运行一体化工具，避免了冗余的单独构建步骤。\n- 改进了下一步建议，使代理在每次调用工具后能获得更准确的后续操作指导。\n- 更新了 UI 自动化点击指引，优先选择标签和 ID 目标，从而减少代理错误。\n\n### 修复问题\n\n- 修复了当构建输出包含回显源代码时出现的误报错误和警告检测问题（[#218](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fpull\u002F218)，由 [@nebooz](https:\u002F\u002Fgithub.com\u002Fnebooz) 提供）。\n- 修复了 CLI 技能文件中过时的工具名称和参数（[#217](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fpull\u002F217)，由 [@pocketpixels](https:\u002F\u002Fgithub.com\u002Fpocketpixels) 提供）。\n- 修正了 Sentry 遥测范围，使其仅捕获内部运行时故障，移除了不必要的数据收集（[#204](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fissues\u002F204)）。\n- 修复了发布工作流中的 Shell 注入漏洞（[#229](https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP\u002Fpull\u002F229)）。\n- 改进了 `doctor` 命令中的隐私脱敏处理，更好地保护默认输出中的项目名称和路径。\n\n### 移除内容\n\n- 移除了 `scripts\u002Finstall-skill.sh`，改用 `xcodebuildmcp init` 命令。\n\n此外，还进行了多项内部改进，以提升稳定性、性能和代码质量。\n\n### 方案 A — Homebrew（无需 Node.js）\n\n安装：\n```bash\nbrew tap getsentry\u002Fxcodebuildmcp\nbrew install xcodebuildmcp\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"xcodebuildmcp\",\n  \"args\": [\"mcp\"]\n}\n```\n\n### 方案 B — npm \u002F npx（Node.js 18+）\n\n安装：\n```bash\nnpm install -g xcodebuildmcp@latest\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n}\n```\n\n📦 **NPM 包**：https:\u002F\u002Fwww.npm","2026-02-23T13:16:02",{"id":186,"version":187,"summary_zh":188,"released_at":189},197806,"v2.0.7","## 发布 v2.0.7\n\n### 变更\n\n- XcodeBuildMCP 已迁移到 [getsentry](https:\u002F\u002Fgithub.com\u002Fgetsentry) GitHub 组织。Homebrew 用户应切换到新的 tap：`brew untap cameroncooke\u002Fxcodebuildmcp && brew tap getsentry\u002Fxcodebuildmcp`。npm 和 npx 用户不受影响。\n\n### 选项 A — Homebrew（无需 Node.js）\n\n安装：\n```bash\nbrew tap getsentry\u002Fxcodebuildmcp\nbrew install xcodebuildmcp\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"xcodebuildmcp\",\n  \"args\": [\"mcp\"]\n}\n```\n\n### 选项 B — npm \u002F npx（Node.js 18+）\n\n安装：\n```bash\nnpm install -g xcodebuildmcp@latest\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n}\n```\n\n📦 **NPM 包**：https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F2.0.7","2026-02-10T23:27:31",{"id":191,"version":192,"summary_zh":193,"released_at":194},197807,"v2.0.6","## 发布 v2.0.6\n\n### 变更\n\n- XcodeBuildMCP 已迁移到 [getsentry](https:\u002F\u002Fgithub.com\u002Fgetsentry) 的 GitHub 组织。Homebrew 用户应切换到新的 tap：`brew untap cameroncooke\u002Fxcodebuildmcp && brew tap getsentry\u002Fxcodebuildmcp`。npm 和 npx 用户不受影响。\n\n### 选项 A — Homebrew（无需 Node.js）\n\n安装：\n```bash\nbrew tap getsentry\u002Fxcodebuildmcp\nbrew install xcodebuildmcp\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"xcodebuildmcp\",\n  \"args\": [\"mcp\"]\n}\n```\n\n### 选项 B — npm \u002F npx（Node.js 18+）\n\n安装：\n```bash\nnpm install -g xcodebuildmcp@latest\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n}\n```\n\n📦 **NPM 包**: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F2.0.6\n","2026-02-10T22:59:00",{"id":196,"version":197,"summary_zh":198,"released_at":199},197808,"v2.0.5","## 发布 v2.0.5\n\n### 新增\n\n- Homebrew 安装方式（`brew tap cameroncooke\u002Fxcodebuildmcp && brew install xcodebuildmcp`）—— 安装一个自包含的二进制文件，无需 Node.js 依赖。\n\n### 移除\n\n- Smithery 分发渠道。\n\n### 方案 A — Homebrew（无需 Node.js）\n\n安装：\n```bash\nbrew tap cameroncooke\u002Fxcodebuildmcp\nbrew install xcodebuildmcp\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"xcodebuildmcp\",\n  \"args\": [\"mcp\"]\n}\n```\n\n### 方案 B — npm \u002F npx（Node.js 18+）\n\n安装：\n```bash\nnpm install -g xcodebuildmcp@latest\n```\n\nMCP 配置：\n```json\n\"XcodeBuildMCP\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"xcodebuildmcp@latest\", \"mcp\"]\n}\n```\n\n📦 **NPM 包**：https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F2.0.5","2026-02-10T14:50:02",{"id":201,"version":202,"summary_zh":203,"released_at":204},197809,"v2.0.0","## 发布 v2.0.0\n\n### 全新！命令行界面\n\nXcodeBuildMCP 现在包含一流的命令行界面，可供直接在终端使用、编写脚本以及集成到 CI 流程中。通过 MCP 可用的所有工具，现在都可以从命令行访问。\n\n```bash\nnpm install -g xcodebuildmcp@beta\nxcodebuildmcp tools # 列出可用工具\nxcodebuildmcp simulator build-and-run --scheme MyApp --project-path .\u002FMyApp.xcodeproj\n```\n\n有状态的操作（日志捕获、调试、视频录制）由每个工作区的后台进程支持，该进程会自动启动，并在空闲后关闭。完整文档请参阅 [docs\u002FCLI.md](docs\u002FCLI.md)。\n\n### 全新！配置文件\n\n通过 `.xcodebuildmcp\u002Fconfig.yaml` 进行项目级配置，取代了对环境变量的需求。您可以在一处设置项目路径、方案、模拟器、启用的工作流、调试设置等。环境变量仍然有效，但配置文件具有更高优先级。\n\n```yaml\nschemaVersion: 1\nenabledWorkflows:\n  - simulator\n  - ui-automation\n  - debugging\nsessionDefaults:\n  scheme: MyApp\n  projectPath: .\u002FMyApp.xcodeproj\n  simulatorName: iPhone 16\n```\n\n完整参考请参阅 [docs\u002FCONFIGURATION.md](docs\u002FCONFIGURATION.md)。\n\n### 全新！Xcode IDE 集成\n\nXcodeBuildMCP 现在可以代理 Xcode 26.3 内置 MCP 桥接中的工具，使您的代理能够访问 Xcode IDE 的功能，例如预览渲染、问题导航器和文档搜索。启用 `xcode-ide` 工作流即可使用此功能。其中包含了 Codex Agent 和 Claude Code Agent 在 Xcode 中的设置说明。详情请参阅 [docs\u002FXCODE_IDE_MCPBRIDGE.md](docs\u002FXCODE_IDE_MCPBRIDGE.md)。\n\n### 新增\n\n- **LLDB 调试**：通过您的代理将调试器附加到模拟器应用上，设置断点、检查变量、查看调用栈并运行 LLDB 命令——所有操作均可完成。支持 DAP 和 LLDB-CLI 后端。调试工具详情请参阅 [docs\u002FTOOLS.md](docs\u002FTOOLS.md)。\n- **会话默认值持久化**：现在可以通过 `persist: true` 将会话默认值保存到配置文件中，这样您偏好的项目、方案和模拟器将在不同会话之间保持记忆。\n- **日志子系统过滤**：可以根据子系统过滤模拟器日志捕获——可选择 `app`（默认）、`all`、`swiftui`（用于 `Self._printChanges()` 输出），或自定义子系统列表。\n- **代理技能**：可选的技能文件，为您的代理提供关于 MCP 服务器或 CLI 使用说明。可通过提供的 Shell 脚本安装，也可手动安装。详情请参阅 [docs\u002FSKILLS.md](docs\u002FSKILLS.md)。\n- **MCP 工具注解**：所有工具现在都包含 MCP 标准注解（只读 vs. 破坏性、幂等性等），供支持这些注解的客户端使用。\n- **模拟器名称解析**：会话默认值现在接受模拟器名称，并自动将其解析为设备 ID。\n- **启动环境变量**：启动工具现在接受一个可选的 `env` 对象，以便在模拟器或设备上启动应用时传递运行时环境变量。\n\n### 变更\n\n- 模拟器工具现已成为默认工作流。此前所有工作流","2026-02-08T21:12:18",{"id":206,"version":207,"summary_zh":208,"released_at":209},197810,"v2.0.0-beta.1","## Release v2.0.0-beta.1\r\n\r\n### Installation\r\n```bash\r\nnpm install -g xcodebuildmcp@2.0.0-beta.1\r\n```\r\n\r\nOr use with npx:\r\n```bash\r\nnpx xcodebuildmcp@2.0.0-beta.1\r\n```\r\n\r\n📦 **NPM Package**: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F2.0.0-beta.1\r\n\r\n## Release notes\r\n\r\n### Breaking\r\n\r\n#### Workflow selection\r\n\r\n- By default when the `enabledWorkflows` configuration option or `XCODEBUILDMCP_ENABLED_WORKFLOWS` environment variable is not set or empty, XcodeBuildMCP will default to loading only the `simulator` workflow. This is a change in behaviour; previously it would load all workflows and therefore tools by default.\r\n\r\nThis change reduces the number of tools loaded by default and requires the user to opt in to enable additional sets of tools based on their project or workflow requirements.\r\n\r\nThe simulator workflow is the default because it is the most common use case based on opt-in analytics data.\r\n\r\nFor more information see the [CONFIGURATION.md](docs\u002FCONFIGURATION.md) documentation.\r\n\r\n- Tool names and descriptions have been made more concise to reduce token consumption. Tool argument names that are self-explanatory have had their descriptions removed entirely.\r\n\r\n#### XcodeBuildMCP is now a first-class CLI\r\n\r\n- XcodeBuildMCP now has a first class CLI interface. This allows you or your agent to invoke tools directly from the terminal which can help reduce the upfront context costs of MCP.\r\n\r\n- When calling `xcodebuildmcp` without any arguments it will default to CLI mode, this is a **breaking** change, you must update your mcp client's configuration to pass the `mcp` argument:\r\n\r\nFrom:\r\n```json\r\n\"XcodeBuildMCP\": {\r\n  \"command\": \"npx\",\r\n  \"args\": [\r\n    \"-y\",\r\n    \"xcodebuildmcp@latest\"\r\n  ]\r\n}\r\n```\r\n\r\nTo:\r\n```json\r\n\"XcodeBuildMCP\": {\r\n  \"command\": \"npx\",\r\n  \"args\": [\r\n    \"-y\",\r\n    \"xcodebuildmcp@2.0.0-beta.1\",\r\n    \"mcp\" \u002F\u002F \u003C--- add this argument\r\n  ]\r\n}\r\n```\r\n\r\nTo lean more about the CLI interface see the [CLI.md](docs\u002FCLI.md) documentation.\r\n\r\n### New!\r\n- Add DAP-based debugger backend and simulator debugging toolset (attach, breakpoints, stack, variables, LLDB command).\r\n- XcodeBuildMCP uses a new project config file at `.xcodebuildmcp\u002Fconfig.yaml` for runtime configuration, this is a more flexible and powerful way to configure XcodeBuildMCP than environment variables.\r\n\r\n### Added\r\n- Add session-status MCP resource with session identifiers.\r\n- Add UI automation guard that blocks UI tools when the debugger is paused.\r\n- Add `manage-workflows` tool to allow agents to change the workflows enable\u002Fdisabling tools at runtime. This requires clients to support tools changed notifications. (opt-in only)\r\n- Add XcodeBuildMCP skill to improve MCP client tool use\u002Fdiscovery, this needs to be installed see [README.md](README.md) for more information.\r\n- Added support for session-aware defaults that are persisted between sessions in the config file.\r\n\r\n### Changed\r\n- Migrate to Zod v4.\r\n- Remove dynamic tool discovery (`discover_tools`) and `XCODEBUILDMCP_DYNAMIC_TOOLS`. Use `XCODEBUILDMCP_ENABLED_WORKFLOWS` to limit startup tool registration.\r\n- Add MCP tool annotations to all tools.\r\n\r\n### Fixed\r\n- Update UI automation guard guidance to point at `debug_continue` when paused.\r\n- Fix tool loading bugs in static tool registration.\r\n- Fix xcodemake command argument corruption when project directory path appears as substring in non-path arguments.\r\n- Fix snapshot_ui warning state being isolated per UI automation tool, causing false warnings.\r\n- Fixed screenshot tool capturing rotated images when simulator is in landscape orientation by detecting window dimensions and applying +90° rotation to correct the framebuffer capture. ([`#186`](https:\u002F\u002Fgithub.com\u002Fcameroncooke\u002FXcodeBuildMCP\u002Fpull\u002F186) by [`@VincentStark`](https:\u002F\u002Fgithub.com\u002FVincentStark))\r\n- Fixed Sentry ESM compatibility by upgrading `@sentry\u002Fnode` from 10.5.0 to 10.37.0 and `@sentry\u002Fcli` from 2.43.1 to 3.1.0 (Fixes XCODEBUILD-MCP-13SX)\r\n","2026-02-02T23:31:13",{"id":211,"version":212,"summary_zh":213,"released_at":214},197811,"v1.15.1","## Release v1.15.1\n\n### Installation\n```bash\nnpm install -g xcodebuildmcp@1.15.1\n```\n\nOr use with npx:\n```bash\nnpx xcodebuildmcp@1.15.1\n```\n\n📦 **NPM Package**: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F1.15.1\n","2025-12-20T11:44:52",{"id":216,"version":217,"summary_zh":218,"released_at":219},197812,"v1.15.0","## Release v1.15.0\n\n### Installation\n```bash\nnpm install -g xcodebuildmcp@1.15.0\n```\n\nOr use with npx:\n```bash\nnpx xcodebuildmcp@1.15.0\n```\n\n📦 **NPM Package**: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F1.15.0\n","2025-12-15T20:42:26",{"id":221,"version":222,"summary_zh":223,"released_at":224},197813,"v1.15.0-beta.0","## Release v1.15.0-beta.0\r\n\r\n### Features\r\n- Bundled AXe binary and frameworks for zero-setup UI automation\r\n- No manual installation required - works out of the box\r\n\r\n### Installation\r\n```bash\r\nnpm install -g xcodebuildmcp@1.15.0-beta.0\r\n```\r\n\r\nOr use with npx:\r\n```bash\r\nnpx xcodebuildmcp@1.15.0-beta.0\r\n```\r\n\r\n📦 **NPM Package**: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F1.15.0-beta.0\r\n\r\n### What's Included\r\n- Latest AXe binary from [cameroncooke\u002Faxe](https:\u002F\u002Fgithub.com\u002Fcameroncooke\u002Faxe)\r\n- All required frameworks (FBControlCore, FBDeviceControl, FBSimulatorControl, XCTestBootstrap)\r\n- Full XcodeBuildMCP functionality with UI automation support\r\n","2025-11-20T21:37:05",{"id":226,"version":227,"summary_zh":228,"released_at":229},197814,"v1.14.1","## Release v1.14.1\n\n### Features\n- Bundled AXe binary and frameworks for zero-setup UI automation\n- No manual installation required - works out of the box\n\n### Installation\n```bash\nnpm install -g xcodebuildmcp@1.14.1\n```\n\nOr use with npx:\n```bash\nnpx xcodebuildmcp@1.14.1\n```\n\n📦 **NPM Package**: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F1.14.1\n\n### What's Included\n- Latest AXe binary from [cameroncooke\u002Faxe](https:\u002F\u002Fgithub.com\u002Fcameroncooke\u002Faxe)\n- All required frameworks (FBControlCore, FBDeviceControl, FBSimulatorControl, XCTestBootstrap)\n- Full XcodeBuildMCP functionality with UI automation support\n","2025-09-22T20:18:54",{"id":231,"version":232,"summary_zh":233,"released_at":234},197815,"v1.14.0","## Release v1.14.0\n\n### Features\n- Bundled AXe binary and frameworks for zero-setup UI automation\n- No manual installation required - works out of the box\n\n### Installation\n```bash\nnpm install -g xcodebuildmcp@1.14.0\n```\n\nOr use with npx:\n```bash\nnpx xcodebuildmcp@1.14.0\n```\n\n📦 **NPM Package**: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F1.14.0\n\n### What's Included\n- Latest AXe binary from [cameroncooke\u002Faxe](https:\u002F\u002Fgithub.com\u002Fcameroncooke\u002Faxe)\n- All required frameworks (FBControlCore, FBDeviceControl, FBSimulatorControl, XCTestBootstrap)\n- Full XcodeBuildMCP functionality with UI automation support\n","2025-09-22T19:58:40",{"id":236,"version":237,"summary_zh":238,"released_at":239},197816,"v1.13.1","## Release v1.13.1\n\n### Features\n- Bundled AXe binary and frameworks for zero-setup UI automation\n- No manual installation required - works out of the box\n\n### Installation\n```bash\nnpm install -g xcodebuildmcp@1.13.1\n```\n\nOr use with npx:\n```bash\nnpx xcodebuildmcp@1.13.1\n```\n\n📦 **NPM Package**: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F1.13.1\n\n### What's Included\n- Latest AXe binary from [cameroncooke\u002Faxe](https:\u002F\u002Fgithub.com\u002Fcameroncooke\u002Faxe)\n- All required frameworks (FBControlCore, FBDeviceControl, FBSimulatorControl, XCTestBootstrap)\n- Full XcodeBuildMCP functionality with UI automation support\n","2025-09-21T21:23:49",{"id":241,"version":242,"summary_zh":243,"released_at":244},197817,"v1.12.10","## Release v1.12.10\n\n### Features\n- Bundled AXe binary and frameworks for zero-setup UI automation\n- No manual installation required - works out of the box\n\n### Installation\n```bash\nnpm install -g xcodebuildmcp@1.12.10\n```\n\nOr use with npx:\n```bash\nnpx xcodebuildmcp@1.12.10\n```\n\n📦 **NPM Package**: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F1.12.10\n\n### What's Included\n- Latest AXe binary from [cameroncooke\u002Faxe](https:\u002F\u002Fgithub.com\u002Fcameroncooke\u002Faxe)\n- All required frameworks (FBControlCore, FBDeviceControl, FBSimulatorControl, XCTestBootstrap)\n- Full XcodeBuildMCP functionality with UI automation support\n","2025-09-10T14:44:47",{"id":246,"version":247,"summary_zh":248,"released_at":249},197818,"v1.12.8","## Release v1.12.8\n\n### Features\n- Bundled AXe binary and frameworks for zero-setup UI automation\n- No manual installation required - works out of the box\n\n### Installation\n```bash\nnpm install -g xcodebuildmcp@1.12.8\n```\n\nOr use with npx:\n```bash\nnpx xcodebuildmcp@1.12.8\n```\n\n📦 **NPM Package**: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F1.12.8\n\n### What's Included\n- Latest AXe binary from [cameroncooke\u002Faxe](https:\u002F\u002Fgithub.com\u002Fcameroncooke\u002Faxe)\n- All required frameworks (FBControlCore, FBDeviceControl, FBSimulatorControl, XCTestBootstrap)\n- Full XcodeBuildMCP functionality with UI automation support\n","2025-09-09T19:54:24",{"id":251,"version":252,"summary_zh":253,"released_at":254},197819,"v1.12.7","## Release v1.12.7\n\n### Features\n- Bundled AXe binary and frameworks for zero-setup UI automation\n- No manual installation required - works out of the box\n\n### Installation\n```bash\nnpm install -g xcodebuildmcp@1.12.7\n```\n\nOr use with npx:\n```bash\nnpx xcodebuildmcp@1.12.7\n```\n\n📦 **NPM Package**: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fxcodebuildmcp\u002Fv\u002F1.12.7\n\n### What's Included\n- Latest AXe binary from [cameroncooke\u002Faxe](https:\u002F\u002Fgithub.com\u002Fcameroncooke\u002Faxe)\n- All required frameworks (FBControlCore, FBDeviceControl, FBSimulatorControl, XCTestBootstrap)\n- Full XcodeBuildMCP functionality with UI automation support\n","2025-09-09T18:17:14"]