App Store Connect MCP Server

A Model Context Protocol server for the App Store Connect API. It lets AI assistants manage apps, versions, localizations, screenshots, creative assets, in-app purchases, pricing and availability, App Review details, TestFlight, bundle IDs, devices, users, and analytics reports.

Forked from JoshuaRileyDev/app-store-connect-mcp-server (archived).

Setup

Create an API key in App Store Connect → Users and Access → Integrations, download the .p8 file, and note the Key ID and Issuer ID.

Add the server to your MCP client config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "app-store-connect": {
      "command": "npx",
      "args": ["-y", "@yunyang088/app-store-connect-mcp-server"],
      "env": {
        "APP_STORE_CONNECT_KEY_ID": "YOUR_KEY_ID",
        "APP_STORE_CONNECT_ISSUER_ID": "YOUR_ISSUER_ID",
        "APP_STORE_CONNECT_P8_PATH": "/path/to/AuthKey_XXXXXXXXXX.p8",
        "APP_STORE_CONNECT_VENDOR_NUMBER": "OPTIONAL"
      }
    }
  }
}

For Claude Code:

claude mcp add app-store-connect \
  -e APP_STORE_CONNECT_KEY_ID=YOUR_KEY_ID \
  -e APP_STORE_CONNECT_ISSUER_ID=YOUR_ISSUER_ID \
  -e APP_STORE_CONNECT_P8_PATH=/path/to/AuthKey_XXXXXXXXXX.p8 \
  -- npx -y @yunyang088/app-store-connect-mcp-server

APP_STORE_CONNECT_VENDOR_NUMBER is optional. When set, the sales and finance report tools are enabled.

Related MCP server: App Store Connect MCP Server

Tools

Notes:

• upload_app_screenshot handles the full reserve → upload → commit flow for a local PNG.

• create_app_screenshot_set expects display types with the APP_ prefix, e.g. APP_IPHONE_67.

• Asset Library flow: upload_asset_library_media (reserve → upload → commit → wait for processing) → create_asset_placement on a version localization.

  • Product page header: PRODUCT_PAGE_HEADER_ASSET, 21:9 3840×1646 PNG. Search results: APP_STORE_SEARCH_RESULTS_ASSET, 3:2 up to 3840×2560. A 16:9 5244×2950 PNG universal asset fits both. Both use placement group DEFAULT_PROFILE, one per localization; upload with category CREATIVE_ASSETS.

  • iPhone Duo screenshots have no legacy screenshotDisplayType; upload with category APP_SCREENSHOTS_AND_PREVIEWS and place as APP_SCREENSHOT in group IPHONE_DUO_PROFILE (2853×2007 / 2034×1398, or portrait).

  • get_asset_library_ref_data returns the live specs and placement groups.

• When a new version is being prepared, the app has two app infos (live and editable). App info localization tools now resolve the editable one, so name/subtitle edits go to the version being prepared.

• In-app purchase flow: create_in_app_purchase → create_in_app_purchase_localization per locale → list_in_app_purchase_price_points (e.g. territory: USA, customerPrice: "0.99") → set_in_app_purchase_price → set_in_app_purchase_availability → upload_in_app_purchase_review_screenshot.

  • Since API 4.4.1, localizations belong to an in-app purchase version. A new in-app purchase comes with version 1 in PREPARE_FOR_SUBMISSION; given only inAppPurchaseId, the localization tool posts to that draft version (v2) and falls back to the deprecated v1 endpoint if there is none. Update/delete try v2 first and fall back to v1 on 404.

  • Price and availability tools replace the whole schedule / territory list. excludeTerritoryIds: ["CHN"] selects every territory except mainland China. Territory IDs in both lists are checked, so a typo such as CN is rejected instead of being ignored.

  • The first in-app purchase of an app has to be submitted together with an app version on the App Store Connect website; there is no submission tool here.

• set_app_availability creates the app's availability once (POST /v2/appAvailabilities, every territory listed with available true/false). After it exists, use update_territory_availability with IDs from get_app_availability.

• set_app_price_schedule with free: true looks up the 0.00 price point in the base territory (default USA).

• Age rating and category tools resolve the app's editable app info when given appId.

• Analytics flow: request → reports → instances → segments → download. Only one ONGOING request is allowed per app.

Development

git clone https://github.com/yunyang088/app-store-connect-mcp-server.git
cd app-store-connect-mcp-server
npm install
npm run build   # compile TypeScript to dist/
npm start       # run the server on stdio

License

MIT