App Store Connect

You can run a Model Context Protocol (MCP) server for Apple's App Store Connect API to manage apps, versions, beta testing, localization, and more directly from MCP clients. This server centralizes App Store Connect interactions, enabling automated workflows and integrations while handling credential security and token management for you.

How to use

You operate this server from an MCP client by starting the local server instance and pointing your client to the provided MCP endpoints. Use the client to list apps, create and update versions, manage localization data, handle TestFlight testers, upload screenshots, register bundle IDs, inspect devices and users, review builds, and check pricing and availability. The server handles authentication with ES256 JWTs, automatically refreshing tokens and redacting sensitive information in logs, so you can focus on your workflow.

How to install

Prerequisites: Node.js 20+ and a modern MCP client (any MCP-compatible tool or assistant).

Step-by-step commands you can follow to install and start using the MCP server.

# 1. Install the MCP server globally
npm install -g asc-mcp

# 2. Set credentials from App Store Connect
export APP_STORE_CONNECT_KEY_ID="YOUR_KEY_ID"
export APP_STORE_CONNECT_ISSUER_ID="YOUR_ISSUER_ID"
export APP_STORE_CONNECT_P8_PATH="/path/to/AuthKey.p8"

# 3. Run the MCP server (integrate with your MCP client as configured below) 
asc-mcp

Configuration

Prerequisites: Set up credentials in App Store Connect API section and provide them to the MCP server via environment variables. The server supports both file-based private keys and direct key content.

Environment variables you will use includes the following. Provide at least one of the key file path or key content.

Security

Security is built around ES256 JWT authentication with automatic token refresh. Private keys are never logged, and tokens are redacted in error output. Key identifiers and issuer IDs are treated as sensitive and are redacted from logs. Tokens are cached and refreshed periodically to minimize key usage.

Troubleshooting

If you encounter configuration errors, verify that all required environment variables are defined and that the path to your private key is correct. Ensure the private key starts with the standard header and that the issuer and key IDs match the key file.

Development

Development and testing require Node.js 20+ and a compatible testing setup. You can build and run tests to verify MCP endpoints and tool integrations as you extend functionality.

Available tools

list_apps

List all apps in your account

get_app

Get details of a specific app

list_app_versions

List all versions for an app

get_app_version

Get version details

create_app_version

Create a new app version

list_version_localizations

List localizations for a version

get_version_localization

Get localization details

create_version_localization

Add a new locale

update_version_localization

Update localization

delete_version_localization

Remove a localization

list_app_infos

List app info records

list_app_info_localizations

List name/subtitle localizations

update_app_info_localization

Update app name and subtitle

list_beta_groups

List beta groups for an app

list_beta_testers

List testers in a beta group

add_beta_tester

Add a tester to a beta group

remove_beta_tester

Remove a tester from a beta group

list_screenshot_sets

List screenshot sets for a localization

list_screenshots

List screenshots in a set

upload_screenshot

Upload a new screenshot

list_bundle_ids

List all bundle IDs

get_bundle_id

Get bundle ID details

create_bundle_id

Register a new bundle ID

update_bundle_id

Update bundle ID name

delete_bundle_id

Delete a bundle ID

list_devices

List registered devices

get_device

Get device details

list_users

List team users

get_user

Get user details

list_builds

List builds for an app

get_build

Get build details

list_app_categories

List app categories

get_app_price_schedule

Get app pricing info

get_app_availability

Get app territory availability