The complete Model Context Protocol (MCP) server for Apple's App Store Connect API.1316 tools. 100% coverage of every non-deprecated operation in Apple's official OpenAPI spec — TestFlight, Xcode Cloud, Game Center, App Clips, in-app purchases, subscriptions, review submissions, analytics, provisioning, and everything else Apple exposes. Works with Claude, Cursor, VS Code Copilot, Codex CLI, Gemini CLI, Windsurf, or any MCP client.
Complete Model Context Protocol (MCP) server for Apple's App Store Connect API — 1316 tools, 100% coverage. TestFlight, Xcode Cloud, Game Center, App Clips, in-app purchases, subscriptions, analytics, review submissions, provisioning. Works with Claude, C
App Store Connect is huge. Apple's own OpenAPI spec currently lists 1303 operations across 203 resource groups — TestFlight, Xcode Cloud, Game Center, App Clips, in-app purchases, subscriptions, offer codes, review submissions, alternative distribution (EU DMA), analytics, metrics, privacy manifests, provisioning, users… the list goes on.
Every community MCP covers a slice. None covers everything.
Often still on the legacy appStoreVersionSubmissions
Alternative distribution (EU DMA)
✅
❌
App data usages (privacy)
✅
❌
Multi-account (switch between dev accounts)
✅ local registry + per-project ASC_ACCOUNT pin
Usually one
Credential safety
No .p8 content in repo, no keys in the process cache, strict .gitignore
Varies
Spec-driven — auto-regenerate on new spec
✅ npm run codegen
❌
If you drive App Store Connect with an AI assistant — submission automation, TestFlight management, IAP / subscription catalog, review triage, analytics, or Xcode Cloud orchestration — this gives the assistant the full toolbox in one install.
Feature matrix
1316 tools total (as of spec v4.5.1):
6accounts_* — local multi-account registry (add / list / switch / remove / update / current)
2auth_* — auth_status (readiness) and auth_revoke_cache
1303 auto-generated from the official App Store Connect OpenAPI spec, one per operation, covering every resource group:
Apps / App Infos / App Store Versions / App Store Version Localizations / Phased Releases / Version Submissions
Review Submissions (v2) + Review Submission Items + App Store Review Attachments + App Store Review Details
Xcode Cloud: Ci Products, Ci Workflows, Ci Build Runs, Ci Build Actions, Ci Artifacts, Ci Issues, Ci Test Results, Ci Xcode Versions, Ci Mac Os Versions, Ci Scm Repositories / References / Pull Requests / Providers
Game Center: Achievements, Leaderboards, Leaderboard Sets, Groups, Matchmaking Queues / Rule Sets / Rules / Teams, Activities, Player Scores / Achievements, App Versions, Enabled Versions, Details, Vocabularies, plus all Localizations / Images / Releases
Provisioning: Bundle Ids, Bundle Id Capabilities, Certificates, Devices, Profiles, Pass Type Ids
Users & Access: Users, User Invitations, Actors, Sandbox Testers
Encryption / Compliance: App Encryption Declarations + Documents, Age Rating Declarations, App Data Usages + Categories + Purposes + Data Protections + Publish State, Accessibility Declarations, End User License Agreements
Alternative Distribution (EU DMA): Alternative Distribution Keys, Domains, Packages, Package Versions / Variants / Deltas, Marketplace Search Details, Marketplace Webhooks
Spec 4.5 additions: App Asset Libraries (images, videos, placements), In-App Purchase / Subscription / Subscription Group Versions with V2 localizations and images, Subscription Plan Availabilities, Game Center Score Moderations and Blocked Players, App Performance Overviews
5 hand-written helpers for flows that don't map cleanly to a single operation:
asset_upload_file — step 2 of the 3-step asset upload protocol (screenshots, previews, review attachments, IAP review screenshots, App Clip header images, Game Center images, routing app coverages)
sales_reports_download — downloads and un-gzips sales reports, returns parsed TSV
finance_reports_download — same for finance reports
analytics_report_instance_wait — poll until a report is COMPLETED/FAILED
ci_build_run_wait — poll an Xcode Cloud build run to completion
Run auth_status, then apps_get_collection to verify end-to-end.
Quick start
Install from npm:
npm install -g apple-app-store-connect-mcp
Or run without installing:
npx -y apple-app-store-connect-mcp
About the package name. The package on npm is apple-app-store-connect-mcp. After install, the command on your $PATH is app-store-connect-mcp (the bin name) — that's what your MCP client config below points at.
Then add to your MCP client config (example, Claude Code):
Users and Access → Integrations → App Store Connect API.
Click Generate API Key (requires Account Holder or Admin role).
Name it, choose the access level you want (Admin, Developer, Finance, Marketing, etc.), and Generate.
Copy the Key ID and Issuer ID (displayed at the top of the page).
Click Download API Key. This gives you an AuthKey_<KEYID>.p8 file. You only get this download once. Store it outside any git repo, for example at ~/.config/app-store-connect-mcp/AuthKey_AB12CD34EF.p8 with chmod 600.
2. Register the key with this MCP server
Launch any MCP client that has the server configured, then call:
All subsequent calls target the currently-switched account.
5. Pinning one account per project (ASC_ACCOUNT)
currentAccount is a single global value in accounts.json, shared by every MCP client on
the machine. If you work on more than one App Store Connect account, that is a footgun: an
accounts_switch in one project silently retargets every other project, and an assistant in
project A can end up writing to account B's apps.
Pin the account per server process instead. Set ASC_ACCOUNT in the MCP client config:
If you work on more than one App Store Connect account, put the server in each project's
.mcp.json instead and pin it — see Pinning one account per project:
Any MCP-compliant client accepts the same command entry — point it at the globally installed app-store-connect-mcp binary, or at node /path/to/dist/index.js when running from source.
Running from source (no global install)
git clone https://github.com/devinwang/app-store-connect-mcp.git
cd app-store-connect-mcp
npm install
npm run build
customer_reviews_get_collection
"filter[app]": <APP_ID>
"sort": "-createdDate"
"limit": 10
customer_review_responses_v1_create_instance
body:
data:
type: customerReviewResponses
attributes:
responseBody: "Thanks for the feedback — we fixed this crash in 1.2.1. Please give it another try!"
relationships:
review:
data: { type: customerReviews, id: <REVIEW_ID> }
This server replaces github.com/zelentsov-dev/asc-mcp. Key differences:
Scope. That server implements ~90 tools; this one implements all 1303 spec operations plus helpers.
Tool names.zelentsov-dev/asc-mcp uses simplified names like apps_search, reviews_list, app_versions_submit_for_review. This server uses Apple's official operationId snake-cased — apps_get_collection, customer_reviews_get_collection, review_submissions_create_instance. There's no auto-translation: update any prompts or scripts that assumed the old names.
Credential compat. The same env vars (ASC_KEY_ID, ASC_ISSUER_ID, ASC_PRIVATE_KEY_PATH) still work, so you don't need to move the .p8 to migrate. You'll get a one-time stderr warning recommending you register via accounts_add for multi-account support.
company_* → accounts_*. Rename mental model: a "company" in the old server is an "account" here.
A comprehensive name-by-name mapping is included in docs/MIGRATION.md.
Security
This repo ships with zero credentials. You bring an App Store Connect API .p8; the server records only its path.
What is and isn't on disk
Where
What
~/.app-store-connect-mcp/accounts.json
Account names, key ids, issuer ids, key-file paths, descriptions. No secrets. Written with 0600 permissions, directory 0700.
Wherever you placed your AuthKey_*.p8
The actual private key. Never committed. Never copied into the server's memory longer than one JWT signing.
Repo contents
Code only. No fixtures, no example keys, no real key ids.
What's in memory
When
What
At JWT sign time
The .p8 content is readFileSync'd, passed to jwt.sign, and the buffer is fill(0)-ed and dereferenced immediately after.
Between calls
A signed JWT (20-minute lifetime) is cached in a local variable in token-cache.ts. This is in-memory only — it is never persisted to disk. Dropped on accounts_switch, accounts_update, accounts_remove, and auth_revoke_cache.
In tool outputs
Everything is passed through redact() before emission. JWT-like strings, PEM blocks, Bearer tokens, and long hex tokens get replaced with [REDACTED …] — defense-in-depth against any code path accidentally logging.
.gitignore blocks
*.p8, AuthKey_*, AuthKey_*.p8
*.pem, *.p12, *.pfx, *.key, id_rsa*
accounts.json, .app-store-connect-mcp/
credentials/, keys/, secrets/
.env, .env.* (keeps .env.example)
Recommended hygiene
Keep your .p8 outside any git repo on your machine.
Grant the API key the narrowest role your workflow needs. Admin lets this MCP do anything including deleting store metadata. Restrict as appropriate.
Rotate the key periodically: revoke the old key in App Store Connect → Users and Access → Integrations, generate a new one, run accounts_update --keyFile <newPath>.
auth_status returns only the key id, issuer id, a boolean, and the JWT expiry timestamp. It never returns the JWT or the .p8 content.
The CI workflow in this repo fails the build if any private-key-material regex is detected in dist/.
Audit trail
Apple logs every API call against your key id. If you ever suspect misuse, open App Store Connect → Users and Access → Integrations and revoke the key; any outstanding JWTs signed with it stop working immediately.
Design notes
Spec-driven. 1303 of the 1316 tools are auto-generated from Apple's official OpenAPI spec (spec/app-store-connect-openapi.json). When Apple ships a new version, npm run spec:download && npm run codegen && npm run build is all it takes to update.
1:1 operationId naming. Tool names are Apple's operationId values converted to snake_case. This means the MCP names match the official REST reference, so when an LLM reads Apple's docs it can pick the right tool without translation.
Pragmatic input validation. Path params are typed zod strings (required), query params are typed zod fields (optional) with the exact bracketed names Apple uses (filter[name], fields[apps], limit[appStoreVersions]). Request bodies are z.record(z.unknown()) with a description pointing at the OpenAPI component schema — ASC validates them server-side and our error translator surfaces mistakes clearly. Generating full zod trees for every JSON:API envelope would balloon the server by 10× and add negligible value.
Error translation.401 becomes "JWT rejected — rotate or check clock skew", 403 becomes "key isn't authorized for this endpoint", 422 surfaces the exact source.pointer from the ASC response, 429 explains the per-team quota, 5xx points at https://developer.apple.com/system-status/.
Stateless transport. stdio only. No network listener, no persistent state beyond the accounts file.
Zero telemetry. The server never phones home.
Contributing
PRs welcome. Before you submit:
npm run typecheck + npm run build pass on Node 18 / 20 / 22 (CI also runs this).
Never include a real .p8, a real keyId, a real issuerId, or a real JWT in an issue, PR, fixture, or example.
When you update to a new OpenAPI spec version:
npm run spec:download
npm run codegen — regenerates src/tools/generated/ and spec/coverage-report.txt
npm run build
Skim spec/coverage-report.txt diff — a delta of 10+ tools or a new top-level tag should get a CHANGELOG note.
New hand-written tools live in src/tools/overrides.ts and must have names that don't collide with any generated name.
Complete Model Context Protocol (MCP) server for Apple's App Store Connect API — 1316 tools, 100% coverage. TestFlight, Xcode Cloud, Game Center, App Clips, in-app purchases, subscriptions, analytics,
Complete Model Context Protocol (MCP) server for Apple's App Store Connect API — 1316 tools, 100% coverage. TestFlight, Xcode Cloud, Game Center, App Clips, in-app purchases, subscriptions, analytics, review submissions, provisioning. Works with Claude, C
टूल
टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
सवाल
Apple App Store Connect कैसे इंस्टॉल करें?
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
क्या Apple App Store Connect के लिए API key चाहिए?
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Apple App Store Connect कौन सा ट्रांसपोर्ट इस्तेमाल करता है?
Apple App Store Connect stdio पर लोकल चलता है।
Apple App Store Connect की पिछली जाँच कब हुई थी?
पिछली जाँच 2026-10-28 को हुई। Complete Model Context Protocol (MCP) server for Apple's App Store Connect API — 1316 tools, 100% coverage. TestFlight, Xcode Cloud, Game Center, App Clips, in-app purchases, subscriptions, analytics, review submissions, provisioning. Works with Claude, C