io.github.gjeltep/app-store-connect-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APP_STORE_APP_ID | No | Your app ID (optional) | |
| APP_STORE_KEY_ID | Yes | Your App Store Connect API key ID | |
| APP_STORE_KEY_TYPE | No | Key type: 'team' or 'individual' (optional) | |
| APP_STORE_ISSUER_ID | Yes | Your App Store Connect issuer ID | |
| APP_STORE_PRIVATE_KEY_PATH | Yes | Path to your App Store Connect private key (.p8) file |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analytics_report_requests_listB | [Analytics/Requests] List analytics report requests for an app. |
| report_requests_createC | [Analytics/Requests] Create a new analytics report request. |
| report_requests_getB | [Analytics/Requests] Get detailed information about a specific analytics report request. |
| report_requests_list_reportsA | [Analytics/Reports] List reports for a specific analytics report request. |
| reports_getC | [Analytics/Reports] Get detailed information about a specific analytics report. |
| reports_list_instancesA | [Analytics/Reports] List instances for a specific analytics report. |
| report_instances_getC | [Analytics/Reports] Get detailed information about a specific analytics report instance. |
| report_instances_list_segmentsB | [Analytics/Segments] List segments for a specific analytics report instance. |
| report_segments_getA | [Analytics/Segments] Get detailed information about a specific analytics report segment. |
| report_instances_download_dataA | [Analytics/Data] Download analytics report data to a TSV file. |
| reviews_listC | [App] List customer reviews for an app. |
| reviews_getC | [App] Get detailed information about a specific customer review. |
| reviews_searchC | [App] Search customer reviews with advanced filtering. |
| crashes_listA | [TestFlight] List crash submissions from beta testers. |
| crashes_searchC | [TestFlight] Search crash submissions with advanced filtering. |
| crashes_get_by_idC | [TestFlight] Get detailed information about a specific crash submission. |
| crashes_get_logB | [TestFlight] Get the raw crash log text for a specific crash submission. |
| users_listA | [Users/Management] List all users in the organization. |
| users_getB | [Users/Management] Get detailed information about a specific user. |
| users_modifyB | [Users/Management] Modify a user account. |
| users_deleteB | [Users/Management] Remove a user account. |
| user_invitations_listA | [Users/Invitations] List all user invitations. |
| user_invitations_getB | [Users/Invitations] Get detailed information about a specific user invitation. |
| user_invitations_createA | [Users/Invitations] Create a new user invitation. |
| user_invitations_deleteA | [Users/Invitations] Cancel/delete a user invitation. |
| products_listC | [XcodeCloud/Products] List all Xcode Cloud products. |
| products_getB | [XcodeCloud/Products] Get detailed information about a specific Xcode Cloud product. |
| workflows_listA | [XcodeCloud/Workflows] List workflows for an Xcode Cloud product. Note: Create/update/delete operations are not supported for safety. |
| workflows_getA | [XcodeCloud/Workflows] Get detailed information about a specific workflow. Note: Create/update/delete operations are not supported for safety. |
| builds_listB | [XcodeCloud/Builds] List builds for a product or workflow. Requires either product_id or workflow_id. |
| builds_getA | [XcodeCloud/Builds] Get detailed information about a specific build. |
| builds_startA | [XcodeCloud/Builds] Start a new build using a branch or tag name. |
| builds_start_by_ref_idA | [XcodeCloud/Builds] Start a new build using a Git reference ID directly. |
| artifacts_listB | [XcodeCloud/BuildArtifacts] List artifacts for a build. |
| issues_listC | [XcodeCloud/BuildArtifacts] List issues for a build. |
| test_results_listB | [XcodeCloud/BuildArtifacts] List test results for a build. |
| scm_providers_listB | [XcodeCloud/SCM] List SCM providers configured for Xcode Cloud. |
| repositories_listB | [XcodeCloud/SCM] List Git repositories for an SCM provider. |
| pull_requests_listB | [XcodeCloud/SCM] List pull requests for a repository. |
| git_references_listB | [XcodeCloud/SCM] List Git references (branches/tags) for a repository. |
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 40 tools
Each tool targets a distinct resource and action within its category. The analytics tools follow a clear hierarchy (requests -> reports -> instances -> segments) that is discernible from descriptions, though the naming could be clearer. No two tools appear to do exactly the same thing.
Most tools follow a resource_action pattern, but analytics tools mix conventions: e.g., 'reports_list_instances' vs 'analytics_report_requests_list' vs 'report_requests_get'. Nested list tools use a different word order than top-level lists, and 'builds_start_by_ref_id' is an outlier. Still, names are generally readable and predictable within categories.
40 tools is well above the 25+ threshold for heavy tool sets. While they cover a broad API, many are simple list/get variations, and an agent would be overwhelmed. Some consolidation (e.g., combining list and search, or using parameters for different resource hierarchies) could reduce the count.
The server covers analytics, reviews, crash reports, user management, and Xcode Cloud, but omits major App Store Connect areas like app metadata, TestFlight builds/beta groups, certificates, devices, and in-app purchases. Within included domains, coverage is fairly thorough, but the overall surface is incomplete for a server claiming to be an App Store Connect MCP.