Heimdall

Heimdall — App Store Connect MCP

Your whole App Store Connect account, in one tool.

🇬🇧 English · 🇹🇷 Türkçe

Ask, and it answers. Tell it, and it's done.

• "Summarize this week's 1-star reviews and draft replies."
• "Which builds are stuck in review?"
• "Raise this subscription's price in every country."
• "What does this subscription cost in each country?"
• "Which screenshots are on the store listing?"
• "Add build 42 to the Internal and External groups."
• "Why did my Xcode Cloud build fail?"

Almost anything you'd click through App Store Connect to do, you can now just ask your AI to do. More examples in the Guide.

_{A real AI session, sped up. The App Store Connect account is a stand-in so the recording can be public.}

Heimdall

One MCP server for the App Store Connect API and the App Store Server API (StoreKit 2), built from Apple's own OpenAPI specification. 13 profiles, 32 sub-profiles, 902 tools.

Most App Store Connect MCP servers give you a hand-picked slice of the API. That works until you need the one endpoint they left out, and then you're off hunting for yet another tool.

Heimdall does the opposite: it gives you the whole API, organized into profiles. Apps and metadata, versions, TestFlight, subscriptions and in-app purchases, pricing, reviews, Game Center, Xcode Cloud, provisioning, webhooks, sales and finance reports — all of it. You pick what you need, and add or remove profiles whenever you like.

Profiles shows what each one covers. You don't have to memorize any of it, though: ask "Is there a tool for in-app events?" and Heimdall tells you which profile has it.

Not sure which profiles you need? The starter packs suggest a set for your role.

Runs on your machine

Most MCP guides recommend remote HTTP servers. Heimdall runs locally instead. It reads your App Store Connect key from the Keychain, signs a short-lived token and talks to Apple directly. Nothing sits in between, so your key stays with you.

Note

Give your key the narrowest role that does the job. Roles explains what each App Store Connect role can do.

Asks before risky changes

Before changing a price, giving someone Admin access or deleting something, Heimdall asks you to confirm and shows what will change. This is on by default for changes that are hard to undo: revenue, deletions, infrastructure and access, and for the release steps that reach users: sending a version to review, releasing it, changing a phased rollout, and opening a build to external testers. Everything else goes through your app's own approval.

More in Security.

Works alongside Fastlane

Heimdall doesn't replace Fastlane; it complements it. Fastlane for the pipeline, Heimdall for everything you'd otherwise do by hand.

Setup

One command:

npx -y @erayendes/asc-mcp setup

Before you run it, create an API key in App Store Connect and make sure Node.js 20.19 or later is installed.

Want your AI to install it for you, or to use it in Xcode 27? Everything else is in Setup.

About the name and the project

In Norse mythology, Heimdall keeps watch over Bifröst, the rainbow bridge that links Asgard to the nine realms. Here, his job is to guard the road between your App Store Connect account and your machine. That's where the name comes from.

I build Heimdall on my own, in the evenings, and release it free and open source under the MIT license. If it gets you out of the App Store Connect dashboard, it has done its job.

License

MIT © Eray Endes

SECURITY.md | SUPPORT.md | CHANGELOG.md | CONTRIBUTING.md | CODE_OF_CONDUCT.md | GOVERNANCE.md

Heimdall is generated from the App Store Connect OpenAPI specification published by Apple Inc. App Store Connect, TestFlight, StoreKit, Xcode and Game Center are trademarks of Apple Inc. This project is not affiliated with Apple Inc.