Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Every App Store Connect + StoreKit 2 endpoint. 929 tools in 13 profiles, narrow to 27.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
ASC_KEY_ID, ASC_ISSUER_ID, ASC_PRIVATE_KEY, ASC_PRIVATE_KEY_PATH, ASC_BUNDLE_IDValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"asc": {
"command": "npx",
"args": [
"-y",
"@erayendes/asc-mcp"
],
"env": {
"ASC_KEY_ID": "your-value",
"ASC_ISSUER_ID": "your-value",
"ASC_PRIVATE_KEY": "your-value",
"ASC_PRIVATE_KEY_PATH": "your-value",
"ASC_BUNDLE_ID": "your-value"
}
}
}
}Run this in your terminal
claude mcp add asc --env ASC_KEY_ID=your-value --env ASC_ISSUER_ID=your-value --env ASC_PRIVATE_KEY=your-value --env ASC_PRIVATE_KEY_PATH=your-value --env ASC_BUNDLE_ID=your-value -- npx -y @erayendes/asc-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"asc": {
"command": "npx",
"args": [
"-y",
"@erayendes/asc-mcp"
],
"env": {
"ASC_KEY_ID": "your-value",
"ASC_ISSUER_ID": "your-value",
"ASC_PRIVATE_KEY": "your-value",
"ASC_PRIVATE_KEY_PATH": "your-value",
"ASC_BUNDLE_ID": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"asc": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@erayendes/asc-mcp"
],
"env": {
"ASC_KEY_ID": "your-value",
"ASC_ISSUER_ID": "your-value",
"ASC_PRIVATE_KEY": "your-value",
"ASC_PRIVATE_KEY_PATH": "your-value",
"ASC_BUNDLE_ID": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
ASC_KEY_ID envASC_ISSUER_ID envASC_PRIVATE_KEY_PATH envASC_BUNDLE_ID envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account erayendes, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: ASC_PRIVATE_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (2.8.0) reached the registry 12 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Aiterm MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Persistent terminals and one launcher for Claude, Codex, Grok, Cursor, and Antigravity harnesses.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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, 33 sub-profiles, 929 tools.
Apple's specification lists 1011 API operations. Heimdall leaves out the 123 that Apple has deprecated, so 888 become tools, and adds 41 hand-written ones: 929 tools in all.
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.
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.
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.
Heimdall doesn't replace Fastlane; it complements it. Fastlane for the pipeline, Heimdall for everything you'd otherwise do by hand.
One command:
npx -y @erayendes/asc-mcp setup
It asks whether to continue in your browser (recommended) or the terminal. You'll need an App Store Connect API key; the browser page tells you which role to give it from what you pick, so you can run setup before creating the key. Node.js 20.19 or later.
Want your AI to install it for you, or to use it in Xcode 27? Everything else is in Setup.
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.
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.