appstore-release-mcp
You can drive the full App Store release cycle for iOS/macOS apps: version bumping, building/uploading binaries, managing metadata, and submitting for review — all via an MCP server.
Verify environment & credentials:
asc_doctorchecks toolchain, ASC API keys, fastlane/xcodebuild/altool, and app record.Check release status:
asc_app_statusshows app versions, review states, and recent build processing states;asc_list_buildslists processing states (wait for VALID).Bump local version:
asc_bump_versionincrements build number and optionally sets marketing version in project.pbxproj and project.yml.Upload builds two ways:
asc_upload_build— runs your fastlane lane (e.g.,fastlane beta) as an async job; returns job ID for polling.asc_upload_ipa— uploads an existing signed.ipaviaxcrun altool(no fastlane needed), also async.
Poll long-running jobs:
asc_job_statusreturns status and log tail for uploads.Update App Store metadata:
asc_update_metadatasets description, keywords, what's-new, promo text; can create a new version if needed.Submit for review:
asc_submit_reviewattaches a build (optional) and creates/submits the review submission — the point of no return, requires human confirmation.
Provides tools for managing the full App Store release cycle: version bumping, binary upload (via fastlane), metadata updates, review submission, and status checking through the App Store Connect API.
Allows running your fastlane lanes for archiving, signing, and uploading your app binary to App Store Connect as an async job with log polling.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@appstore-release-mcp Run asc_doctor to verify my configuration"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
appstore-release-mcp
An MCP server that drives the full App Store release cycle for iOS and macOS apps: version bump → archive + TestFlight upload → metadata → review submission → status.
What makes it different: existing App Store Connect MCP servers wrap the REST API — metadata, TestFlight management, analytics. None of them can do the one step the REST API doesn't support: getting a binary onto Apple's servers. This server is a release pilot, not an API browser, and gives you two ways to do that:
Direct ASC REST API (ES256 JWT, zero-dependency signing via
node:crypto) for status, builds, metadata, and review submissionasc_upload_build— your existing fastlane lane archives, signs, and uploads, run as an async job with log polling (a real archive takes 5–15 minutes — no MCP timeout can hold that)asc_upload_ipa— already have a signed.ipa? (fromeas build, a CI pipeline, a manual Xcode archive) Upload it directly viaxcrun altool— no fastlane, no local archive step, nothing to configure beyond the ASC API key you already haveLocal version bumping across
project.pbxproj(andproject.ymlfor xcodegen projects)
Requirements
macOS with Xcode command line tools (
xcrun altool— used byasc_upload_ipa)fastlane with a lane that builds and uploads (e.g.
beta) — only needed forasc_upload_build; skip it entirely if you're only usingasc_upload_ipaAn App Store Connect API key (
.p8)
Related MCP server: xcode-cloud-mcp
Setup
Generate an ASC API key (once): App Store Connect → Users and Access → Integrations → App Store Connect API → Team Keys → Generate (role: App Manager). Download the
.p8— Apple lets you download it exactly once. Keep it in~/.appstoreconnect/private_keys/.Register with Claude Code:
claude mcp add appstore \
-e APPLE_KEY_ID=XXXXXXXXXX \
-e APPLE_ISSUER_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx \
-e ASC_KEY_PATH=$HOME/.appstoreconnect/private_keys/AuthKey_XXXXXXXXXX.p8 \
-e APPLE_TEAM_ID=XXXXXXXXXX \
-e ASC_BUNDLE_ID=com.example.myapp \
-e ASC_PROJECT_DIR=/path/to/your/xcode/project \
-- npx appstore-release-mcpFor a macOS app whose Fastfile uses platform :mac, add -e ASC_PLATFORM=MAC_OS -e ASC_FASTLANE_PLATFORM=mac.
Verify: ask the agent to run
asc_doctor. All checks should be ✓.
Tools
Tool | What it does |
| Verify config, creds, fastlane/xcodebuild/altool, app record — run first |
| Versions + review states + recent builds in one call |
| Build processing states (wait for |
| Bump build number / set marketing version in local project files |
| Run your fastlane upload lane as an async job — returns job ID immediately |
| Upload an already-built |
| Poll a job started by |
| Description / keywords / what's-new / promo text via REST |
| Attach build + create review submission + submit |
Release walkthrough
Building locally with fastlane:
asc_doctor # toolchain healthy?
asc_bump_version {marketing_version: "1.1.0"}
asc_upload_build # → job id
asc_job_status {job_id} # poll until succeeded
asc_list_builds # wait for processingState VALID
asc_update_metadata {whats_new: "...", create_version: "1.1.0"}
asc_submit_review {build_id} # point of no return
asc_app_status # WAITING_FOR_REVIEWAlready have a signed .ipa (EAS Build, CI, manual archive) — no fastlane needed:
asc_doctor
asc_upload_ipa {ipa_path: "./build/app.ipa"} # → job id
asc_job_status {job_id} # poll until succeeded
asc_list_builds # wait for processingState VALID
asc_update_metadata {whats_new: "...", create_version: "1.1.0"}
asc_submit_review {build_id}
asc_app_statusEnvironment variables
Credential names deliberately match fastlane's app_store_connect_api_key, so one credential set serves both.
Var | Required | Notes |
| yes | ASC API key ID |
| yes | ASC issuer ID |
| one of | base64-encoded |
| for | Apple Developer team ID (not needed for |
| yes | your app's bundle identifier |
| recommended | Xcode project root where fastlane runs (default: cwd) |
| no |
|
| no | upload lane name (default: |
| no | fastlane platform prefix, e.g. |
| no | full override, e.g. |
Notes
Build jobs are children of the server process; if the MCP client disconnects mid-build the job dies. Logs persist in
~/.appstore-mcp/jobs/either way.asc_submit_reviewis the point of no return for a release — the tool description tells agents to confirm with a human first.
License
MIT
Available Tools
8 toolsasc_app_statusA
Snapshot of the app's release state: latest App Store versions with their review states, and recent builds with processing states. Use this to answer 'where is the release right now?'
Inputs: no named parameters.
asc_bump_versionA
Bump the local app version before a build. Increments the build number (CURRENT_PROJECT_VERSION) and optionally sets a new marketing version. Updates every .xcodeproj/project.pbxproj in the project dir, plus project.yml if the project uses xcodegen, so all sources stay in sync.
Inputs: bump_build, marketing_version.
asc_doctorA
Verify the release toolchain end-to-end: ASC API credentials, mac-app directory, fastlane, xcodebuild, and (if creds are present) that the app record exists in App Store Connect. Run this first in any release session.
Inputs: no named parameters.
asc_job_statusA
Check a build/upload job started by asc_upload_build. Returns status (running/succeeded/failed) and the tail of the log.
Inputs: job_id (required), log_lines.
asc_list_buildsA
List recent uploaded builds and their processing states (PROCESSING → VALID before they can be submitted). Use after an upload to watch for the build becoming VALID.
Inputs: limit.
asc_submit_reviewA
Submit the editable App Store version for review: optionally attach a build, then create and submit a review submission. The build must have processingState VALID (check asc_list_builds). This is the point of no return for a release — confirm with the human first.
Inputs: build_id.
asc_update_metadataA
Update App Store listing metadata (description, keywords, what's-new, promotional text) on the currently editable version via the ASC API. If no editable version exists, pass create_version to open a new one.
Inputs: locale, keywords, whats_new, description, +2 more.
asc_upload_buildA
Archive, sign, and upload the app to TestFlight via the configured fastlane lane (default: fastlane beta; see ASC_FASTLANE_* / ASC_UPLOAD_CMD env vars). Runs asynchronously (5–15 min) — returns a job ID immediately; poll with asc_job_status. Note: if the lane calls increment_build_number you do NOT need asc_bump_version first unless changing the marketing version.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool addresses a distinct step in the release workflow (environment check, version bump, upload, status polling, build listing, metadata update, submission). No two tools have overlapping responsibilities.
All tools share the 'asc_' prefix and use lowercase with underscores. Most are verb_noun (bump_version, list_builds), but 'asc_doctor' and 'asc_app_status' are noun-based, introducing slight inconsistency.
With 8 tools, the set is well-scoped for a release management server. Each tool serves a necessary function without redundancy, and the number is ideal for agent usability.
The tools cover the essential release lifecycle: environment verification, version bumping, build upload, status tracking, build listing, metadata update, and review submission. Minor gaps like cancellation or rollback are not present but are acceptable for a focused toolset.
Maintenance
Related MCP Connectors
Create App Store screenshots, icons, ASO copy, localization, and revisions via hosted MCP.
Run App Store Connect from your IDE: pricing, listings, screenshots, releases, AI visibility.
MCP server for Appcircle mobile CI/CD platform.
Hosted iOS app intelligence and creative research MCP server.
Related MCP Servers
- AlicenseBqualityFmaintenanceAn MCP server to communicate with the App Store Connect API for iOS Developers25332MIT
- AlicenseBqualityBmaintenanceMCP server for managing Xcode Cloud workflows, builds, and test artifacts via the App Store Connect API.1742 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for shipping iOS apps, enabling screenshots of simulators, managing App Store Connect metadata, and submitting apps for review.5 npmMIT
- AlicenseNot gradedqualityCmaintenanceApp Store Connect MCP Server (Swift) that manages apps, builds, TestFlight, metadata, reviews natively on macOSMIT