asc-mcp
Provides tools for interacting with the App Store Connect API, including listing apps and account status, retrieving app review/release state and build info, generating sales reports, reading and replying to customer reviews, managing TestFlight testers and builds, submitting app versions for review, and making arbitrary App Store Connect API requests with confirmation gating.
Provides tools for Xcode Cloud workflows and recent build runs, including starting a workflow optionally on a specific branch or tag.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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 |
| Configured accounts, and whether sales reports are set up for each |
| Apps (id, name, bundle ID, SKU) across one or all accounts |
| Recent versions with review/release state and attached build, recent review submissions, latest build |
| 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 |
| Recent customer reviews with any developer response; filter by rating, territory, or unanswered |
| Publish or replace a developer response |
| Recent builds (build number, marketing version, processing and beta state) and beta groups |
| Invite a tester by email to a group, whether or not they already exist |
| Add a build to a group; submits for Beta App Review when the group is external |
| Attach a build, then create or reuse a review submission and submit it |
| Workflows and recent build runs |
| Start a workflow, optionally on a specific branch or tag |
| 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 build1. 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.jsIf 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 APIThe 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 hostssrc/salesReport.ts: Sales SUMMARY report parsing and per-app rollupsrc/context.ts: account selection and app resolutionsrc/tools.ts: the tools
Security
Never commit
config.json,.p8files, or.envfiles..gitignorealready excludes them.asc_requestonly callsapi.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…
This server cannot be deployed
Maintenance
Related MCP Connectors
Run App Store Connect from your IDE: pricing, listings, screenshots, releases, AI visibility.
App Store Connect operator for AI agents: icons, TestFlight builds, listings, IAP, rejection fixes.
Create App Store screenshots, app icons and store copy, then push them to App Store Connect.
Ship apps for iPhone, iPad, Mac, Apple TV, Vision Pro and Android to the App Store and Google Play
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables interaction with Apple's App Store Connect API through natural language to manage apps, beta testing, localizations, analytics, sales reports, and CI/CD workflows for iOS and macOS development.31115 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables analysis and management of iOS/macOS apps via the App Store Connect API, including app management, reviews, sales reports, analytics, performance metrics, and TestFlight.17 npm2MIT
- AlicenseCqualityDmaintenanceEnables management of App Store Connect resources including app reviews, TestFlight crashes, analytics reports, and Xcode Cloud workflows through natural language or AI agents.401MIT
- AlicenseNot gradedqualityDmaintenanceEnables management of iOS/macOS apps, TestFlight builds, app metadata, analytics, and more through natural language interactions with Apple Store Connect API.47 npm60MIT