Skip to main content
Glama

asc-mcp

A small, task-focused MCP server for App Store Connect, with support for several accounts in one server.

Generated App Store Connect MCP servers expose every API endpoint as its own tool, which comes to more than 1,000 tools per account. That bloats every session and makes it hard for the model to pick the right tool. This server exposes 13 tools built around everyday work, plus one escape hatch for everything else. It also returns flattened, trimmed responses instead of raw JSON:API documents.

Tools

Tool

What it does

list_accounts

Configured accounts, and whether sales reports are set up for each

list_apps

Apps (id, name, bundle ID, SKU) across one or all accounts

app_status

Recent versions with review/release state and attached build, recent review submissions, latest build

daily_report

Sales summary per app: downloads, updates, redownloads, IAPs, subscriptions, proceeds by currency, top countries. Covers daily (multi-day ranges too), weekly, monthly and yearly reports

reviews

Recent customer reviews with any developer response; filter by rating, territory, or unanswered

reply_to_review ✎

Publish or replace a developer response

testflight

Recent builds (build number, marketing version, processing and beta state) and beta groups

testflight_add_tester ✎

Invite a tester by email to a group, whether or not they already exist

testflight_distribute ✎

Add a build to a group; submits for Beta App Review when the group is external

submit_for_review ✎

Attach a build, then create or reuse a review submission and submit it

xcode_cloud_status

Workflows and recent build runs

xcode_cloud_start ✎

Start a workflow, optionally on a specific branch or tag

asc_request ✎

Any App Store Connect API call (GET runs immediately; other methods are confirm-gated)

✎ marks tools that change something. They return a preview unless called with confirm: true, so the assistant can show you what will happen before it happens.

Apps can be referred to by App Store ID, bundle ID, SKU, or name (a partial name works if it's unique). Pass account when more than one account is configured.

Related MCP server: App Store Connect MCP Server

Setup

Requires Node 20+.

git clone https://github.com/devandanger/asc-mcp.git
cd asc-mcp
npm install
npm run build

1. Create an API key for each account

In App Store Connect, go to Users and Access → Integrations → App Store Connect API. Create a key with the App Manager role (or Admin if you need user management), and download the .p8 file. Note the Issuer ID and Key ID.

For daily_report, also note your vendor number, found under Payments and Financial Reports (top left). The key needs the Finance, Sales, or Admin role to read sales reports.

2. Write the config

Create ~/.config/asc-mcp/config.json. You can point to a different path with the ASC_MCP_CONFIG environment variable.

{
  "accounts": {
    "acme": {
      "issuerId": "…",
      "keyId": "…",
      "privateKeyPath": "~/.app-store-connect-mcp/AuthKey_XXXXXXXXXX.p8",
      "vendorNumber": "8xxxxxxx"
    },
    "studio": {
      "issuerId": "…",
      "keyId": "…",
      "privateKeyPath": "~/.app-store-connect-mcp/AuthKey_YYYYYYYYYY.p8",
      "vendorNumber": "8yyyyyyy"
    }
  }
}

Lock the file down: chmod 600 ~/.config/asc-mcp/config.json. The .p8 keys stay wherever you keep them; the server reads them at startup and never copies them.

For a single account, you can skip the file and use environment variables instead: ASC_ISSUER_ID, ASC_KEY_ID, ASC_PRIVATE_KEY_PATH (or ASC_PRIVATE_KEY), ASC_VENDOR_NUMBER, and optionally ASC_ACCOUNT_NAME.

3. Add it to your MCP client

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "asc": {
      "command": "/absolute/path/to/node",
      "args": ["/Users/YOU/Developer/asc-mcp/dist/index.js"]
    }
  }
}

Use the full path that which node prints, because desktop apps don't see the PATH that nvm/Homebrew set up in your shell. Restart Claude Desktop afterwards.

Claude Code:

claude mcp add asc -- node /Users/YOU/Developer/asc-mcp/dist/index.js

If you're replacing per-account servers (for example one server per developer account), remove those entries once asc is working.

Development

npm test      # builds, then runs unit tests and an in-memory MCP round trip against a fake API

The code is small and laid out by concern:

  • src/auth.ts: ES256 JWT signing and caching (no JWT dependency)

  • src/client.ts: HTTP client with retry on 429, pagination, gzip, response flattening; refuses non-Apple hosts

  • src/salesReport.ts: Sales SUMMARY report parsing and per-app rollup

  • src/context.ts: account selection and app resolution

  • src/tools.ts: the tools

Security

  • Never commit config.json, .p8 files, or .env files. .gitignore already excludes them.

  • asc_request only calls api.appstoreconnect.apple.com.

  • Tools that change anything require confirm: true.

License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers