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.sh

This fetches dependencies, generates the Xcode project, and builds. Or manually:

tuist install && tuist generate && tuist build

Configure

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-mcp

Connect 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."

Handshake Troubleshooting

If Codex reports JSON-RPC -32603 with “The data couldn’t be read because it isn’t in the correct format” during startup, rebuild this revision and replace the executable referenced by your MCP configuration. The Swift SDK 0.12.1 decodes experimental client capabilities as strings; structured values can fail initialization. This server includes a compatibility transport that ignores unsupported experimental values while preserving standard capabilities.

Verify a built executable with:

python3 scripts/test-handshake.py /path/to/AppStoreConnectMCP

The check uses a temporary key and tests initialization, tool discovery, and list_orgs without contacting App Store Connect. Restart the MCP connection after replacing the executable.

Available Tools

All tools (except list_orgs and set_default_org) accept an optional org parameter to target a specific organization.

To fetch store metadata, start with list_apps to get the app ID. Use list_app_infos to find the app-info record you want, then pass its ID to list_app_info_localizations for names, subtitles, and privacy fields. App-info records can represent live or upcoming metadata; the output includes each record's state and ID.

Use update_app_info_localization with the selected app_info_id, an existing locale, and at least one of name or subtitle. Omitted fields are preserved; an empty subtitle clears it. Select the draft app-info record to change upcoming metadata. This tool does not create missing locales.

For keywords and descriptions, use list_versions to choose the version and platform, then call list_version_localizations with its version ID. Both localization tools accept an optional locale filter and follow all pagination links. Full text is returned without truncation; missing or empty fields are shown as (not set).

For example: “Fetch the English name, subtitle, keywords, description, and privacy policy URL for my app's current iOS release.”

Verify metadata decoding and formatting with ./scripts/test-metadata.sh. After building, run python3 scripts/test-handshake.py /path/to/AppStoreConnectMCP to check tool discovery and argument validation. These checks use fixtures and a temporary key without contacting App Store Connect.

./scripts/test-release-metadata.sh tests draft release checks and localized name/subtitle updates against fixtures. It uses the frameworks from a release build; pass another build's product directory as its first argument if needed.

Configuration

Environment Variables

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:

• Vlad

• Max

Contributing

See CONTRIBUTING.md for guidelines on adding new tools and development workflow.

Links

• App Store Connect API documentation

• MCP Swift SDK

• Model Context Protocol specification