App Store Connect MCP Server
Automate App Store Connect from your AI agent. Manage versions, metadata, builds, and submissions through natural language.
README
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.
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 submission — Submit versions to App Review in one step
- 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.sh
This fetches dependencies, generates the Xcode project, and builds. Or manually:
tuist install && tuist generate && tuist build
Configure
Set your API credentials:
export ASC_KEY_ID="your-key-id"
export ASC_PRIVATE_KEY_PATH="/path/to/AuthKey_XXXXXX.p8"
export ASC_ISSUER_ID="your-issuer-id" # required for team keys
export ASC_AUTH_MODE="team" # "team" (default) or "individual"
Get these values from App Store Connect > Users and Access > Integrations > App Store Connect API. For individual keys, set ASC_AUTH_MODE="individual" and omit ASC_ISSUER_ID.
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-mcp
Connect to Claude Code
Add to ~/.claude.json (global) or .claude/settings.json (project) and use the npm package:
{
"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"
}
}
}
}
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 | ||
prepare_release |
Check readiness, create version, attach build, sync metadata | app_id, version_string, platform |
release_status |
Full status overview: state, build, localizations, release type | app_id, version_id?, platform? |
validate_for_submission |
Pre-submit checklist with pass/fail for each requirement | app_id, version_id?, platform? |
clone_version_metadata |
Copy all localizations from one version to another | source_version_id, target_version_id, locales? |
| Version Management | ||
list_apps |
List all apps in your account | — |
create_version |
Create a new App Store version | app_id, version_string, platform |
list_versions |
List existing versions for an app | app_id, platform? |
update_version |
Update version attributes | version_id, copyright?, release_type? |
add_localization |
Add/update localized metadata | version_id, locale, description?, keywords?, whats_new?, promotional_text?, marketing_url?, support_url? |
| Build Management | ||
list_builds |
List available builds | app_id, limit? |
upload_build |
Upload an IPA to App Store Connect | app_id, ipa_path, version_string, build_number, platform? |
attach_build |
Attach a build to a version | version_id, build_id |
| Review | ||
submit_for_review |
Submit a version for App Review | version_id |
| Diagnostics & Performance | ||
list_diagnostic_signatures |
List diagnostic signatures (hangs, disk writes) for a build | build_id, diagnostic_type?, limit? |
get_diagnostic_logs |
Get detailed logs with stack traces for a diagnostic signature | signature_id |
get_perf_metrics |
Get performance and power metrics for an app or build | app_id or build_id, metric_type?, platform? |
| Organization | ||
list_orgs |
List configured organizations | — |
set_default_org |
Change the default organization | org |
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 |
|---|---|---|
ASC_KEY_ID |
API key ID | Yes |
ASC_PRIVATE_KEY_PATH |
Path to .p8 private key file |
Yes |
ASC_ISSUER_ID |
API issuer ID | Team keys only |
ASC_AUTH_MODE |
team (default) or individual |
No |
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 alphabetically
When 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 tool
Reporting 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
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。