What App Store Release MCP server does
The App Store Release MCP server helps prepare an iOS app for App Store review. It combines local inspection with App Store Connect operations so an agent can assess the app, update supported release information, and submit only after readiness checks pass.
Its preflight analysis examines the app’s Info.plist, privacy manifest, and source code without sending those files to App Store Connect. Findings can cover issues such as missing permission explanations, unavailable account deletion, or a purchase flow without restore functionality. Each result identifies the relevant guideline, file and line when available, and a proposed fix.
How it works
The workflow is divided into three main commands. check reads the app and connected App Store Connect data, then returns a verdict and an ordered action plan. Results indicate whether the server can make a change through Apple’s API or whether the developer must complete the task manually.
release writes supported store data, including the build, localized metadata, price, age rating, accessibility labels, screenshots, subscriptions, offers, offer codes, and in-app purchases. Repeating the command is intended to be idempotent, so an unchanged second run does not send duplicate updates.
submit submits the version and eligible new plans or purchases, but refuses to proceed unless the check reports that the app is ready. The check --wait option can then follow the review until it reaches an outcome. App Privacy label changes remain a web-console task; the check output provides the required navigation guidance.
Setup and configuration
Install the skills package with npx skills add beydemirfurkan/appstore-release, then ask the agent to publish the app for review. The project also provides an MCP launch command, a Claude Desktop bundle, a Claude Code plugin installation path, and a CLI command for running checks directly.
A real app requires an App Store Connect API key and a configuration file. The project’s reference documentation provides the quick-start procedure for connecting those credentials. Node 20.11 or newer is listed as a runtime requirement. Expo projects can use their existing store.config.json, eas.json, and app.json files.
A local demonstration is available for testing without an Apple account. It uses a local App Store Connect stand-in, so the sample check, release, and submit commands do not send data outside the machine.
Tools and capabilities
The App Store Release MCP server covers these release areas:
- App review preflight checks
- Screenshot sizing and upload, including iPhone Duo and iPad
- Age-rating questionnaire data
- Subscription plans, trials, and lifetime purchases
- Rejection handling and resubmission guidance
- EAS certificates and provisioning profiles
- TestFlight groups, testers, beta review, and What to Test content
- Customer review reading, reply drafting, and approval-controlled publishing
Limitations and notes
Apple’s App Privacy label is not managed through the API workflow described here, so it must be handled in App Store Connect’s web interface. The first subscription or in-app purchase can be submitted with the version through the API, but if App Store Connect rejects that operation, the server does not submit anything and instead provides the manual steps.
The App Store Release MCP server is not affiliated with Apple. Its listed compatibility target is App Store Connect API 4.5 and iOS 27. Older skill names from the 3.x series must be removed before installing the current skill set.