app-store-connect-mcp

MCP server for managing Apple's App Store Connect. 📦

Status: offline validation implemented; not published. A source build exposes get_capabilities, validate_repository, documentation, and eight generated JSON Schemas. Authentication and bounded Apple transport have automated tests; discovery and all mutations remain pending. The intended first-release features below are not yet available.

Keep App Store metadata and localized screenshot sources beside your application code. Let an MCP-capable agent inspect the account, validate the repository, show a concrete change plan, and apply the approved changes through Apple's documented APIs.

Intended first release

• Register bundle IDs and reconcile explicitly requested capabilities. Inspect an Xcode project to propose the identifiers and capabilities it needs.

• Discover existing App Store app records, prepare the manual bootstrap for a missing record, and create editable platform versions.

• Synchronize localized names, subtitles, descriptions, keywords, support URLs, privacy-policy URLs, and other supported listing fields.

• Manage version-wide copyright and App Review contact information and notes.

• Upload, verify, order, and reconcile localized screenshots for a selected version and display type, using reusable source files in AppStore/assets/.

• Configure an explicitly managed base price and storefront availability. New configuration templates start free and request all current territories.

• Provide explicit certificate, device, and provisioning-profile workflows without automatic certificate revocation or private-key custody.

• Check submission readiness, select an already uploaded build, and submit a selected version only through a separate approved submission operation.

An unchanged second sync must produce no writes. Omitted fields remain untouched. A regular metadata sync must never submit or release an app.

Related MCP server: App Store Connect MCP Server

Boundaries

The initial App Store app record requires a manual bootstrap unless a documented public creation endpoint is verified during implementation. This is distinct from registering a bundle ID or creating a version. See API capabilities.

Media Manager is not treated as a separate cloud library. Files are assigned to version-localization screenshot sets. Reuse between versions means reusing repository paths and reconciling each destination, not assuming a screenshot ID can have several parents.

Uploading a privacy-policy URL does not complete Apple's privacy questionnaire. Builds, age ratings, export-compliance declarations, agreements, and regional requirements can still block submission. The server must report those blockers rather than invent answers.

Intended setup

Runtime target: Node.js 24 LTS. Xcode inspection is macOS-only; ordinary API and manifest operations should also work on Linux. A local checkout of the app repository must be accessible to the server process.

After publication, the intended MCP launch is:

npx -y @thatfactory/app-store-connect-mcp --allowed-root /absolute/path/to/app-repository

This is read-only with respect to Apple. To permit approved write plans, start it with --allow-writes. Add --allow-submission separately only when review submission is intended. Neither flag removes plan validation or the host's responsibility to obtain user approval.

Use the same credentials as xcode-cloud-mcp:

The private key accepts literal multiline PEM or escaped \n. A present primary variable wins over its alias; malformed or blank primary values fail clearly rather than silently selecting a different identity. The server does not read a repository .env automatically. Supply credentials through the MCP host or the process environment.

Credential compatibility does not imply permission compatibility. A key that can read Xcode Cloud might lack permission for provisioning or app metadata. The server reports authorization failures with the affected resource and operation.

Repository layout

AppStore/
  app.json
  commerce.json
  provisioning.json                 # optional
  info/
    en-US.json
    de-DE.json
    fr-FR.json
    ja.json
    pt-BR.json
  versions/
    macOS/
      1.0/
        version.json
        review.json
        review-notes.txt
        localizations/
          en-US/
            metadata.json
            description.txt
            keywords.txt
            screenshots.json
          ...
  assets/
    screenshots/
      macOS/
        en-US/
          01-overview.png
          02-weekly-budget.png
        ...

See the format specification for defaults, optional files, localization rules, screenshot ordering, and safe secret references. The server reads the local checkout; it neither clones repositories nor commits or pushes changes by itself.

Example agent requests

Import Headroom's existing App Store information into a new local export directory. Do not overwrite my repository files.

Validate AppStore, then plan the German, French, Japanese, and Brazilian Portuguese metadata for macOS version 1.0. Leave English, pricing, screenshots, and submission unchanged.

Plan the screenshots listed for version 1.0 in every configured locale. Show missing files, ordering changes, and any removals before applying.

Inspect the app target and propose any missing bundle IDs or portal capabilities. Do not change the Xcode project or register anything yet.

Development and documentation

Run npm ci and npm run check for strict type checking, tests, build, and a clean packed-package MCP smoke test. Run node dist/index.js --help for local launch options. CI and nightly execute the same checks on Node 24 without Apple credentials.

Product explains the longer-term vision. Architecture defines internal boundaries. Execution plan breaks implementation into reviewable changes. Sources records the research baseline.

Planned distribution: public scoped npm package, MIT license, GitHub release publishing with trusted publishing where configured. Keep all customer repositories, credentials, exported review information, and signing artifacts out of the package tarball.

This is an independent project and is not affiliated with or endorsed by Apple.

Offline validation

Start with --allowed-root /absolute/path/to/checkout, then call validate_repository with the absolute AppStore directory as root. Optional domains, locales, platform (directory spelling, such as macOS) and version limit the check. Domains: appInfo, versionMetadata, version, review, screenshots, commerce, provisioning. With no selector, validation considers declared platforms and discovered versions.

The initial locale registry covers en-US, de-DE, fr-FR, ja and pt-BR. Other Apple-supported locales require registry expansion. Validation preserves omission/null/empty values; it does not determine creation completeness or release readiness. JSON schema checks, paths, text budgets and screenshot manifests are implemented; decoded image validation remains Phase 07. Review environment references are field-allowlisted and resolved values never appear in results. Character checks use conservative UTF-16 units and report code points/graphemes/UTF-8 bytes for prose. No URLs are fetched.

The validator bounds each text/JSON file to 1 MiB, each referenced asset to 32 MiB, total read bytes to 64 MiB and files to 2000 per request. Results include up to 200 diagnostics and explicitly report truncation. Use narrower selectors for larger roots. The synthetic example validates structurally but is not a ready-to-submit listing. Run npm run schemas:check to verify published schemas match the runtime validators.