xcode-cloud-mcp
Local MCP server enabling agents to track Xcode Cloud builds and access TestFlight crash reports through the App Store Connect API.
README
xcode-cloud-mcp (self-owned)
Local Model Context Protocol server so your agents can track Xcode Cloud builds via the App Store Connect API.
It also reads TestFlight beta-feedback crash reports. These are distinct from Xcode Cloud CI failures: they are reports a TestFlight tester explicitly submitted, including the raw crash log for a selected report.
This is your private copy — no third-party Xcode Cloud MCP package. Only well-known dependencies:
| Package | Why |
|---|---|
@modelcontextprotocol/sdk |
MCP stdio server |
jose |
ES256 JWT for App Store Connect |
zod |
Tool argument schemas |
What agents can do
| Tool | Purpose |
|---|---|
list_products |
Discover Xcode Cloud products |
list_apps |
Discover App Store Connect apps for TestFlight diagnostics |
list_workflows |
Workflows for a product |
get_workflow |
Single workflow details |
start_build |
Trigger a build (optional git ref) |
cancel_build |
Cancel an in-flight build |
list_build_runs |
Recent runs for a workflow |
get_build_run |
Status snapshot |
get_build_actions |
Per-action progress (build/test/archive) |
wait_for_build |
Poll until terminal status or timeout |
get_build_issues |
Errors / warnings |
list_action_artifacts |
Logs / result bundles metadata |
get_build_logs |
Download log text for an action |
get_test_results |
Tests for an action |
get_test_failures |
Failed tests across a run |
list_beta_feedback_crashes |
Privacy-minimized TestFlight crash-report summaries |
get_beta_crash_log |
Raw log for one selected TestFlight crash report |
Typical agent flow
list_products→list_workflowsstart_buildorlist_build_runsfor an existing runwait_for_build/get_build_run+get_build_actions- On failure:
get_build_issues,get_test_failures,get_build_logs
TestFlight crash-report flow
list_apps(optionally filter by bundle id)list_beta_feedback_crasheswith the selectedappIdget_beta_crash_logfor a specificsubmissionId
The listing intentionally omits tester email and the free-form feedback
comment. Raw crash logs are bounded by maxChars (80,000 by default) and
should be retrieved only when needed for diagnosis.
Prerequisites
- Node.js 20+
- Apple Developer account with Xcode Cloud
- App Store Connect API key (Developer or App Manager is usually enough)
Create an API key
- App Store Connect → Users and Access → Integrations → App Store Connect API
- Generate a key → download the
.p8(once only) - Note Key ID and Issuer ID
Setup
cd ~/Desktop/projects/xcode-cloud-mcp
npm install
npm run build
Copy env template and fill in values:
cp .env.example .env
APP_STORE_KEY_ID=YOUR_KEY_ID
APP_STORE_ISSUER_ID=YOUR_ISSUER_UUID
APP_STORE_PRIVATE_KEY_PATH=/Users/you/path/to/AuthKey_XXXXXXXXXX.p8
Prefer APP_STORE_PRIVATE_KEY_PATH over pasting PEM into config.
Run locally (smoke)
export $(grep -v '^#' .env | xargs)
npm run dev
# process waits on stdio — that's correct for MCP
Quick API check without MCP (optional):
node --import tsx -e '
import { loadConfig } from "./src/config.ts";
import { AppStoreAuth } from "./src/auth.ts";
import { AppStoreConnectClient } from "./src/client.ts";
const c = loadConfig();
const client = new AppStoreConnectClient(c, new AppStoreAuth(c));
const doc = await client.get("/v1/ciProducts", { limit: 5 });
console.log(JSON.stringify(doc, null, 2));
'
Grok config
Add to ~/.grok/config.toml (user scope) or project .grok/config.toml:
[mcp_servers.xcode-cloud]
command = "node"
args = ["/Users/deepanshu/Desktop/projects/xcode-cloud-mcp/dist/index.js"]
startup_timeout_sec = 30
env = {
APP_STORE_KEY_ID = "YOUR_KEY_ID",
APP_STORE_ISSUER_ID = "YOUR_ISSUER_UUID",
APP_STORE_PRIVATE_KEY_PATH = "/Users/deepanshu/Desktop/projects/AuthKey_XXXXXXXXXX.p8"
}
Or via CLI:
grok mcp add xcode-cloud \
-e APP_STORE_KEY_ID=YOUR_KEY_ID \
-e APP_STORE_ISSUER_ID=YOUR_ISSUER_UUID \
-e APP_STORE_PRIVATE_KEY_PATH=/Users/deepanshu/Desktop/projects/AuthKey_XXXXXXXXXX.p8 \
-- node /Users/deepanshu/Desktop/projects/xcode-cloud-mcp/dist/index.js
Then /mcps → confirm tools, or:
grok mcp doctor xcode-cloud
Cursor
~/.cursor/mcp.json:
{
"mcpServers": {
"xcode-cloud": {
"command": "node",
"args": ["/Users/deepanshu/Desktop/projects/xcode-cloud-mcp/dist/index.js"],
"env": {
"APP_STORE_KEY_ID": "YOUR_KEY_ID",
"APP_STORE_ISSUER_ID": "YOUR_ISSUER_UUID",
"APP_STORE_PRIVATE_KEY_PATH": "/Users/deepanshu/Desktop/projects/AuthKey_XXXXXXXXXX.p8"
}
}
}
}
Security
- Never commit
.p8,.env, or keys - Restrict key role to the minimum needed
- Rotate keys if they leak
- This server speaks only to
api.appstoreconnect.apple.com(override only viaASC_API_BASE_URL)
Project layout
src/
index.ts # stdio entry
config.ts # env loading
auth.ts # JWT ES256
client.ts # ASC REST client
types.ts # CI resource shapes
format.ts # tool response helpers
tools/register.ts # MCP tools
License
Private — for your use only.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。