zelentsov-dev/asc-mcp

A local Model Context Protocol server for the App Store Connect API.
Manage apps, builds, TestFlight, reviews, and more from Codex, Claude, and other MCP clients on macOS.
---
Overview
**asc-mcp** is a Swift-based MCP server that connects a local macOS MCP client to the App Store Connect API. It exposes **502 tools** across 33 App Store tool domains + 2 core domains, enabling you to automate iOS and macOS release workflows through natural language.
Configuration examples are included for Codex, Claude Code, Claude Desktop, Gemini CLI, VS Code with GitHub Copilot, Continue, Cursor, and Devin Desktop (formerly Windsurf). Client configuration is documented; release CI verifies installation, MCP initialization, and tool discovery on macOS rather than launching every third-party client.
New here? Follow the Quick Start. The remaining sections are reference material for advanced configuration, tool selection, and contributors.
Key capabilities
- **Release and metadata** — versions, localizations, builds, review submissions, phased rollout, and Xcode Cloud
- **TestFlight and uploads** — beta groups, testers, feedback, recruitment, build delivery, processing, and export compliance
- **Monetization** — in-app purchases, subscriptions, pricing, availability, offer codes, and promotional offers
- **Marketing** — screenshots, previews, custom product pages, product page optimization, and promoted purchases
- **Accounts and provisioning** — multiple App Store Connect teams, users, bundle IDs, devices, certificates, profiles, and capabilities
- **Feedback and operations** — customer reviews, webhooks, accessibility declarations, analytics, metrics, and diagnostics
- **Safer automation** — read-only mode, confirmation safeguards, strict pagination, and mutation recovery guidance
- **Auditable API coverage** — a versioned Apple OpenAPI contract and release-time drift checks
Platform Support
asc-mcp is a local stdio server: the MCP client starts it on the same computer. A client being available on Linux or Windows does not make this Swift server cross-platform.
| Environment | Status | Notes |
|---|---|---|
| macOS 15.6+ with Xcode 26.x | **Recommended** | Release CI specifically uses GitHub's macOS 15 runner with Xcode 26.2 |
| macOS 14.0-15.5 | Declared deployment target only | Build and runtime are unverified; a separately installed Swift 6.2+ toolchain may be needed |
| Linux | Not supported yet | Porting work and Linux CI are not complete |
| Windows | Not supported | Current source dependencies and Swift MCP stdio transport are not Windows-compatible |
See Apple's Xcode system requirements for the macOS versions supported by each Xcode release.
Web and cloud sessions do not automatically inherit a local MCP configuration. Run the MCP client locally on a compatible Mac, or use a client feature that explicitly keeps execution on that Mac.
Quick Start
The recommended setup stores App Store Connect credentials once in a private local file. MCP clients then need only the path to the asc-mcp executable.
1. Install asc-mcp
2. Create an App Store Connect API key
1. Open App Store Connect → Users and Access → Integrations → Team Keys.
2. Generate a key with the least-privileged role that covers your workflow. App Manager or Admin is needed only when the corresponding operations require it.
3. Download the .p8 file. Apple allows it to be downloaded only once.
4. Copy the Key ID and Issuer ID.
3. Save the credentials locally
Create private configuration directories, then move the downloaded .p8 file into ~/.keys/. Replace the source path and filename in the second command:
Create ~/.config/asc-mcp/companies.json:
Replace /Users/you with your actual home-directory path. Keep both files outside the repository and restrict access:
> [!CAUTION]
> Never commit companies.json, a .p8 key, or raw credentials to Git. Revoke the App Store Connect key immediately if it is exposed.
4. Connect your MCP client
Choose one client. You do not need to configure every client.
**Codex**
**Claude Code**
For Claude Desktop, Gemini CLI, VS Code, Continue, Cursor, and Devin Desktop, use the ready-to-copy examples in MCP Client Setup.
5. Try it
Restart a GUI client after changing its configuration, open its MCP tool list, and ask:
If the connection or request fails, see Troubleshooting.
Installation
Mint on macOS (recommended)
Mint installs the pinned release from source and keeps the executable at ~/.mint/bin/asc-mcp.
Update or reinstall the pinned release:
Stable users should install a version tag. Installing main or develop is intended only for maintainers and pre-release testing.