App Store Connect MCP
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_KEY_PATH | Yes | Absolute path to your App Store Connect API private key (.p8) file | |
| ASC_ISSUER_ID | Yes | Your App Store Connect Issuer ID |
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 |
|---|---|
| list_appsA | List every app visible to this API key: id, bundle id, name, sku. |
| get_appA | Fetch one app's full attributes by its App Store Connect app id. |
| find_app_by_bundle_idA | Look up an app by its bundle identifier (e.g. com.example.app). Returns None if it doesn't exist yet. |
| list_bundle_idsA | List registered Bundle IDs and whether each is used for an app. |
| list_certificatesA | List signing certificates on the account (type, name, expiry). |
| list_profilesA | List provisioning profiles on the account. |
| list_buildsC | List TestFlight builds for an app: version, build number, processing state. |
| list_beta_groupsB | List TestFlight beta groups (internal/external) for an app. |
| list_beta_testersB | List testers in a TestFlight beta group. |
| list_app_store_versionsB | List App Store versions for an app: version string, platform, state. |
| get_app_store_versionA | Fetch one App Store version's full attributes, including appStoreState. |
| create_app_store_versionB | Create a new App Store version on an EXISTING app record (does not create the app itself). |
| attach_build_to_versionA | Attach a processed TestFlight build to an App Store version, ready for submission. |
| submit_for_reviewA | Submit an App Store version for Apple review. |
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 14 tools
Each tool targets a distinct resource and action: apps (list/get/find), versions (create/list/get/attach/submit), TestFlight builds/beta groups/testers (list only), and account resources (bundle IDs, certificates, profiles). Even though list_apps, get_app, and find_app_by_bundle_id all retrieve app info, their input methods differ clearly, preventing misselection.
All tool names follow the same verb_noun pattern in snake_case (create_, list_, get_, find_, attach_, submit_). The only minor deviation is 'find_app_by_bundle_id' which uses 'find' instead of 'get', but it remains consistent in structure and readability.
14 tools is well-scoped for an App Store Connect server covering app management, TestFlight builds, version lifecycle, and submission. Each tool addresses a specific workflow step without unnecessary overlap, making the count appropriate for the domain.
The server covers the core workflow of listing apps, fetching versions, attaching builds, and submitting for review, but lacks critical CRUD operations: there is no create/update/delete for apps, no ability to manage beta testers beyond listing, and no way to create or edit beta groups. These gaps would require agent workarounds or external calls.