Labsco
MCP SERVER

Appstore Connect MCP

by pofky

Drive an App Store release from your agent: edit metadata, upload screenshots, attach a build, submit and release.

Mobile & App Store Release
Summary
The release chain, not another wrapper over the API.

Other App Store Connect servers hand an agent hundreds of raw endpoints and leave the sequencing to it. This one is shaped like the job: sign, archive, upload, wait for the build to go valid, attach it, push metadata and screenshots, audit, submit, release — with the handful of steps Apple keeps out of the API returned as explicit website instructions rather than silently skipped.

What it is

An App Store Connect server built around release work rather than raw endpoints: 41 tools that read your apps and reviews, audit a version before submission, and then actually write — metadata, screenshots, builds, TestFlight, in-app purchases, submission and release. Published as `@pofky/asc-mcp`, version 1.9.5, over stdio.

What you get
  • Six tools that cost nothing: `list_apps`, `app_details`, `review_status`, plus `asc_setup_check` for diagnosing a broken connection, `asc_guide` for the in-agent playbook, and `asc_start_trial`
  • A pre-submission audit that reads as the single source of truth for 'is this submittable' — `release_preflight` checks metadata, character limits, screenshots and build state, and ends with the steps Apple only allows in the website
  • The whole ship chain: `create_version`, `update_version_metadata`, `upload_screenshots`, `wait_for_build`, `attach_build`, `submit_for_review`, `release_version`, `manage_phased_release`
  • Store-front settings in one place — `set_app_metadata`, `set_app_price`, `set_app_availability`, `set_age_rating`, `set_review_contact`
  • TestFlight distribution: `list_beta_groups`, `assign_build_to_group`, `invite_beta_tester`
  • Binary work driven through Xcode on your own Mac — `setup_app_store_signing`, `build_and_archive`, `upload_binary`
  • Reading the market and your users: `list_reviews`, `sales_report`, `daily_briefing`, `keyword_insights`, `competitor_snapshot`, `metadata_diff`, and `release_notes` built from commits since your last tag
  • Review clustering and reply drafts that run on your own client's model through MCP Sampling — `triage_reviews`, `draft_review_response`, which never auto-posts
  • Six slash-command workflows, among them /asc-ship-release and /asc-rejection-audit, shipped as MCP Prompts
Requirements

Node.js 18+, membership of the Apple Developer Program, and an App Store Connect API key created with the Admin or App Manager role. Three environment variables are declared required: `ASC_KEY_ID`, `ASC_ISSUER_ID` and `ASC_PRIVATE_KEY_PATH`, the last pointing at the .p8 file Apple lets you download exactly once; `ASC_LICENSE_KEY` is optional and unlocks the paid half. Running `npx @pofky/asc-mcp init --write` finds the key, asks for the Issuer ID and merges the server block into your client config. The .p8 is read locally and the JWT is minted on your machine. Pricing is a 7-day trial, started from inside the agent, then $9/month; every outward-facing action — submit, release, upload — needs an explicit confirm flag.

Setup effort

One command plus a key — npx @pofky/asc-mcp init --write, then supply credentials