MCP.Market

Appstore Release MCP server

by rabdulsal·io.github.rabdulsal/appstore-release-mcp·v0.1.1

App Store release pilot — version bump, TestFlight upload, metadata, review submission

C60/100grade C
What users say
No reviews yet
Be the first
Safety scan
C60/100

full report

Adoption
New

0 stars37 downloads/wk

Reviews

Write one

Nobody has reviewed Appstore Release yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Appstore Release tools (8, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • asc_app_status

    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?'

  • asc_bump_version

    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.

  • asc_doctor

    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.

  • asc_job_status

    Check a build/upload job started by asc_upload_build. Returns status (running/succeeded/failed) and the tail of the log.

  • asc_list_builds

    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.

  • asc_submit_reviewwrite action

    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.

  • asc_update_metadatawrite action

    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.

  • asc_upload_buildwrite action

    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.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

1 high
  • Code scan5 source files scanned13/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 38 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • highShell command built from a string (injection risk)exec.shell-concat
    dist/index.js: …version"]]) { try { execSync(`which ${name}`, { stdio: "pipe" }); …
Overall 60/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Appstore Release compares

Against every graded E-commerce MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
60/100
higher than 15% of 2,174 E-commerce servers
Tools
8
the typical E-commerce server has 6
Tools that change things
38%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
37
more than 35% of 411 E-commerce servers with a package

What its tools let an agent do: 5 read · 3 change

Install Appstore Release in Claude Code, Cursor or VS Code

Runs npx -y appstore-release-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add appstore-release-mcp -- npx -y appstore-release-mcp
Add to Cursor

What the publisher says

From the Appstore Release repository's README, as published. We do not edit it. Read it on GitHub

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 submission
  • ascuploadbuild — 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)
  • ascuploadipa — already have a signed .ipa? (from eas build, a CI pipeline, a manual Xcode archive) Upload it directly via xcrun altool — no fastlane, no local archive step, nothing to configure beyond the ASC API key you already have
  • Local version bumping across project.pbxproj (and project.yml for xcodegen projects)

Requirements

  • macOS with Xcode command line tools (xcrun altool — used by ascuploadipa)
  • fastlane with a lane that builds and uploads (e.g. beta) — only needed for ascuploadbuild; skip it entirely if you're only using ascuploadipa
  • An App Store Connect API key (.p8)

Setup

  1. 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/.
  1. 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 ASCPLATFORM=MACOS -e ASCFASTLANEPLATFORM=mac.

  1. Verify: ask the agent to run asc_doctor. All checks should be ✓.

Tools

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_REVIEW

Already have a signed .ipa (EAS Build, CI, manual archive) — no fastlane needed:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Appstore Release: common questions

Is Appstore Release MCP server safe?
With care: it is graded C, so read the findings first (60/100). Read the Appstore Release safety report
How do I install Appstore Release?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Appstore Release need an API key?
Yes. The registry entry asks for APPLE_KEY_CONTENT.
Is Appstore Release maintained?
The last commit was 77 days ago (2026-08-19). The latest release is v0.1.1.
What can I use instead of Appstore Release?
Servers from other publishers that do the same job: Appstoreconnect MCP server, Appstore Connect MCP server and AsoBeast MCP server.
How does Appstore Release compare with other E-commerce MCP servers?
safety score 60/100 (higher than 15% of 2,174 E-commerce servers); tools 8 (the typical E-commerce server has 6); tools that change things 38% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Appstore Release

Same job from other publishers: the closest match first, then the best rated.

  • Appstoreconnect
    App Store Connect for MCP clients: PPP pricing, subscriptions, TestFlight, reviews, reports & more
    A
  • Appstore Connect
    MCP server for Apple's App Store Connect API. Manage apps, TestFlight, and more.
    A
  • AsoBeast
    App Store and Google Play ASO: keyword rankings, competitors, reviews, audits and an action queue.
    A
  • Storelift
    App Store & Google Play keyword ranks, rivals, reviews and AI visibility. Free plan included.
    A
  • Apify
    Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
    A