App Store Connect MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASC_KEY_ID | Yes | Your App Store Connect API Key ID | |
| ASC_ISSUER_ID | Yes | Your App Store Connect Issuer ID | |
| ASC_PRIVATE_KEY_PATH | Yes | Path to your 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_appsB | List all apps in your App Store Connect account |
| get_appA | Get detailed information about a specific app |
| list_buildsA | List builds for an app. Filter by processing state or version. |
| get_buildB | Get detailed information about a specific build |
| list_app_versionsB | List all App Store versions for an app |
| get_app_versionB | Get detailed information about a specific app version |
| submit_for_reviewA | Submit an app store version for App Review. The version must be in READY_FOR_REVIEW state. |
| list_beta_groupsA | List TestFlight beta groups for an app |
| list_beta_testersA | List beta testers, optionally filtered by beta group |
| add_beta_testerB | Add a beta tester to a beta group by email |
| list_usersA | List all users (team members) and their roles in App Store Connect |
| list_devicesA | List registered devices in your developer account |
| list_bundle_idsC | List registered bundle identifiers |
| list_customer_reviewsB | List customer reviews for an app |
| respond_to_reviewB | Respond to a customer review |
| list_certificatesB | List signing certificates in your developer account |
| list_profilesB | List provisioning profiles |
| list_in_app_purchasesC | List in-app purchases for an app |
| list_subscriptionsB | List subscription groups for an app |
| get_sales_reportC | Request a sales or financial report. Returns report data as text. |
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 20 tools
Each tool targets a distinct resource and action: apps, builds, versions, beta groups/testers, reviews, users, devices, bundle IDs, certificates, profiles, IAP, subscriptions, and sales. The few related tools (list vs get, list_customer_reviews vs respond_to_review) are clearly differentiated by their verbs and object nouns.
All tool names follow a consistent verb_noun or verb_preposition_noun pattern (e.g., list_apps, get_build, submit_for_review, respond_to_review). Naming is uniformly lowercase with underscores, making the pattern predictable across all 20 tools.
With 20 tools, the set is on the heavier side but still coherent for the broad App Store Connect domain. The count is justified by the many distinct resource types covered, though it approaches the upper limit of what feels manageable.
The tool set is read-heavy, covering listing and getting for most resources, plus a few actions like responding to reviews, submitting for review, and adding beta testers. However, it lacks update/delete operations for apps, builds, versions, users, and other entities, leaving notable gaps in lifecycle management.