Log inSubmit server
App Store Connect MCP logo

App Store Connect MCP

Manage App Store Connect apps, TestFlight, reviews, reports, and team access through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install App Store Connect MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "app-store-connect-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/app-store-connect-mcp"
      ],
      "env": {
        "APP_STORE_CONNECT_KEY_ID": "YOUR_VALUE_HERE",
        "APP_STORE_CONNECT_ISSUER_ID": "YOUR_VALUE_HERE",
        "APP_STORE_CONNECT_PRIVATE_KEY": "YOUR_VALUE_HERE",
        "APP_STORE_CONNECT_PRIVATE_KEY_PATH": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

app-store-connect-mcp connects MCP clients to Apple App Store Connect for app, build, TestFlight, review, reporting, and team-user operations. It authenticates with an App Store Connect API key and signs short-lived ES256 JWTs locally for Apple API requests. Read tools cover account data and reports, while write tools require confirmation before changes are submitted. Reach for it when an agent needs to inspect or manage App Store Connect without building a separate API client.

Use cases

  • List recent builds for an app
  • Manage TestFlight testers and beta groups
  • Review customer feedback by rating or territory
  • Download sales and finance reports
  • Invite App Store Connect team members

Key features

  • App, release, and build inspection
  • TestFlight tester and beta-group management
  • Customer review retrieval and responses
  • Sales and finance report downloads
  • Team user and invitation management
  • Confirmation-gated write operations

Tools22

What App Store Connect MCP lets your agent do. Expand a tool for its parameters.

Self-reported~343 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 44d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @chrischall/app-store-connect-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.4kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Tools exposed22Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How App Store Connect MCP works

What app-store-connect-mcp does

app-store-connect-mcp exposes App Store Connect operations as Model Context Protocol tools. It covers app discovery, release metadata, build status, TestFlight groups and testers, customer reviews, sales and finance reports, and team users. Agents can use it to answer questions such as which builds are available, who belongs to a beta group, how an app is rated in a territory, or which team invitations remain pending.

The server also supports selected write operations. It can invite or remove TestFlight testers, modify beta-group membership, submit builds for beta review, publish review responses, and invite team members with explicit role and app-visibility settings.

How it works

The server runs as a local MCP process, commonly through npx or a built Node.js bundle. It uses an App Store Connect API key consisting of a Key ID, Issuer ID, and .p8 private key. The private key can be loaded from a file or supplied as PEM content. Short-lived ES256 JWTs are generated when requests are made, without external token storage.

Before performing a write, the server uses a confirmation flow. Clients with confirmation-prompt support can display the exact request. Other clients receive a preview containing the method, path, request body, and a single-use confirmation token; the operation proceeds only after a matching follow-up call. Confirmation behavior can be adjusted with environment variables.

Setup and configuration

Node.js 22 or later is required. Install with the npm package through npx, or clone the repository, run npm install, build it, and point an MCP client at the generated bundle. Claude Desktop and Claude Code are documented client options.

Set these authentication variables:

  • APP_STORE_CONNECT_KEY_ID
  • APP_STORE_CONNECT_ISSUER_ID
  • Either APP_STORE_CONNECT_PRIVATE_KEY_PATH or APP_STORE_CONNECT_PRIVATE_KEY

The API key must have permissions appropriate to the requested operations. Developer access is described as sufficient for read-only browsing, while App Manager access covers TestFlight management and Admin access is used for user invitations and many write operations. A .p8 file can only be downloaded once from App Store Connect, so it should be stored securely.

Optional confirmation controls include MCP_CONFIRM_MODE, MCP_CONFIRM_ELICITATION, MCP_CONFIRM_TTL_SECONDS, and MCP_CONFIRM_SECRET. The latter is useful when confirmation tokens need to remain valid across a process restart.

Tools and capabilities

App and build inspection includes list_apps, get_app, list_app_store_versions, get_app_infos, list_builds, and get_build. Build and app lists support filters such as bundle ID, name, state, or version where applicable.

TestFlight operations include listing beta groups and testers, inviting and deleting testers, changing group membership, and submitting a build for beta review. Review tools list or retrieve customer reviews and post or update developer responses, with rating and territory filtering available when listing reviews.

Reporting tools download sales data by day, week, month, or year and retrieve regional finance and proceeds data in TSV form. Team administration includes listing users, viewing pending invitations, and inviting users with roles and explicit app visibility. asc_healthcheck checks credentials and upstream reachability while returning failures as data.

Limitations and notes

Write access depends on the App Store Connect role assigned to the API key. Every write operation is confirmation-gated, including tester changes, beta-review submissions, review responses, and team invitations.

The project states that its code was produced and maintained by Claude Code and has not received a human audit. Review the implementation and requested tool permissions before using it with production App Store Connect accounts. Tests mock request methods rather than making live App Store Connect calls.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about App Store Connect MCP

app-store-connect-mcp is an MCP server that connects AI clients to Apple App Store Connect. Its main tools inspect apps, releases, builds, TestFlight groups and testers, customer reviews, sales and finance reports, and team users, while also supporting confirmed write operations such as invitations, review responses, and beta-review submissions.

Install it with `npx -y @chrischall/app-store-connect-mcp`, then add that command to your MCP client configuration. You can also clone the repository, run `npm install`, build it, and configure the client to run the generated Node.js bundle. Node.js 22 or later is required.

It needs an App Store Connect API Key ID, Issuer ID, and private key. Set `APP_STORE_CONNECT_KEY_ID` and `APP_STORE_CONNECT_ISSUER_ID`, then provide either `APP_STORE_CONNECT_PRIVATE_KEY_PATH` for a `.p8` file or `APP_STORE_CONNECT_PRIVATE_KEY` for PEM contents.

Yes. It runs as a standard local MCP process, so it can be configured in Cursor using the same command and environment variables used for other stdio MCP servers. The documented setup specifically covers Claude Desktop and Claude Code.

It requires confirmation before every supported write. Depending on the client, it either displays a confirmation prompt or returns a preview and single-use token that must be supplied in a matching follow-up call. The confirmation mode, token lifetime, and prompt behavior are configurable.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewApp Store Connect MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/app-store-connect-mcp-2?style=directory)](https://allmcps.com/mcp/app-store-connect-mcp-2)
HTML Embed
<a href="https://allmcps.com/mcp/app-store-connect-mcp-2"><img src="https://allmcps.com/api/badge/app-store-connect-mcp-2?style=directory" alt="App Store Connect MCP on AllMCPs" /></a>