apple-asc-mcp lets Claude drive App Store Connect releases via MCP
u/waruna_ds built `apple-asc-mcp`, an MCP server that lets Claude (or any MCP-compatible agent) handle App Store Connect tasks — metadata, screenshots, submission, IAPs, and TestFlight — via natural-language commands.
Score breakdown
The tool replaces the manual, multi-step App Store Connect workflow with a single conversational interface, allowing MCP-compatible AI agents to drive an entire release end-to-end against the live Apple API.
- 01Built by u/waruna_ds, mostly with Claude, and released as MIT-licensed open source on GitHub.
- 02Connects to Claude Code, Cursor, Codex, or any MCP-compatible agent via the Model Context Protocol.
- 03Accepts natural-language commands to run the full App Store release pipeline: xcodebuild → upload → metadata → screenshots → submit.
u/waruna_ds published `apple-asc-mcp`, an MCP server built mostly with Claude that wraps Apple's App Store Connect API in a conversational interface. Once wired into Claude Code, Cursor, Codex, or any other MCP-compatible agent, a developer can describe a release in plain language — for example, "create version 1.4.0 on the latest build, set the en-US what's new, upload the screenshots in ~/screens, submit for review" — and the tool executes the full sequence: `xcodebuild`, upload, metadata, screenshots, and submission. Beyond the core release flow, it also covers TestFlight, in-app purchases, subscriptions, pricing, and review management.
The author also explicitly recommends that teams already using fastlane in CI stick with it, positioning `apple-asc-mcp` specifically for the conversational "drive a release" loop rather than as a fastlane replacement.
The post is candid about the project's maturity. The core release and monetization functionality — authentication, metadata, screenshots, pricing, and the full IAP/subscription flows — has been tested against a real App Store Connect app and live Apple traffic. However, further-out features such as webhooks, Xcode Cloud, reporting, Game Center, and A/B experiments match Apple's spec but have not yet been run against the live API; the author advises pinning your version and expecting some API shapes to shift. The author also explicitly recommends that teams already using fastlane in CI stick with it, positioning `apple-asc-mcp` specifically for the conversational "drive a release" loop rather than as a fastlane replacement. The tool is MIT-licensed, installable via `npm install -g apple-asc-mcp`, and ships with an `apple-asc-mcp --diagnose` command to verify API key setup.
Key facts
- 01Built by u/waruna_ds, mostly with Claude, and released as MIT-licensed open source on GitHub.
- 02Connects to Claude Code, Cursor, Codex, or any MCP-compatible agent via the Model Context Protocol.
- 03Accepts natural-language commands to run the full App Store release pipeline: xcodebuild → upload → metadata → screenshots → submit.
- 04Also covers TestFlight, in-app purchases, subscriptions, pricing, and review management.
- 05Core release and monetization flows are tested against live Apple App Store Connect traffic.
- 06Experimental features (webhooks, Xcode Cloud, Game Center, A/B experiments) match Apple's spec but are not yet validated against the live API.
- 07Install via `npm install -g apple-asc-mcp`; run `apple-asc-mcp --diagnose` to check API key setup.
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Jun 9, 2026 · 17:05 UTC. How this works →