Log inSubmit server
Asc MCP logo

Asc MCP

Automates App Store Connect metadata, screenshots, builds, TestFlight, review submission, release, and reporting through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Asc MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "asc-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "@pofky/asc-mcp"
      ],
      "env": {
        "ASC_ISSUER_ID": "YOUR_VALUE_HERE",
        "ASC_KEY_ID": "YOUR_VALUE_HERE",
        "ASC_PRIVATE_KEY_PATH": "YOUR_VALUE_HERE",
        "ASC_LICENSE_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The asc-mcp MCP server connects an AI agent to App Store Connect for app releases, metadata, screenshots, builds, TestFlight, reviews, sales reports, and release actions. It uses an App Store Connect API key with an Issuer ID and exposes opinionated tools for common workflows rather than raw API endpoints. Reach for it when you want an agent to check release readiness, update store content, attach a processed build, or submit and release an app. It also includes setup checks, an in-agent guide, review analysis, and release-note support.

Use cases

  • Audit an app before App Review submission
  • Update localized App Store metadata and screenshots
  • Attach a processed build and submit a release
  • Manage TestFlight groups and external testers
  • Summarize reviews, sales, and release status

Key features

  • App Store Connect release automation
  • Metadata and screenshot management
  • Build processing and attachment
  • TestFlight group and tester management
  • Review, sales, keyword, and competitor analysis
  • Pre-submission audits and release briefings

Tools41

What Asc MCP lets your agent do. Expand a tool for its parameters.

Self-reported~1.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

6/6 checks healthy over the last 51d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11h ago via OSV.dev · @pofky/asc-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.6kPackage downloads in the last 30 days.
Last commit10d agoMost recent push to the default branch.
Tools exposed41Callable tools this server registers over MCP.

How Asc MCP works

What asc-mcp MCP server does

The asc-mcp MCP server gives an AI agent access to App Store Connect workflows through 41 MCP tools. It can list apps, inspect version and review status, edit store metadata, upload screenshots, manage builds, operate TestFlight groups, set app pricing and metadata, submit versions for review, release approved versions, and manage phased releases.

The server also includes read and analysis features. Agents can retrieve reviews and sales reports, compare live and pending metadata, inspect competitors, analyze keywords, generate release notes from Git commits since the last tag, and produce a daily briefing across apps. A release preflight checks metadata, character limits, screenshots, and build status before submission.

Two review-oriented tools use MCP Sampling: one clusters recent reviews into themes, and another drafts a response in the review’s locale. Drafted responses are not posted automatically.

How it works

Authentication uses an App Store Connect API key, its Issuer ID, and a downloaded .p8 private-key file. The server communicates with App Store Connect through the API, so building and signing the binary remains a separate Mac-side task. Once a build is processed, the agent can wait for it, attach it to an editable version, and continue with submission or release.

The asc-mcp MCP server organizes common release operations into higher-level tools. For example, an agent can create an editable version, validate and update metadata, upload screenshots with checksums, attach a valid build, and submit it. Submission and public release require an explicit confirmation value. The asc_guide tool provides flow-specific instructions and identifies steps that still require the App Store Connect website.

Setup and configuration

Create an App Store Connect API key with the Admin or App Manager role, then obtain the Issuer ID, Key ID, and .p8 file. The recommended setup places the key at ~/.appstoreconnect/private_keys/AuthKey_XXXXXXXXXX.p8. In that arrangement, the Issuer ID is the only required environment value because the Key ID and key path can be detected.

Install with npm or run it through npx:

Terminal
npm install -g @pofky/asc-mcp
npx @pofky/asc-mcp init --write

The initialization command can find the key, request the Issuer ID, back up and update supported client configuration, and write the MCP server block. For non-interactive use, pass --issuer; --config, --key-path, --key-id, and --license are also available. The server can be added manually to an MCP configuration using npx -y @pofky/asc-mcp.

Run npx @pofky/asc-mcp doctor or call asc_setup_check to test credentials, the live App Store Connect connection, and license status.

Tools and capabilities

  • Inspect apps, versions, builds, review status, customer reviews, and sales by territory.
  • Edit descriptions, keywords, promotional text, URLs, app names, subtitles, and release notes with character-limit validation.
  • Upload screenshots, wait for build processing, and attach a processed build.
  • Manage TestFlight groups, beta assignments, and external tester invitations.
  • Set categories, copyright, content rights, export compliance, and base pricing.
  • Submit versions, release approved versions, and control seven-day phased rollouts.
  • Audit releases and summarize reviews, keywords, competitors, metadata differences, and Git-based release notes.

Limitations and notes

The README identifies Claude Desktop, Claude Code, Cursor, Windsurf, and Cline as supported clients. The service has a seven-day trial followed by a stated $9 monthly Pro price; some tools remain free, while certain read-only Pro tools have limited preview usage without a license. The .p8 key can only be downloaded once from Apple, so it must be stored securely. Building and signing the binary is not performed by the server and still requires a Mac-side process.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Asc MCP

asc-mcp is an MCP server that connects AI agents to App Store Connect. Its main tools manage app metadata, screenshots, builds, TestFlight groups, reviews, sales reports, submissions, releases, and phased rollouts. It authenticates with an App Store Connect API key, Issuer ID, and .p8 private key.

Install it with npm or run `npx @pofky/asc-mcp init --write`. The initializer detects a standard `.p8` key location, asks for the Issuer ID, and can write the MCP configuration. Manual configuration with `npx -y @pofky/asc-mcp` is also supported.

Yes, asc-mcp works with Cursor. The README also names Claude Desktop, Claude Code, Windsurf, and Cline. Use `npx @pofky/asc-mcp init --write` to create or update supported client configuration, or add the server manually to Cursor’s MCP settings.

Run `npx @pofky/asc-mcp doctor` or call `asc_setup_check`. It checks the API key, Issuer ID, live App Store Connect connectivity, and license tier, then reports a specific fix for detected failures.

Yes, asc-mcp can submit a version for App Review and release an approved version, but both actions require `confirm: true`. The server does not build or sign the binary; that step still requires a Mac-side process.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAsc MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/asc-mcp-2?style=directory)](https://allmcps.com/mcp/asc-mcp-2)
HTML Embed
<a href="https://allmcps.com/mcp/asc-mcp-2"><img src="https://allmcps.com/api/badge/asc-mcp-2?style=directory" alt="Asc MCP on AllMCPs" /></a>