xcode-cloud-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APP_STORE_KEY_ID | No | App Store Connect API key ID (alias) | |
| APP_STORE_ISSUER_ID | No | App Store Connect API issuer ID (alias) | |
| APP_STORE_PRIVATE_KEY | No | App Store Connect private key (alias) | |
| APPSTORE_CONNECT_API_KEY_ID | No | App Store Connect API key ID (primary) | |
| APPSTORE_CONNECT_API_ISSUER_ID | No | App Store Connect API issuer ID (primary) | |
| APPSTORE_CONNECT_API_KEY_CONTENT | No | App Store Connect private key content (PEM or escaped \n) (primary) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_productsA | List Xcode Cloud products available to the configured App Store Connect account. Automatically paginates through all results. |
| list_workflowsA | List workflows for a given Xcode Cloud product. Automatically paginates through all results. |
| get_workflow_detailsA | Retrieve detailed Xcode Cloud workflow configuration, including environment, start conditions, actions, and enabled state. |
| list_build_runsB | List recent build runs for a workflow, optionally filtered by outcome. Automatically paginates through build runs. Use limit to cap the number of results returned. |
| get_build_issuesC | Resolve a build and return build identity plus issue counts from Xcode Cloud. |
| get_build_logsC | Resolve a build, download text-like log artifacts, save them under a temporary local directory, and return a compact summary with failed tests, highlights, and saved log paths that local agents can inspect with grep or cat. |
| materialize_build_logsB | Resolve a build, download and extract text-like log artifacts into a local temporary directory, and return saved file paths for grep or cat based investigation. |
| cleanup_saved_logsA | Remove saved local log directories either for one build run or for all directories older than a retention window. |
| get_test_resultsC | Resolve a build and return build-level test summary information, saved local log paths, detected failed tests, and result bundle metadata. |
| get_failed_testsC | Resolve a build, ensure logs are materialized locally, and return only the detected failed tests with their assertion messages when available. |
| get_test_artifactsC | Resolve a build and return metadata plus download URLs for UI test artifacts and result bundles. |
| configure_manual_release_candidateA | Replace all actions with one macOS archive and all start conditions with manual builds from one exact branch. Requires TestFlight Deployment Preparation. Preserves enabled state. Does not configure tester-group post-actions; use Xcode or App Store Connect for those. |
| set_workflow_enabledB | Explicitly enable or disable one Xcode Cloud workflow. |
| update_workflow_generalC | Explicitly update general workflow fields such as name, description, and clean build behavior. |
| update_workflow_start_conditionsC | Explicitly update workflow start conditions. Pass null to remove a condition. |
| update_workflow_actionsB | Explicitly replace the full workflow actions array. This should be used only when the caller intends to send the final desired action list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Several tools overlap significantly in purpose: get_build_logs, materialize_build_logs, and get_test_results all resolve a build and download/extract logs locally, with get_build_logs and materialize_build_logs being nearly indistinguishable. get_failed_tests and get_test_artifacts also resolve builds and return test-related metadata, adding further ambiguity. The workflow update tools (update_workflow_general, update_workflow_actions, update_workflow_start_conditions, configure_manual_release_candidate) are more distinct, but the log/test cluster is confusing.
Most tool names follow a consistent verb_noun pattern (get_failed_tests, list_products, update_workflow_general). There is a minor deviation with 'configure_manual_release_candidate' using 'configure' instead of 'update' or 'set', and 'set_workflow_enabled' uses 'set' while others use 'update', but overall the pattern is predictable.
16 tools is slightly heavy for the Xcode Cloud domain but still within a reasonable range. Many tools are needed to cover workflows, builds, tests, and logs, though some redundancy (e.g., multiple log-extraction tools) suggests the count could be trimmed.
The server covers key operations: listing products/workflows, getting workflow details, updating various workflow aspects, listing/analyzing builds, retrieving test results and logs, and cleaning up logs. Minor gaps exist, such as no tool to start a build or manage products, but the core workflows for monitoring and configuration are well-covered.