Heimdall App Store Connect MCP
Heimdall gives an agent the whole App Store Connect and Server APIs: releases, subscriptions, reviews, TestFlight, 786 tools
- 57 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The API key opens prices, subscriptions, user access, code signing and version releases of your account
- The `.p8` private key is stored in client configurations or in a file on disk
Install
- Works in
Manual install
npx -y @erayendes/asc-mcp setupThe wizard saves the key and registers the chosen profiles.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The API key opens prices, subscriptions, user access, code signing and version releases of your account
- The `.p8` private key is stored in client configurations or in a file on disk
This is third-party code. Review the repository files before installing.
What it does
Heimdall is an MCP server built from Apple's OpenAPI specification. It covers the App Store Connect API and the App Store Server API (StoreKit 2): releases, TestFlight, subscriptions and in-app purchases, the store page and reviews, Game Center, Xcode Cloud, provisioning, webhooks and sales. In total there are 786 tools in 14 profiles and 51 sub-profiles. Tools are split by kind of work and each profile runs as its own small server. The ASC-Core profile with app and tool search and media operations is always attached. Before changing a price, granting Admin access or deleting, Heimdall shows what will change and asks for confirmation, and irreversible steps require typing the word CONFIRM. Setup runs with `npx -y @erayendes/asc-mcp setup`.
Who it is for. iOS developers and studios who run releases, subscriptions and the store page from an agent and want full Apple API coverage.
Good fit when
- Summarize this week's one-star review complaints and prepare replies
- Learn which builds are stuck in review
- Raise a subscription price in every country at once
- Add build 42 to the internal and external TestFlight groups
Not a fit when
- A small set of a couple of tools with no profiles is enough
- The API key must not be issued with broad permissions
- The app is not in an Apple Developer account
Example request
Is there a tool for in-app events for my app? Show builds stuck in review and raise the subscription price in every countryMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
ASC_KEY_IDrequired, secret- App Store Connect API key ID
ASC_ISSUER_IDrequired, secret- Key issuer ID
ASC_PRIVATE_KEYsecret- Private `.p8` key as a string
ASC_PRIVATE_KEY_PATH- Path to the private key file
Limitations
An App Store Connect API key is required: the key ID `ASC_KEY_ID`, the issuer `ASC_ISSUER_ID` and the private key in `ASC_PRIVATE_KEY` or a path in `ASC_PRIVATE_KEY_PATH`. A key with a broad role opens prices, user access, code signing and version releases, so give the minimal role and pick only the profiles you need, which also saves model context. Since 3.0 the set of profiles changed, and after updating from 2.x setup must be run again. Confirmations appear in a dialog on Mac or by typing the word CONFIRM.
How to disable. Remove the registered profiles from the client configurations and revoke the API key in App Store Connect. To stay on 2.x use the version `@erayendes/asc-mcp@2.8.0`.
FAQ
How do I install Heimdall?
Run `npx -y @erayendes/asc-mcp setup`. The wizard saves your key and registers the chosen profiles in every AI app it finds.
What are profiles?
Groups of tools by kind of work: releases, TestFlight, subscriptions, the store page, Game Center, Xcode Cloud and others. Each runs as its own server and ASC-Core is attached to all.
How are dangerous actions guarded?
Before a price change, access grant or deletion Heimdall shows the consequences and asks for confirmation. Irreversible steps such as releasing a version require typing CONFIRM.
How many tools does the build have?
786 tools in 14 profiles and 51 sub-profiles. Of the 1036 operations in Apple's specification, deprecated and duplicate ones are left out.
How is it different from other App Store Connect servers?
Many give a hand-picked slice of the API, while Heimdall covers all of it, cut by kind of work to avoid overloading the model context.
Discussion
No questions or reviews yet.
Related
MCP serversApp Store Connect MCP
appstoreconnect-mcp
An MCP server for App Store Connect: subscription prices by country, offers, review submission and sales reports straight from an agent chat
App Store Connect MCP reads TestFlight builds, reviews and sales and updates app metadata through the Apple API
The asc CLI manages builds, TestFlight and App Store Connect releases, returning results as tables or structured JSON.
The Itsyconnect MCP server edits App Store Connect listings, translates fields and adds locales from your coding agent.
A Swift CLI for App Store Connect: builds, TestFlight, metadata, subscriptions and review submission with ready commands in JSON
Skills for driving App Store Connect through the asc CLI: builds, TestFlight, analytics, ads and crash triage
README in short
The README opens with the 3.0 announcement and its changes: profiles by kind of work, four media tools, one call to submit for review and clear confirmations. The scope of the API, action safeguards, installation and a profile table follow.