App Store Connect MCP Integration

Core principle: When asc-mcp is configured, you can manage the entire App Store Connect workflow without leaving Claude Code — submit builds, distribute to TestFlight, respond to reviews, and monitor metrics programmatically.

Setup

Install

brew install mint
mint install zelentsov-dev/asc-mcp@1.4.0

Create API Key

1. Open App Store Connect → Users and Access → Integrations → API
2. Generate key with Admin or App Manager role
3. Download the

   .p8

   file (one-time download — save it securely)
4. Note the Key ID and Issuer ID

Add to Claude Code

claude mcp add asc-mcp \
  -e ASC_KEY_ID=YOUR_KEY_ID \
  -e ASC_ISSUER_ID=YOUR_ISSUER_ID \
  -e ASC_PRIVATE_KEY_PATH=/path/to/AuthKey.p8 \
  -- ~/.mint/bin/asc-mcp

Verify

Ask Claude to call

company_current

Worker Filtering

asc-mcp has 25 workers (~208 tools). Loading all of them wastes context. Use

--workers

Presets

apps,builds,beta_groups,beta_testers

apps,builds,versions,reviews

apps,iap,subscriptions,offer_codes,pricing

To use a preset, add

--workers

claude mcp add asc-mcp \
  -e ASC_KEY_ID=... \
  -e ASC_ISSUER_ID=... \
  -e ASC_PRIVATE_KEY_PATH=... \
  -- ~/.mint/bin/asc-mcp --workers apps,builds,versions,reviews

Note:

company

auth

--workers

builds

build_processing

build_beta

Worker Selection Decision Tree

digraph workers {
    "What are you doing?" [shape=diamond];
    "TestFlight preset" [shape=box, label="--workers apps,builds,\nbeta_groups,beta_testers"];
    "Release preset" [shape=box, label="--workers apps,builds,\nversions,reviews"];
    "Monetization preset" [shape=box, label="--workers apps,iap,\nsubscriptions,offer_codes,pricing"];
    "Full (no flag)" [shape=box, label="No --workers flag\n(all 208 tools)"];

    "What are you doing?" -> "TestFlight preset" [label="distributing beta builds"];
    "What are you doing?" -> "Release preset" [label="submitting to App Store"];
    "What are you doing?" -> "Monetization preset" [label="managing IAP/subscriptions"];
    "What are you doing?" -> "Full (no flag)" [label="multiple tasks or unsure"];
}

Workflow: Release Pipeline

Submit a new version to the App Store.

1. apps_search(query: "MyApp")           → get app ID
2. builds_list(appId, limit: 5)          → find latest processed build
3. app_versions_create(appId, platform: "IOS", versionString: "2.1.0")
4. app_versions_attach_build(versionId, buildId)
5. app_versions_set_review_details(versionId, { contactEmail, notes, ... })
6. app_versions_submit_for_review(versionId)
7. (After approval) app_versions_create_phased_release(versionId)

Before step 3: Version string must not already exist. Check with

app_versions_list

Before step 4: Build must be in

VALID

builds_get_processing_state

Before step 6: Version must be in

PREPARE_FOR_SUBMISSION

Workflow: TestFlight Distribution

Distribute a build to beta testers.

1. apps_search(query: "MyApp")           → get app ID
2. builds_list(appId, limit: 5)          → find latest build
3. builds_set_beta_localization(buildId, locale: "en-US", whatsNew: "Bug fixes")
4. beta_groups_list(appId)               → find or create group
   OR beta_groups_create(appId, name: "Internal Testers", isInternal: true)
5. beta_groups_add_builds(groupId, [buildId])
6. builds_send_beta_notification(buildId) → notify testers (optional)

Tip: Internal testers (up to 100) get builds immediately. External testers (up to 10,000) require Beta App Review for the first build of each version.

Workflow: Review Management

Monitor and respond to App Store reviews.

1. apps_search(query: "MyApp")           → get app ID
2. reviews_list(appId, sort: "-createdDate", limit: 20)
   OR reviews_list(appId, filterRating: "1,2")  → negative reviews only
3. reviews_stats(appId)                  → rating distribution summary
4. reviews_create_response(reviewId, responseBody: "Thank you for...")

Response guidelines:

• Respond to negative reviews within 24-48 hours
• Be professional and offer specific help
• Updating a response replaces the previous one (users see "Developer Response")

Workflow: Feedback Triage

Correlate TestFlight feedback with build diagnostics.

1. builds_list(appId, limit: 10)         → recent builds
2. builds_get_beta_testers(buildId)      → who tested this build
3. metrics_build_diagnostics(buildId)    → crash signatures for this build
4. metrics_get_diagnostic_logs(signatureId) → individual crash logs

Limitation: TestFlight text feedback and screenshots are NOT available via the App Store Connect API. Use Xcode Organizer or the ASC web dashboard for feedback content.

Workflow: Multi-Company

Switch between App Store Connect teams.

1. company_list                          → see configured accounts
2. company_switch(companyId: "client-a") → switch active account
3. (All subsequent calls use client-a's credentials)

Multi-Company Setup

Add to

~/.config/asc-mcp/companies.json

{
  "companies": [
    {
      "id": "my-company",
      "name": "My Company",
      "key_id": "KEY_ID_1",
      "issuer_id": "ISSUER_1",
      "key_path": "/Users/you/.keys/AuthKey1.p8"
    },
    {
      "id": "client-a",
      "name": "Client A",
      "key_id": "KEY_ID_2",
      "issuer_id": "ISSUER_2",
      "key_path": "/Users/you/.keys/AuthKey2.p8"
    }
  ]
}

Or use numbered environment variables:

ASC_COMPANY_1_NAME

ASC_COMPANY_1_KEY_ID

Key Tool Quick Reference

Apps & Builds

apps_search

query

apps_list

limit

builds_list

appId

limit

sort

builds_find_by_number

appId

buildNumber

builds_get_processing_state

buildId

builds_check_readiness

buildId

Versions & Submission

app_versions_create

appId

platform

versionString

app_versions_attach_build

versionId

buildId

app_versions_set_review_details

versionId

contactEmail

notes

app_versions_submit_for_review

versionId

app_versions_cancel_review

versionId

app_versions_release

versionId

app_versions_create_phased_release

versionId

TestFlight

beta_groups_create

appId

name

isInternal

beta_groups_add_testers

groupId

testerIds

beta_groups_add_builds

groupId

buildIds

builds_set_beta_localization

buildId

locale

whatsNew

builds_send_beta_notification

buildId

Reviews & Metrics

reviews_list

appId

sort

filterRating

limit

reviews_stats

appId

reviews_create_response

reviewId

responseBody

metrics_app_perf

appId

metrics_build_diagnostics

buildId

API Constraints

PREPARE_FOR_SUBMISSION

en-US

ja

de-DE

zh-Hans

ru

builds_get_processing_state

app_versions_update_phased_release

Gotchas

builds_get_processing_state

VALID

app_versions_list

PREPARE_FOR_SUBMISSION

apps_search

company_current

analytics_*

vendor_number

Anti-Rationalization

app_versions_set_review_details

app_versions_submit_for_review

company_current

When asc-mcp is NOT Available

If asc-mcp is not configured, fall back to manual workflows:

• Crash analysis: Use Xcode Organizer (see

  axiom-testflight-triage

  ) or App Store Connect web dashboard (see

  axiom-app-store-connect-ref

  )
• TestFlight distribution: Use Xcode → Product → Archive → Distribute, or

  xcodebuild

  +

  altool

• Review management: Use App Store Connect web dashboard
• Submission: Use Xcode → Product → Archive → Distribute to App Store

Resources

Skills: axiom-app-store-submission, axiom-app-store-ref, axiom-app-store-connect-ref, axiom-testflight-triage

Agents: crash-analyzer, security-privacy-scanner, iap-auditor