xcode-cloud-mcp
Related Servers
Alternatives to xcode-cloud-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceLocal MCP server enabling agents to track Xcode Cloud builds and access TestFlight crash reports through the App Store Connect API.6 npmApache 2.0
- AlicenseBqualityFmaintenanceAn MCP server to communicate with the App Store Connect API for iOS Developers2593 npm331MIT
- AlicenseNot gradedqualityCmaintenanceApp Store Connect MCP Server (Swift) that manages apps, builds, TestFlight, metadata, reviews natively on macOSMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with Xcode build tools, iOS Simulator, and Apple notarization services.5 npm5MIT
- AlicenseAqualityCmaintenanceAn MCP server that drives the full App Store release cycle for iOS and macOS apps: version bump, archive + TestFlight upload, metadata, review submission, and status.833 npmMIT
- AlicenseNot gradedqualityAmaintenanceThis MCP server provides access to Apple's App Store Connect API. It allows users to inspect apps, versions, builds, TestFlight groups, sales, users, and optionally edit metadata and manage testers.345 npm2MIT
TDQS
Scored across 17 tools
Several tools overlap in the build/test/log resolution space: get_build_logs vs materialize_build_logs both resolve a build and download/extract logs, and get_test_results already includes failed tests that get_failed_tests returns separately. The workflow-config tools (update_workflow_general/start_conditions/actions, configure_manual_release_candidate) are mostly distinct, but the log/test cluster will cause misselection.
Every tool follows a consistent snake_case verb_noun pattern (list_workflows, get_build_logs, update_workflow_actions, cleanup_saved_logs). No camelCase or mixed conventions appear, and the single longer exception (configure_manual_release_candidate) still matches the scheme.
17 tools is slightly on the heavy side but the server spans several sub-domains (products, workflows, builds, logs, tests), so most tools earn their place. The count is reasonable, though merging the redundant log materialization tools would tighten it.
The surface covers the lifecycle well: products, workflow listing/details/enablement, granular workflow updates, build start/list/issues, log retrieval/cleanup, and test result/artifact access. Minor gaps remain (no workflow create/delete, and build cancellation is unsupported by Apple's API), but core agent workflows are covered.