App Store Connect MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@App Store Connect MCP ServerPrepare version 2.1.0 for my app and show release status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
App Store Connect MCP Server
Automate App Store Connect from your AI agent.
Overview
This MCP server lets AI agents like Claude Code, Claude Desktop, and Cursor manage your App Store Connect workflows through natural language. Create versions, update metadata, attach builds, and submit for review — all without leaving your editor.
Built in Swift with the MCP Swift SDK, it connects directly to the App Store Connect REST API using ES256 JWT authentication.
Related MCP server: App Store Connect MCP
Key Features
Release workflows — Prepare releases, check status, validate before submission, and clone metadata between versions
Version management — Create, update, and list App Store versions
Localized metadata — Add descriptions, keywords, release notes, and URLs for any locale
Build management — List builds, upload IPAs, and attach builds to versions
Diagnostics & performance — View diagnostic signatures, logs, and performance metrics per build
Review and publication — Submit versions to App Review and manually release approved versions
Multi-organization — Manage multiple App Store Connect teams from a single server
Secure auth — ES256 JWT signing via Apple CryptoKit with automatic token refresh
Build From Source (Setup)
Use this path if you want to work on or build this repository locally.
Prerequisites
macOS 13+, Swift 6.0+ / Xcode 16+
Tuist 4.x (
brew install tuist)An App Store Connect API key with App Manager role or higher
Install and Build
./bootstrap.shThis fetches dependencies, generates the Xcode project, and builds. Or manually:
tuist install && tuist generate && tuist buildConfigure
Choose the configuration that matches your App Store Connect API key.
Team API Key
Team keys require the issuer ID. ASC_AUTH_MODE defaults to team, but setting it
explicitly makes the configuration clear:
export ASC_KEY_ID="your-key-id"
export ASC_PRIVATE_KEY_PATH="/path/to/AuthKey_XXXXXX.p8"
export ASC_ISSUER_ID="your-issuer-id"
export ASC_AUTH_MODE="team"Individual API Key
Individual keys do not use an issuer ID. Set ASC_AUTH_MODE to individual and
omit ASC_ISSUER_ID:
export ASC_KEY_ID="your-key-id"
export ASC_PRIVATE_KEY_PATH="/path/to/AuthKey_XXXXXX.p8"
export ASC_AUTH_MODE="individual"Get these values from App Store Connect > Users and Access > Integrations > App Store Connect API.
Install via npm
Use this path if you only want to run the MCP server and not build from source.
Prerequisites
Node.js 18+ and npm
macOS
Install/Run Command
npx -y @vvlladd/appstoreconnect-mcpConnect to Claude Code
Add one of the following configurations to ~/.claude.json (global) or
.claude/settings.json (project) and use the npm package.
For a team API key:
{
"mcpServers": {
"appstoreconnect": {
"command": "npx",
"args": ["-y", "@vvlladd/appstoreconnect-mcp"],
"env": {
"ASC_KEY_ID": "your-key-id",
"ASC_PRIVATE_KEY_PATH": "/path/to/AuthKey.p8",
"ASC_ISSUER_ID": "your-issuer-id",
"ASC_AUTH_MODE": "team"
}
}
}
}For an individual API key:
{
"mcpServers": {
"appstoreconnect": {
"command": "npx",
"args": ["-y", "@vvlladd/appstoreconnect-mcp"],
"env": {
"ASC_KEY_ID": "your-key-id",
"ASC_PRIVATE_KEY_PATH": "/path/to/AuthKey.p8",
"ASC_AUTH_MODE": "individual"
}
}
}
}Then ask your agent something like:
"Prepare version 2.1.0 for my app, validate it's ready for submission, and show me the full release status."
Available Tools
Tool | Description | Key Parameters |
Release Workflows | ||
| Check readiness, create version, attach build, sync metadata, configure rollout |
|
| Full status overview: state, build, localizations, release type, rollout |
|
| Pre-submit checklist with pass/fail for each requirement |
|
| Copy all localizations from one version to another |
|
Version Management | ||
| List all apps in your account | — |
| Create a new App Store version |
|
| List existing versions for an app |
|
| Update version attributes |
|
| Choose a 7-day phased rollout or instant rollout to all users |
|
| Add/update localized metadata |
|
Build Management | ||
| List available builds |
|
| Upload an IPA to App Store Connect |
|
| Attach a build to a version |
|
Review | ||
| Submit a version for App Review |
|
| Release a version in |
|
Diagnostics & Performance | ||
| List diagnostic signatures (hangs, disk writes) for a build |
|
| Get detailed logs with stack traces for a diagnostic signature |
|
| Get performance and power metrics for an app or build |
|
Organization | ||
| List configured organizations | — |
| Change the default organization |
|
All tools (except list_orgs and set_default_org) accept an optional org parameter to target a specific organization.
Configuration
Environment Variables
Variable | Description | Required |
| API key ID | Yes |
| Path to | Yes |
| API issuer ID; omit for individual keys | Team keys only |
| Authentication mode: | Required for individual keys |
Multi-Organization Support
Manage multiple App Store Connect teams by setting org-prefixed environment variables:
ASC_ORG_acme_ISSUER_ID=xxx
ASC_ORG_acme_KEY_ID=yyy
ASC_ORG_acme_PRIVATE_KEY_PATH=/path/to/acme.p8
ASC_ORG_acme_AUTH_MODE=team
ASC_ORG_startup_ISSUER_ID=aaa
ASC_ORG_startup_KEY_ID=bbb
ASC_ORG_startup_PRIVATE_KEY_PATH=/path/to/startup.p8
ASC_DEFAULT_ORG=acme # optional, defaults to first org alphabeticallyWhen multi-org variables are present, single-org variables are ignored. Use list_orgs to see configured organizations and set_default_org to switch at runtime.
Architecture
Sources/AppStoreConnectMCP/
main.swift — Entry point: server + stdio transport
Configuration.swift — Environment variable loading
OrganizationRegistry.swift — Multi-org registry (actor)
Auth/JWTGenerator.swift — ES256 JWT token generation
Logging/MCPLogger.swift — Stderr-based structured logging
API/
AppStoreConnectClient.swift — HTTP client with auto-retry (401/429)
Endpoints.swift — URL builders
Models/ — Codable request/response types (JSON:API)
Tools/
ToolDefinitions.swift — MCP tool schemas
ToolRouter.swift — Tool call dispatch
Handlers/ — One handler per toolReporting Issues
The GitHub Issues tab is disabled for security reasons. To report a bug or request a feature, please reach out directly to one of the maintainers:
Contributing
See CONTRIBUTING.md for guidelines on adding new tools and development workflow.
Links
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables 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.Last updated31141MIT
- Alicense-qualityCmaintenanceEnables AI agents to manage Apple App Store Connect through the official API, including apps, metadata, reviews, TestFlight, provisioning, users, and reports.Last updatedMIT
- Alicense-qualityCmaintenanceEnables AI assistants to manage Apple App Store Connect resources like apps, builds, TestFlight, and reviews through natural language.Last updated8MIT
- Alicense-qualityCmaintenanceEnables AI agents to manage App Store Connect apps, including registering bundle IDs, uploading metadata and screenshots, setting age ratings, managing TestFlight groups and testers, and submitting apps for review.Last updatedMIT
Related MCP Connectors
Live App Store & Google Play data for AI agents: app discovery, ASO keywords, reviews.
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Create App Store screenshots, icons, ASO copy, localization, and revisions via hosted MCP.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vvlladd/AppStoreConnectMCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server