Ship an iOS app to App Store review: readiness report, idempotent pipeline, submit.
Runs on your machine from its package; the steps are below.
At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Distributed as an MCP bundle (`https://github.com/beydemirfurkan/appstore-release/releases/download/v4.3.2/appstore-release.mcpb`) — download it and import the bundle in your MCP client.
Ship an iOS app to App Store review by asking your agent.
Real output, recorded against the demo below.
npx skills add beydemirfurkan/appstore-release
Then tell your agent: "Publish my app for review."
The agent reads your app from App Store Connect and names everything that stands between it and review. It then fixes whatever Apple's API allows and submits only once nothing is in the way.
git clone https://github.com/beydemirfurkan/appstore-release && cd appstore-release
source scripts/demo/setup.sh
appstore-release check
appstore-release release
appstore-release submit --submit
The demo runs against a local stand-in for App Store Connect, so nothing leaves your machine.
preflight reads the app itself — Info.plist, privacy manifest, code — offline, and names what App Review rejects before you build: a permission prompt with no reason, accounts that cannot be deleted, a paywall with no restore. Each finding has the guideline, the file and line, and the fix.
check reads the whole app and returns a verdict with an ordered plan. Each finding says whether the tool can fix it or only you can.
release writes the listing: build, metadata in every locale, price, age rating, accessibility labels, screenshots, subscriptions with their offers and offer codes, and in-app purchases. It is idempotent; a second run sends nothing.
submit sends the version with any new plans and purchases, and refuses unless check says ready. check --wait then follows the review to its outcome.
Apple keeps the App Privacy label in its web UI; check tells you exactly where to click. An app's first subscription or in-app purchase goes with the version by API — and if App Store Connect will not take it, nothing is submitted and you get the clicks instead.
Using Expo? Your store.config.json, eas.json and app.json are read as they are.
appstore-release reads the plan and hands each finding to the skill that knows that area:
Coming from 3.x, where the skills were named asc-*? Remove the old ones, then add again:
npx skills remove asc-screenshots asc-age-rating asc-subscriptions asc-rejection asc-credentials asc-testflight asc-reviews
npx skills add beydemirfurkan/appstore-release
/plugin marketplace add beydemirfurkan/appstore-releaseappstore-release.mcpbnpx -y -p github:beydemirfurkan/appstore-release appstore-release-mcp (config)npx github:beydemirfurkan/appstore-release checkConnecting a real app takes an App Store Connect API key and a config file; the reference walks through both.