Server data from the Official MCP Registry
App Store release pilot — version bump, TestFlight upload, metadata, review submission
App Store release pilot — version bump, TestFlight upload, metadata, review submission
Valid MCP server (2 strong, 4 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.
6 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: APPLE_KEY_ID
Environment variable: APPLE_ISSUER_ID
Environment variable: ASC_KEY_PATH
Environment variable: APPLE_KEY_CONTENT
Environment variable: APPLE_TEAM_ID
Environment variable: ASC_BUNDLE_ID
Environment variable: ASC_PROJECT_DIR
Environment variable: ASC_PLATFORM
Environment variable: ASC_FASTLANE_LANE
Environment variable: ASC_FASTLANE_PLATFORM
Environment variable: ASC_UPLOAD_CMD
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-rabdulsal-appstore-release-mcp": {
"env": {
"APPLE_KEY_ID": "your-apple-key-id-here",
"ASC_KEY_PATH": "your-asc-key-path-here",
"ASC_PLATFORM": "your-asc-platform-here",
"APPLE_TEAM_ID": "your-apple-team-id-here",
"ASC_BUNDLE_ID": "your-asc-bundle-id-here",
"ASC_UPLOAD_CMD": "your-asc-upload-cmd-here",
"APPLE_ISSUER_ID": "your-apple-issuer-id-here",
"ASC_PROJECT_DIR": "your-asc-project-dir-here",
"APPLE_KEY_CONTENT": "your-apple-key-content-here",
"ASC_FASTLANE_LANE": "your-asc-fastlane-lane-here",
"ASC_FASTLANE_PLATFORM": "your-asc-fastlane-platform-here"
},
"args": [
"-y",
"appstore-release-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
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: archiving, signing, and uploading your binary. This server is a release pilot, not an API browser:
node:crypto) for status, builds, metadata, and review submissionproject.pbxproj (and project.yml for xcodegen projects)beta) — only needed for asc_upload_build; all other tools are pure REST.p8)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-mcp
For a macOS app whose Fastfile uses platform :mac, add -e ASC_PLATFORM=MAC_OS -e ASC_FASTLANE_PLATFORM=mac.
asc_doctor. All checks should be ✓.| Tool | What it does |
|---|---|
asc_doctor | Verify config, creds, fastlane, xcodebuild, app record — run first |
asc_app_status | Versions + review states + recent builds in one call |
asc_list_builds | Build processing states (wait for VALID after upload) |
asc_bump_version | Bump build number / set marketing version in local project files |
asc_upload_build | Run your fastlane upload lane as an async job — returns job ID immediately |
asc_job_status | Poll a build job; status + log tail |
asc_update_metadata | Description / keywords / what's-new / promo text via REST |
asc_submit_review | Attach build + create review submission + submit |
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_REVIEW
Credential names deliberately match fastlane's app_store_connect_api_key, so one credential set serves both.
| Var | Required | Notes |
|---|---|---|
APPLE_KEY_ID | yes | ASC API key ID |
APPLE_ISSUER_ID | yes | ASC issuer ID |
APPLE_KEY_CONTENT / ASC_KEY_PATH | one of | base64-encoded .p8 / path to .p8 file |
APPLE_TEAM_ID | for builds | Apple Developer team ID |
ASC_BUNDLE_ID | yes | your app's bundle identifier |
ASC_PROJECT_DIR | recommended | Xcode project root where fastlane runs (default: cwd) |
ASC_PLATFORM | no | IOS (default), MAC_OS, TV_OS, VISION_OS |
ASC_FASTLANE_LANE | no | upload lane name (default: beta) |
ASC_FASTLANE_PLATFORM | no | fastlane platform prefix, e.g. mac or ios |
ASC_UPLOAD_CMD | no | full override, e.g. bundle exec fastlane ios beta |
~/.appstore-mcp/jobs/ either way.asc_submit_review is the point of no return for a release — the tool description tells agents to confirm with a human first.MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.