Asc Mcp
Every App Store Connect + StoreKit 2 endpoint. 890 tools in 13 profiles, narrow to 27.
- Transport
- Not stated
- Package
- —
- Registry id
- io.github.erayendes/asc-mcp
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
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 question | Through the raw tools | Heimdall |
|---|---|---|
| "What does this subscription cost in every country?" | one measured agent session: 1.02M tokens, $3 | ~1.3k tokens, 2.1s |
| "What screenshots are on the listing?" | 53 HTTP calls, 264 KB | 4 calls, ~1 KB |
| "Change this subscription's price." | 4 reads, then a choice among 842 price points | one call |
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.
Xcode 27 is not on that list because Xcode has no config file to write — it installs plug-ins from a Git URL. After setup, open Xcode → Settings → Intelligence → Plug-ins → Add Plug-in → Add from URL, paste https://github.com/erayendes/app-store-connect-mcp, and tick Heimdall | ASC Skill plus the areas you need. Then pick an agent in the conversation's model menu — Claude Agent, Codex or Gemini — rather than a built-in model: plug-ins reach the agents, not Xcode's own chat. The agent launches the same servers, and they read the key setup stored.
Is an AI agent installing Heimdall for you? See AGENTS.md for the handoff protocol: the agent adds the profiles with
register, you runsetupyourself 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.
From the project's README.