Heimdall — App Store Connect MCP

_{A real agent session over MCP, sped up. The App Store Connect account is a stand-in so the recording can be public — regenerate with vhs assets/demo/demo.tape.}

🇬🇧 English · 🇹🇷 Türkçe

English

Heimdall. One tool for your entire App Store Connect account.

An MCP server for the App Store Connect API and the App Store Server API (StoreKit 2), with every tool generated from Apple's own OpenAPI specification. 13 profiles, 32 sub-profiles, 890 tools.

Apps and metadata, versions and phased releases, TestFlight, subscriptions and in-app purchases, pricing, reviews, Game Center, Xcode Cloud, provisioning, webhooks, and sales and finance reports.

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

• "Summarise this week's 1-star reviews and draft replies."
• "Which builds are stuck in review?"
• "Raise this subscription's price in every territory."

What the one call saves

The first row is a real session, not a projection: the agent walked the chain, could not fit the answer, wrote it to a CSV and hand-built a country-name dictionary in Python to finish. The other two are call counts against a live account.

Quick start

npx -y @erayendes/asc-mcp setup

_{One pass, and safe throughout: the access details it needs, then a live credential check. Then your choices — the profiles and sub-profiles you want, and the key ends up in the Keychain, not in a config file.}

The setup wizard asks for your API key once, stores it safely, and registers the profiles you choose with every MCP client on your machine — Claude, Codex, Antigravity, Cursor, Windsurf, VS Code. None of them share a config file, so this is the step you would otherwise repeat once per client, in a different format each time. Time thrown away. Full walkthrough in the Guide.

Is an AI agent installing Heimdall for you? See AGENTS.md for the handoff protocol: the agent adds the profiles with register, you run setup yourself for the key — your private key is for your eyes only, and the agent never sees it.

What sets Heimdall apart

Most App Store Connect MCP servers offer a hand-picked slice of the API. That works right up until you need the one endpoint none of them covered. Heimdall does the opposite: it gives you all of the tools and lets you choose which ones you want — and change your mind whenever you like.

Profiles

Register only the profiles your project uses. What each one covers is in the profile table; adding and removing them later is here.

Not sure which? Starter packs answers it by role — a release manager installs distribution + app-info, an ASO team marketing + analytics — and examples/ works each one through, including the part that usually goes wrong.

There is nothing to memorise — ask "is there a tool for in-app events?" and asc__search_tools searches everything, including what isn't loaded, and tells you which profile it lives in.

Risky writes ask first

Changing a price, handing out Admin or deleting something asks for confirmation before it runs, showing what would change, so a misread instruction cannot execute unchecked. This is the default for the four risk levels that are hard to undo — revenue, destructive, infrastructure, access — and everything else runs on your client's own tool approval. --confirm asks before every write instead; --no-confirm asks before none; --read-only drops mutating tools entirely. See Security.

Least privilege, and a way to check it

Apple never returns a key's role from any endpoint, so App Manager — not Admin — is the right default for day-to-day release work; Admin only earns its place for user management and for the one-time first request of a new analytics report type, which has no path in the App Store Connect UI at all. Contracts, tax and banking sit behind the Account Holder alone, reachable by no API key regardless of role. Call asc__status with check_capabilities: true to see what a key actually has rather than guessing from a 403 mid-task. Full breakdown in the Guide.

Local by design, not by default

MCP guidance recommends remote HTTP servers: one URL, no install, updates you control. Heimdall runs locally over stdio instead, and that is a deliberate trade. Running locally, the key never leaves your machine: Heimdall reads it from the Keychain, signs a short-lived token, and talks to Apple directly. Nothing sits in between.

The cost is real and worth naming: you need Node installed, and you update by version rather than by us pushing one. That is the price of the key staying yours.

Works alongside Fastlane

Heimdall is not a Fastlane alternative — it is the interactive half. Keep Fastlane for repeatable, scripted CI work (code signing, build upload, metadata pushes). Fastlane for the pipeline, Heimdall for exploration and one-off changes.

Documentation

• Guide — API key, install, setup wizard, profiles, configuration, examples
• Examples — starter packs by role, seven worked scenarios, and a GitHub Actions workflow
• Security — credential handling, safety modes, pre-install audit, vulnerability reporting
• Support — getting help, troubleshooting
• Changelog — release history
• Contributing — how to contribute, local dev setup
• Code of Conduct
• Governance — who maintains this and why

Support the project

Heimdall is free and open. If it saves you time, you can become a member or buy me a coffee ☕.

About the name

Heimdall is the guardian of Asgard in Norse mythology and one of Odin's sons. He keeps watch over Bifröst, the rainbow bridge linking Asgard to the nine realms. His gift for sensing events before they happen lets him guard Asgard against giants and other enemies, and warn the gods of danger on its way.

This project stands watch over your App Store Connect account; that's where it gets its name. :)

License

MIT — see LICENSE.