asc

asc-mcp is a Swift-based MCP server that acts as a bridge between Claude (or any MCP-compatible host) and the App Store Connect API. It exposes a comprehensive set of tools to automate the iOS/macOS release workflow, including multi-account management, full release pipelines (versions, builds, submission), TestFlight automation, build management, customer reviews, IAPs, subscriptions, provisioning, marketing assets, analytics, and metadata management. You can interact with the server through Claude Code integration, or via the CLI once the binary or container is running. The included configuration supports multiple companies and optional analytics data via vendor numbers. To get started, configure your App Store Connect API credentials, add one or more companies, and run the server. You can then invoke the 208 available MCP tools across 25 workers to perform typical release tasks, gather metrics, and automate repetitive processes.

Prerequisites:

• macOS 14.0+ (Sonoma)
• Swift 6.2+ (Xcode 16.0+ recommended for building)
• App Store Connect API Key (Key ID, Issuer ID, and private key)
• Optional: Claude integration setup for Claude Code access

Option A — Install via Mint (recommended):

brew install mint
mint install zelentsov-dev/asc-mcp@1.4.0

Option B — Build from source:

git clone https://github.com/zelentsov-dev/asc-mcp.git
cd asc-mcp
swift build -c release

If you build from source, you can register the binary with Claude Code similarly to the Mint path:

claude mcp add asc-mcp -- /path/to/.build/release/asc-mcp

Optional: Copy the built binary to a directory in your PATH for convenience:

cp .build/release/asc-mcp /usr/local/bin/asc-mcp

Configuration tips:

• Use the recommended environment-variable setup for MCP clients, especially ASC_KEY_ID, ASC_ISSUER_ID, and ASC_PRIVATE_KEY_PATH. For multi-account setups, define ASC_COMPANY_N_NAME/KEY_ID/ISSUER_ID/KEY_PATH pairs for each account (numbered from 1).
• The server also supports a JSON configuration file at ~/.config/asc-mcp/companies.json for multi-company setups; this is optional when using environment variables.
• Ensure your App Store Connect API key has the appropriate roles (Admin or App Manager recommended).
• When running in Docker, ensure the container has access to the private key file (mount volumes as needed) and that the environment variables are properly passed.
• If you encounter connectivity or authentication issues, verify that ASC_PRIVATE_KEY_PATH points to a valid .p8 file and that Key ID / Issuer ID match the key. Check that the vendor_number is configured if you plan to use analytics reports.