mcpField
A
app-store-connect-mcp

app-store-connect-mcp

Local
github.com/chrischallDeveloper Tools1Updated 2d ago

About app-store-connect-mcp

app-store-connect-mcp connects Claude to App Store Connect for app, TestFlight, review, sales, finance, and team-user operations. It includes confirmation steps for write actions and requires an App Store Connect API key.

Key features

  1. 01Browse apps and releases
  2. 02Manage builds and TestFlight testers
  3. 03Read and respond to reviews
  4. 04Download sales and finance reports
  5. 05View and invite team users
  6. 06Confirm write actions

Use cases

  1. 01Check recent app builds
  2. 02Invite or manage beta testers
  3. 03Review ratings and reply to customers
  4. 04Retrieve sales or finance reports

MCP support

Exposes App Store Connect operations as MCP tools for Claude. Write operations require confirmation before changes are sent.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"chrischall-app-store-connect": {
"command": "npx",
"args": [
"-y",
"@chrischall/app-store-connect-mcp"
],
"env": {
"APP_STORE_CONNECT_KEY_ID": "<APP_STORE_CONNECT_KEY_ID>",
"APP_STORE_CONNECT_ISSUER_ID": "<APP_STORE_CONNECT_ISSUER_ID>",
"APP_STORE_CONNECT_PRIVATE_KEY_PATH": "<APP_STORE_CONNECT_PRIVATE_KEY_PATH>",
"APP_STORE_CONNECT_PRIVATE_KEY": "<APP_STORE_CONNECT_PRIVATE_KEY>"
}
}
}
}
Run commandnpx -y @chrischall/app-store-connect-mcp
Environment variables to set
APP_STORE_CONNECT_KEY_IDSecret10-character App Store Connect API Key ID (e.g. ABC1234567).
APP_STORE_CONNECT_ISSUER_IDTeam Issuer ID (UUID) from App Store Connect → Users and Access → Integrations.
APP_STORE_CONNECT_PRIVATE_KEY_PATHSecretAbsolute path to your downloaded .p8 private key file. Either this or APP_STORE_CONNECT_PRIVATE_KEY is required.
APP_STORE_CONNECT_PRIVATE_KEYSecretPEM contents of your .p8 private key. Either this or APP_STORE_CONNECT_PRIVATE_KEY_PATH is required.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@chrischall/app-store-connect-mcp1.3.2

Tools

22

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
namestringNoExact app name filter
limitintegerNoMax apps to return (default 50). Without auto_paginate this is capped at one API page (200); with auto_paginate it is the total across pages.
bundleIdstringNoExact bundle ID filter (e.g. com.example.MyApp)
auto_paginatebooleanNoFollow links.next across pages until the limit is reached (default false). Check the pagination block in the result for has_more.

Details

From the project README

App Store Connect MCP

CI license

A Model Context Protocol server that connects Claude to App Store Connect, giving you natural-language access to your apps, builds, TestFlight beta groups and testers, customer reviews, sales/finance reports, and team users.

Warning

AI-developed project. This codebase was entirely built and is actively maintained by Claude Code. No human has audited the implementation. Review all code and tool permissions before use.

What you can do

Ask Claude things like:

  • "List my apps"
  • "Show me the latest builds for app 1234567890"
  • "Who hasn't accepted their TestFlight invitation?"
  • "Invite [email protected] to the External Beta group"
  • "Submit build 9876 for beta review"
  • "What's our average rating in Japan this month?"
  • "Respond to that 1-star review with an apology"
  • "Pull yesterday's daily sales report for vendor 80012345"
  • "Invite a new developer with App Manager role"

Requirements

Installation

Option A — npm
npx -y @chrischall/app-store-connect-mcp

Add to your Claude config (.mcp.json or Claude Desktop config):

{
  "mcpServers": {
    "app-store-connect": {
      "command": "npx",
      "args": ["-y", "@chrischall/app-store-connect-mcp"],
      "env": {
        "APP_STORE_CONNECT_KEY_ID": "ABC1234567",
        "APP_STORE_CONNECT_ISSUER_ID": "57246542-96fe-1a63-e053-0824d011072a",
        "APP_STORE_CONNECT_PRIVATE_KEY_PATH": "/absolute/path/to/AuthKey_ABC1234567.p8"
      }
    }
  }
}
Option B — from source
git clone https://github.com/chrischall/app-store-connect-mcp.git
cd app-store-connect-mcp
npm install
npm run build

Add to Claude Desktop config:

  • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "app-store-connect": {
      "command": "node",
      "args": ["/absolute/path/to/app-store-connect-mcp/dist/bundle.js"],
      "env": {
        "APP_STORE_CONNECT_KEY_ID": "ABC1234567",
        "APP_STORE_CONNECT_ISSUER_ID": "57246542-96fe-1a63-e053-0824d011072a",
        "APP_STORE_CONNECT_PRIVATE_KEY_PATH": "/absolute/path/to/AuthKey_ABC1234567.p8"
      }
    }
  }
}

Getting an API key

  1. Sign in at App Store Connect → Users and Access → Integrations → App Store Connect API.
  2. Click + to generate a key. Pick a role appropriate to what you want Claude to do — Developer is enough for read-only browsing; App Manager for TestFlight management; Admin for user invites and most write operations.
  3. Download the .p8 file (you can only download it once) and note the Key ID and Issuer ID.
  4. Either point APP_STORE_CONNECT_PRIVATE_KEY_PATH at the saved .p8, or paste the PEM contents into APP_STORE_CONNECT_PRIVATE_KEY (newline-escaped is fine).

The key signs short-lived (20-minute) ES256 JWTs on demand. No external token storage; nothing is sent to anyone but Apple.

Tools

ToolWhat it does
list_appsList apps in your account (filter by bundleId/name)
get_appGet a single app by ID
list_app_store_versionsList App Store releases for an app
get_app_infosAge rating and store-state info for an app
list_buildsRecent builds (newest first), filter by app/state/version
get_buildSingle build details
list_beta_groupsTestFlight internal/external beta groups
list_beta_testersBeta testers, filter by app/group/email
invite_beta_testerAdd a new tester, optionally to groups/builds
delete_beta_testerRemove a tester from your team
add_testers_to_beta_groupAdd existing testers to a group
remove_testers_from_beta_groupRemove testers from a group
submit_build_for_beta_reviewSend a build for TestFlight beta review
list_customer_reviewsApp Store reviews, filter by rating/territory
get_customer_reviewSingle review with developer response
respond_to_reviewPost or update a developer reply
download_sales_reportDaily/weekly/monthly/yearly units & sales TSV
download_finance_reportRegion finance/proceeds TSV; Total_* trailer lines in a separate summary
list_usersApp Store Connect team users
list_user_invitationsPending team invitations
invite_userInvite a new team member with roles; app visibility is explicit (allAppsVisible: true or a non-empty visibleAppIds, no all-apps default)
asc_healthcheckVerify credentials and upstream reachability; reports failures as data, not exceptions

Environment

VariableRequiredNotes
APP_STORE_CONNECT_KEY_IDyes10-character Key ID (e.g. ABC1234567)
APP_STORE_CONNECT_ISSUER_IDyesTeam Issuer ID (UUID)
APP_STORE_CONNECT_PRIVATE_KEYone ofFull PEM contents of your .p8. Newline-escapes (\n) are accepted.
APP_STORE_CONNECT_PRIVATE_KEY_PATHone ofAbsolute path to the .p8 file

Confirmations

Every write (invite_beta_tester, delete_beta_tester, add_testers_to_beta_group, remove_testers_from_beta_group, submit_build_for_beta_review, respond_to_review, invite_user) asks you to confirm before anything is sent. A client that can show a confirmation prompt (Claude Code) shows one with the exact request. On a client that cannot, the first call sends nothing and returns a preview — method, path and the JSON body it will send — plus a confirmToken; only a repeat call with the same arguments and that token performs the write. A token is single-use, expires, and is refused if any argument changed since the preview.

variabledefault
MCP_CONFIRM_MODEask-userWhat a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). ask-user: two steps — the first call does nothing and returns a preview plus a token, and the model must get your approval in chat before calling again with it. auto: the same two steps, but the model may use the token after reviewing the preview itself. refuse: writes are refused on such clients. A client that can show prompts (Claude Code) always gets the real prompt, unless MCP_CONFIRM_ELICITATION=off. An unrecognised value is treated as refuse.
MCP_CONFIRM_ELICITATIONonoff never sends a confirmation prompt, so every client gets the MCP_CONFIRM_MODE path. Set it for a client that declares it can show prompts but never does (the gated call hangs — opencode 2.0.x). Any other value stays on, with a stderr warning.
MCP_CONFIRM_TTL_SECONDS600How long a token stays valid.
MCP_CONFIRM_SECRETrandom per processSigning key; set it only if tokens must survive a server restart.

Development

npm install
npm test               # vitest run
npm run test:watch     # watch mode
npm run build          # tsc + esbuild bundle
npm run dev            # node --env-file=.env dist/index.js

Tests mock client.request / client.requestRaw; no real App Store Connect calls are made.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.