asc-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 (required) | |
| ASC_ISSUER_ID | No | Only for team keys | |
| ASC_PRIVATE_KEY | No | Where the private key lives: `keychain` (default), a 1Password `op://` reference, or a file path outside this repo with `chmod 600` | keychain |
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_appsA | Read-only. Lists the apps in App Store Connect that your API key can see, with bundle IDs and Apple IDs. Optionally filter by part of the name or bundle ID. |
| get_appA | Read-only. Shows one app's details (bundle ID, Apple ID, SKU, primary locale) and its latest App Store version and state per platform. |
| list_buildsA | Read-only. Lists an app's uploaded builds, newest first, with version, build number, platform, processing status (processing / ready / failed / invalid), upload time and expiry. Use status "processing" to see builds still being processed by Apple. |
| list_beta_groupsA | Read-only. Lists an app's TestFlight beta groups, showing whether each is internal or external and whether its public link is on. |
| list_beta_testersA | Read-only. Lists TestFlight testers for an app (or for one of its beta groups), with name, email, status (invited / accepted / installed …) and how they were invited. |
| list_app_store_versionsA | Read-only. Lists an app's App Store versions, newest first, with platform, state (e.g. prepare for submission, waiting for review, in review, ready for distribution, rejected) and release type. |
| list_customer_reviewsA | Read-only. Lists an app's App Store customer reviews, newest first, with star rating, title, text (trimmed), country and date. Optionally filter by star rating or territory. |
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 7 tools
Each tool targets a distinct App Store Connect resource: apps, builds, beta groups, beta testers, App Store versions and customer reviews. The only near-overlap is get_app vs list_apps, but the singular/plural split and the 'details with latest version state' framing make the boundary clear. Descriptions also spell out optional filters (status, star rating, territory) so parameter choice is unambiguous.
A strict verb_noun pattern holds throughout: get_app plus six list_* tools. Pluralization is used correctly for collections (list_apps, list_builds, list_beta_groups) and singular for the single-resource get. No style mixing.
Seven read-only tools is well-scoped for a focused App Store Connect inspection server, covering apps, builds, TestFlight and reviews without padding. Each tool maps to a distinct listing need; nothing feels redundant or missing at the count level.
The surface is entirely read-only, so there is no lifecycle coverage (no create/update beta group, invite testers, submit/release a version, or respond to reviews), and there is no single-build or single-version detail fetch analogous to get_app. For pure read/inspect workflows the listed resources are reasonably covered, but an agent trying to act on App Store Connect will hit multiple dead ends.