Asc MCP

asc-mcp

Ship an App Store release from your coding agent. An MCP server for App Store Connect: 41 tools that edit version metadata, upload screenshots, attach builds, drive TestFlight, create in-app purchases, submit and release, plus an intelligence layer that audits a version before you submit and summarizes your reviews. 6 slash-command workflows and a bundled Claude Skill. Not another API wrapper.

asc-mcp.pages.dev · npm · Pricing: 7-day free trial, then $9/month, VAT included (sales tax added in the US, Canada and India)

In plain words

You made a toy and you want it in a giant toy store, the App Store. The store has a strict office. Before your toy reaches the shelf, you fill out lots of forms, add pictures, set a price, and wait for a helper to check it all. Forget one thing and they say "no, try again", and days are gone.

asc-mcp is a helper robot for that office. It talks to your AI assistant, so you just say what you want:

• "How is my toy doing?" It tells you whether the store said yes or no, and with Pro, what people wrote about your toy.
• "Is my toy ready?" It checks your forms first, like a teacher reading your homework before you hand it in: "You forgot a picture, and this link is broken."
• "Fix it for me." It fills in forms, adds pictures and sets prices. Before a big move, like changing a price or handing your toy to the store, it stops and asks: are you sure?

Checking whether the store said yes or no is free, with no time limit. Everything else works free for 7 days, no card, then it's $9 a month, VAT included, with sales tax added in the US, Canada and India. The robot checks your homework, and the store still decides.

For the grown-ups: the toy is your app, the office is App Store Connect, and the robot is an MCP server running on your own computer.

Claude Desktop, one click: download the latest asc-mcp.mcpb and open it. Claude asks for your Issuer ID and lets you pick your .p8 with a file picker. No JSON, no restart hunt.

Everything else (Claude Code, Cursor, Windsurf, Cline), one command:

npx @pofky/asc-mcp init --write   # finds your .p8, asks for your Issuer ID, writes your MCP config

Then ask your agent: "start my asc-mcp trial, my email is you@example.com". All 41 tools unlock for 7 days, no card and nothing to cancel, and the trial activates in the session you are already in, so whatever you were blocked on works on the very next call. After that Pro is $9 a month (VAT included; in the US, Canada and India sales tax is added at checkout). Six tools stay free, and two of those (the setup check and the playbook) need nothing but Node. The Pro tools that only read (reviews, sales, builds, TestFlight groups, preflight, briefing, keywords, competitors, metadata diff, release notes) also work 5 times in total on your machine with no license, as a preview.

No context switching. No portal. Just ask.

What Makes This Different

Maintained successor to JoshuaRileyDev/app-store-connect-mcp-server (archived Feb 2026). Different angle, same API surface plus more.

Other ASC MCP servers wrap the API and give you 80 to 982 raw endpoints. This one gives you 41 opinionated tools, 6 slash-command Prompts, and a Claude Skill that all think. The read tools summarize and audit; the Pro control tools actually drive App Store Connect, from editing metadata to submitting and releasing, with the same API key. Two tools use MCP Sampling: your own client's model does the LLM work, so there is no extra cost from this server.

Why full control is possible without fastlane: fastlane's deliver and pilot are just calls to the same App Store Connect REST API this server authenticates against with your .p8. So nearly everything you would script with fastlane is a tool here, no Ruby toolchain required. The only step that needs your Mac is building and signing the binary, which build_and_archive and upload_binary drive via Xcode.

Setup (about 5 minutes)

You need: an Apple Developer account, Node 18 or newer, and an AI coding app that supports MCP (Claude Code, Claude Desktop, Cursor, Windsurf, Cline or any other MCP client). MCP is the standard way these apps plug in extra tools; asc-mcp is one of those tools, and it runs on your own computer.

Step 1. Create an App Store Connect API key. Open App Store Connect > Integrations > App Store Connect API and generate a key with the Admin or App Manager role. From that same page you need two things:

• The `.p8` file. Click Download. Apple lets you download it only once, so keep it safe. Its name, AuthKey_XXXXXXXXXX.p8, contains the Key ID.
• The Issuer ID. The UUID shown at the top of the page, with a copy button next to it.

Move the key into Apple's standard folder, where asc-mcp finds it on its own:

mkdir -p ~/.appstoreconnect/private_keys

mv ~/Downloads/AuthKey_*.p8 ~/.appstoreconnect/private_keys/

Step 2. Run init.

npx @pofky/asc-mcp init --write

It finds the key, asks for your Issuer ID, backs up your Claude Desktop / Claude Code config and adds the server to it, so there is no JSON to edit. Leave out --write to print the block and paste it yourself.

Step 3. Restart your agent and check. Ask it: "run asc_setup_check". It checks the key, the Issuer ID, a live connection to App Store Connect and your license, and prints the exact fix for anything wrong. The same check from a terminal is npx @pofky/asc-mcp doctor. Then ask: "List my App Store Connect apps".

Step 4. Start the trial. Ask your agent: "start my asc-mcp trial" and give it your email. It calls asc_start_trial, which unlocks all 41 tools for 7 days with no card and nothing to cancel. The key works in the running session, so whatever you were blocked on works on the very next call, and it is saved on your machine, in ~/.asc-mcp/license.json and in any MCP client config that already has an asc-mcp entry, so it survives a restart. One trial per Apple developer account. Without a trial, six tools stay free with no time limit, and most Pro tools that only read work 5 times in total as a preview.

Other ways to install

Claude Desktop, no terminal. Download the .mcpb bundle from the latest release and open it. Claude asks for your Issuer ID and lets you pick the .p8 with a file picker.

As a Claude Code plugin. One line installs the server and the review-triage skill together, and Claude Code asks for your Issuer ID when it enables the plugin:

/plugin install asc-mcp --marketplace pofky/asc-mcp

The plugin lives in plugin/, and its README says what it runs and sends. In your agent, the /asc-start command walks a first-time user through setup.

Running init from an agent, or any pipe. There is no terminal to answer questions in, so pass what would have been asked:

npx @pofky/asc-mcp init --write --issuer <your-issuer-uuid>   # add --config <path> if you keep several client configs

It never invents a value: if the Issuer ID is missing it says so instead of writing a config that fails at Apple's auth. --key-path, --key-id and --license are there for the same reason, and every one of them also reads from the matching ASC_* environment variable. Already paid? --license adds your Pro key to the config.

Global install. npm install -g @pofky/asc-mcp, then use asc-mcp where the examples say npx -y @pofky/asc-mcp.

Manual config. Add to your agent's MCP config (Claude Desktop config, or ~/.claude.json for Claude Code):

{

"mcpServers": { "appstore-connect": { "command": "npx", "args": ["-y", "@pofky/asc-mcp"], "env": { "ASC_ISSUER_ID": "YOUR_ISSUER_ID" } } } }

With the .p8 in ~/.appstoreconnect/private_keys/, ASC_ISSUER_ID is the only required env var (Key ID and key path are auto-detected). Add ASC_LICENSE_KEY to unlock Pro. A key kept elsewhere: set ASC_PRIVATE_KEY_PATH to the file and ASC_KEY_ID to its 10-character ID.

Works with Claude Code, Cursor, Windsurf, Cline, and any MCP-compatible client.

Tools

Free (no signup, no license key)

Pro (free 7-day trial, then $9/month)

$9 per month, VAT included; in the US, Canada and India sales tax is added at checkout, before you pay. Cancel any time.

| draft_review_response | Drafts a public reply to a single review in the review's locale, via Sampling. Elicits tone if your client supports it. Never auto-posts. | Apple gu