ActivationPal

App Store Connect MCP Servers

The best App Store Connect MCP server to start with is RayanBayat's app-store-connect: it reads your apps, builds, TestFlight testers and reviews, and sends nothing until you approve each change. All of these servers wrap Apple's App Store Connect API, which authorizes requests with API keys that sign JWTs.

ServerBest forCoversPrice
RayanBayat/app-store-connectApproving every change yourselfApps, builds, TestFlight, listings, screenshots, reviewsFree
swlittles/app-store-connect-mcpShipping TestFlight builds in one callTestFlight, listing, screenshots, subscriptions, reviews, sales reportsFree
erayendes/app-store-connect-mcpPricing, subscriptions and review triageApp Store Connect, TestFlight, StoreKit 2Free
zelentsov-dev/asc-mcpSwift server with tools across 34 App Store domainsApps, builds, TestFlight, subscriptions, Xcode CloudFree
TrialAndErrorAI/appstore-connect-mcpA short tool list in the agent's context923 endpoints through 2 toolsFree
ryaker/appstore-connect-mcpSales reports and review analysisTestFlight, reviews, metadata, sales reportsFree
mikusnuz/app-publish-mcpOne app on iOS and AndroidApp Store Connect and Google Play, 91 toolsFree
tunaarikaya/magaza-mcpComparing both stores in one questionApp Store Connect and Google Play, 41 toolsFree

1. RayanBayat/app-store-connect

Best for: teams that want an agent to read store data and approve every edit.

It reads apps, builds, TestFlight testers, localized store texts, screenshots and customer reviews through Apple's official API. Changes are off until you turn them on. Each change then shows the old and new values, and nothing is sent until you press Accept. Every 30 days its tools pause until you have read a short maintenance report. MIT licensed.

2. swlittles/app-store-connect-mcp

Best for: shipping TestFlight builds and editing listings with few tool calls.

Its tools are workflows rather than single endpoints, so "ship this build to these groups with these notes" is one call. It covers TestFlight builds and testers, the store listing, screenshots, subscriptions, App Review submission, customer reviews and sales reports. It is read-only until you set ASC_WRITE=1, and destructive actions stay a dry run until confirmed.

3. erayendes/app-store-connect-mcp

Best for: managing pricing, subscriptions and submissions across many countries.

Called Heimdall, it runs App Store Connect, TestFlight and StoreKit 2 from your AI with 786 tools in 14 profiles, generated from Apple's OpenAPI spec. It handles worldwide pricing, offers, subscriptions, submissions and review triage. Writes are confirmed before they run, a read-only mode is available, and it runs locally through npx.

4. zelentsov-dev/asc-mcp

Best for: macOS teams that want a Swift server with tools across 34 App Store domains.

A local server for macOS MCP clients with more than 500 tools across apps, builds, TestFlight, reviews, subscriptions and Xcode Cloud. Its README includes configuration examples for Codex, Claude Code, Claude Desktop, Gemini CLI, VS Code with GitHub Copilot, Continue and Cursor.

5. TrialAndErrorAI/appstore-connect-mcp

Best for: keeping the agent's context small.

Instead of one tool per endpoint, it exposes two. search queries Apple's OpenAPI spec, and execute calls the API with JavaScript the model writes. That reaches 923 endpoints with about 1K tokens of tool definitions, against roughly 100K for one tool per endpoint, by its README's count. Its quick start asks for an Admin or Finance role key.

6. ryaker/appstore-connect-mcp

Best for: pulling sales reports and reading customer reviews from Claude Desktop, Cursor, Windsurf or VS Code.

It connects those clients to the App Store Connect API to automate TestFlight builds, analyze customer reviews, update app metadata and fetch sales reports. The quickstart runs through npx, with the key ID, issuer ID and private key passed as environment variables in the client's MCP config.

7. mikusnuz/app-publish-mcp

Best for: teams that ship the same app on iOS and Android.

One server for App Store Connect and Google Play Console, with 91 tools for listings, screenshots, releases, reviews and submissions. You supply a signed .aab, .apk or .ipa. The server handles the store-side work from upload through metadata, testing, review submission and release, so one agent session covers both stores.

8. tunaarikaya/magaza-mcp

Best for: answering questions that span both stores, such as a subscription price in each.

It combines App Store Connect and Google Play in one MCP server with 41 tools, plus access to the full API of 1,440 operations in about 9,000 tokens. No server sits in the middle: the package runs on your machine, talks directly to Apple and Google, and keeps your keys in your Keychain.

How to connect an App Store Connect MCP server

Every server above needs an App Store Connect API key. Apple's steps:

  1. The Account Holder requests API access. In App Store Connect, open Users and Access, click Integrations, click Request Access, accept the terms and click Submit. Apple reviews each request.
  2. The Account Holder or an Admin opens Integrations, then Team Keys, then Generate API Key. Enter a name for your own reference, pick the role under Access and click Generate.
  3. Download the key file and note the key's ID and the issuer ID. The READMEs of RayanBayat's server and TrialAndErrorAI's both ask for these, and say the file can be downloaded only once.
  4. Add the server to your agent as its README describes. For Claude Code, the MCP docs cover adding a server.

Without Account Holder or Admin rights, you can generate a key for your own use instead. Each user can have one active key at a time.

Read-only or read and write

The role you pick in step 2 sets what any server can do with the key, whatever the server's own switches say. Apple states the role permissions determine what the API can be used for.

Servers differ on top of that. RayanBayat's is read-only by default and asks you to approve each change. swlittles' stays read-only until ASC_WRITE=1, and Heimdall has a read-only mode. The others list management tools for builds, testers, metadata or pricing, so give them a key with a role that matches what you want the agent to do.

What App Store Connect data does not show

These servers return store data: sales, analytics, finance, reviews, builds and listings. It ends where the install begins. Your own app events, such as which onboarding step users leave on or which plan they pick on the paywall, are not store data.

For that side, this site makes ActivationPal, which has its own MCP server on every plan. Its agent keys are read-only, and it works with Claude Code, Codex, Cursor, OpenCode and Windsurf. See onboarding analytics for the funnel it reads, iOS app analytics for the setup, or the agent API docs. For keyword and ranking data rather than your own account, see the best ASO tools.

Frequently asked questions

Who can create an App Store Connect API key?

The Account Holder first requests API access. After that, the Account Holder or an Admin can generate team keys. By default, every App Store Connect user can also generate and revoke a key for individual use, unless an Admin or Account Holder has removed that ability.

Can I limit an API key to one app?

Not with a team key. Team keys apply across all apps in the account, so app access cannot be limited. A key's name and access level cannot be edited after you generate it. To change either one, revoke the key and generate a new one.

What is MCP, and is it safe to connect a server?

MCP, the Model Context Protocol, is an open-source standard for connecting AI applications to external systems. Claude Code's docs advise verifying that you trust each server before connecting it, since servers that fetch external content can expose you to prompt injection. Read a server's source before giving it a key.