App Store Connect MCP Server

A Model Context Protocol (MCP) server for interacting with the App Store Connect API. This server provides tools for managing apps, beta testers, bundle IDs, devices, app metadata, and capabilities in App Store Connect.

Overview

The App Store Connect MCP Server is a comprehensive tool that bridges the gap between AI and Apple's App Store Connect ecosystem. Built on the Model Context Protocol (MCP), this server enables developers to interact with their App Store Connect data directly through conversational AI, making app management, beta testing, and analytics more accessible than ever.

Key Benefits:

• 🤖 AI-Powered App Management: Use natural language to manage your iOS and macOS apps

• 📊 Comprehensive Analytics: Access detailed app performance, sales, and user engagement data

• 👥 Streamlined Beta Testing: Efficiently manage beta groups and testers

• 🌍 Localization Management: Update app descriptions, keywords, and metadata across all languages

• 🔧 Developer Tools Integration: List Xcode project schemes and integrate with development workflows

• 🔐 Secure Authentication: Uses official App Store Connect API with JWT authentication

• 🚀 Real-time Data: Access up-to-date information directly from Apple's systems

Who This Is For:

• iOS/macOS developers managing apps in App Store Connect

• Development teams coordinating beta testing programs

• Product managers analyzing app performance and user engagement

• Marketing teams managing app metadata and localizations

• DevOps engineers automating app store workflows

• Anyone looking to streamline their Apple developer experience

This server transforms complex App Store Connect operations into simple conversational commands, whether you're checking app analytics, managing beta testers, updating app descriptions, or exploring your development pipeline.

Features

• App Management

  • List all apps

  • Get detailed app information

  • View app metadata and relationships

• Beta Testing

  • List beta groups

  • List beta testers

  • Add/remove testers from groups

  • Manage beta test configurations

  • View beta feedback with screenshots and device information

• App Store Version Localizations ✨ NEW

  • Create new app store versions with release scheduling

  • List all app store versions for an app

  • List all localizations for an app version

  • Get specific localization details

  • Update app descriptions, keywords, and promotional text

  • Manage marketing and support URLs

  • Update "What's New" text for releases

• Bundle ID Management

  • List bundle IDs

  • Create new bundle IDs

  • Get bundle ID details

  • Enable/disable capabilities

• Device Management

  • List registered devices

  • Filter by device type, platform, status

  • View device details

• User Management

  • List team members

  • View user roles and permissions

  • Filter users by role and access

• Analytics & Reports

  • Create analytics report requests for apps

  • Download App Store engagement, commerce, and usage analytics

  • Access performance and frameworks usage reports

  • Download sales and trends reports (daily, weekly, monthly, yearly)

  • Download finance reports by region

• Xcode Development Tools

  • List available schemes in Xcode projects and workspaces

  • Integrate with development workflows and CI/CD pipelines

• Workflow & Build Management ✨ NEW

  • List workflows (CI products) for your team

  • List build runs for specific workflows/CI products

  • View detailed build information including git commit details (SHA, message, author, etc.)

  • Filter builds by status, date, pull request builds, execution progress

  • Monitor CI/CD pipeline status and results

• CI Build Debugging & Logs ✨ NEW

  • List build actions (analyze, build, test, archive) for build runs

  • Get detailed build action information

  • List and filter build issues and errors by type and category

  • Access test results with failure details and file locations

  • Comprehensive debugging support for failed builds and tests

Installation

Using Smithery

To install App Store Connect Server for Claude Desktop automatically:

Manual Installation

Or use directly with npx:

Configuration

Add the following to your Claude Desktop configuration file:

macOS

Windows

Authentication

Required Configuration

1. Generate an App Store Connect API Key from App Store Connect

2. Download the .p8 private key file

3. Note your Key ID and Issuer ID

4. Set the required environment variables in your configuration:

   • APP_STORE_CONNECT_KEY_ID: Your API Key ID

   • APP_STORE_CONNECT_ISSUER_ID: Your Issuer ID

   • APP_STORE_CONNECT_P8_PATH: Path to your .p8 private key file

   • OR APP_STORE_CONNECT_P8_B64_STRING: The base64 encoded contents of your .p8 private key file ✨ NEW

Private Key Configuration: You can provide your private key in two ways:

• File Path (recommended for local development): Use APP_STORE_CONNECT_P8_PATH with the path to your .p8 file

• Direct Content (useful for CI/CD and cloud deployments): Use APP_STORE_CONNECT_P8_B64_STRING with the base64 encoded .p8 file content

Example using P8_B64_STRING:

How to create the base64 encoded private key:

To create the base64 encoded string from your .p8 file, you can use the following command:

Copy the resulting base64 string and use it as the value for APP_STORE_CONNECT_P8_B64_STRING.

Optional Configuration for Sales & Finance Reports

To enable sales and finance reporting tools, you'll also need:

• APP_STORE_CONNECT_VENDOR_NUMBER: Your vendor number from App Store Connect

Note: Sales and finance report tools (download_sales_report, download_finance_report) will only be available if the vendor number is configured. You can find your vendor number in App Store Connect under "Sales and Trends" or "Payments and Financial Reports".

Complete Tool Reference

📱 App Management Tools

list_apps

Get a list of all apps in App Store Connect.

Parameters:

• limit (optional): Maximum number of apps to return (default: 100, max: 200)

• bundleId (optional): Filter by bundle identifier

Example:

get_app_info

Get detailed information about a specific app.

Parameters:

• appId (required): The ID of the app

• include (optional): Related resources to include (e.g., appClips, appInfos, appStoreVersions, betaGroups, builds)

Example:

👥 Beta Testing Tools

list_beta_groups

List all beta testing groups (internal and external).

Parameters:

• limit (optional): Maximum number of groups to return (default: 100, max: 200)

• appId (optional): Filter by app ID

Example:

list_group_testers

List testers in a specific beta group.

Parameters:

• groupId (required): The ID of the beta group

• limit (optional): Maximum number of testers to return (default: 100, max: 200)

Example:

add_tester_to_group

Add a new tester to a beta group.

Parameters:

• groupId (required): The ID of the beta group

• email (required): Email address of the tester

• firstName (optional): Tester's first name

• lastName (optional): Tester's last name

Example:

remove_tester_from_group

Remove a tester from a beta group.

Parameters:

• groupId (required): The ID of the beta group

• testerId (required): The ID of the tester

Example:

list_beta_feedback_screenshots

List beta feedback screenshot submissions.

Parameters:

• appId (optional): Filter by app ID

• bundleId (optional): Filter by bundle identifier

• buildId (optional): Filter by build ID

• limit (optional): Maximum results (default: 100)

• includeBuilds (optional): Include build information

• includeTesters (optional): Include tester information

Example:

get_beta_feedback_screenshot

Get detailed information about a specific beta feedback screenshot.

Parameters:

• feedbackId (required): The ID of the feedback

• includeBuilds (optional): Include build information

• includeTesters (optional): Include tester information

• downloadScreenshot (optional): Download the screenshot image (default: true)

Example:

🌍 App Store Version Localization Tools

create_app_store_version

Create a new app store version for an app.

Parameters:

• appId (required): The ID of the app

• platform (required): The platform (IOS, MAC_OS, TV_OS, VISION_OS)

• versionString (required): Version string in format X.Y or X.Y.Z (e.g., '1.0' or '1.0.0')

• copyright (optional): Copyright text for this version

• releaseType (optional): How the app should be released (MANUAL, AFTER_APPROVAL, SCHEDULED)

• earliestReleaseDate (optional): ISO 8601 date string (required when releaseType is SCHEDULED)

• buildId (optional): ID of the build to associate with this version

Example:

list_app_store_versions

Get all app store versions for a specific app.

Parameters:

• appId (required): The ID of the app

• limit (optional): Maximum number of versions to return (default: 100, max: 200)

• filter (optional): Filter options

  • platform: Filter by platform (IOS, MAC_OS, TV_OS)

  • versionString: Filter by version string (e.g., '1.0.0')

  • appStoreState: Filter by state (e.g., READY_FOR_SALE, PREPARE_FOR_SUBMISSION)

Example:

list_app_store_version_localizations

Get all localizations for a specific app store version.

Parameters:

• appStoreVersionId (required): The ID of the app store version

• limit (optional): Maximum number of localizations (default: 100, max: 200)

Example:

get_app_store_version_localization

Get detailed information about a specific localization.

Parameters:

• localizationId (required): The ID of the localization

Example:

update_app_store_version_localization

Update a specific field in an app store version localization.

Parameters:

• localizationId (required): The ID of the localization

• field (required): Field to update (description, keywords, marketingUrl, promotionalText, supportUrl, whatsNew)

• value (required): New value for the field

Example:

🔤 Bundle ID Management Tools

create_bundle_id

Register a new bundle ID for app development.

Parameters:

• identifier (required): The bundle ID string (e.g., 'com.example.app')

• name (required): A name for the bundle ID

• platform (required): Platform (IOS, MAC_OS, or UNIVERSAL)

• seedId (optional): Your team's seed ID

Example:

list_bundle_ids

Find and list bundle IDs registered to your team.

Parameters:

• limit (optional): Maximum results (default: 100, max: 200)

• sort (optional): Sort order (name, -name, platform, -platform, identifier, -identifier)

• filter (optional): Filter by identifier, name, platform, or seedId

• include (optional): Include related resources (profiles, bundleIdCapabilities, app)

Example:

get_bundle_id_info

Get detailed information about a specific bundle ID.

Parameters:

• bundleIdId (required): The ID of the bundle ID

• include (optional): Related resources to include

• fields (optional): Specific fields to include

Example:

enable_bundle_capability

Enable a capability for a bundle ID.

Parameters:

• bundleIdId (required): The ID of the bundle ID

• capabilityType (required): Type of capability (e.g., PUSH_NOTIFICATIONS, ICLOUD, GAME_CENTER)

• settings (optional): Capability-specific settings

Example:

disable_bundle_capability

Disable a capability for a bundle ID.

Parameters:

• capabilityId (required): The ID of the capability to disable

Example:

📱 Device Management Tools

list_devices

Get a list of all devices registered to your team.

Parameters:

• limit (optional): Maximum results (default: 100, max: 200)

• sort (optional): Sort order (name, platform, status, udid, deviceClass, model, addedDate)

• filter (optional): Filter by name, platform, status, udid, or deviceClass

• fields (optional): Specific fields to include

Example:

👤 User Management Tools

list_users

Get a list of all users on your App Store Connect team.

Parameters:

• limit (optional): Maximum results (default: 100, max: 200)

• sort (optional): Sort order (username, firstName, lastName, roles)

• filter (optional): Filter by username or roles

• fields (optional): Specific fields to include

• include (optional): Include visibleApps relationship

Example:

📊 Analytics & Reports Tools

create_analytics_report_request

Create a new analytics report request for an app.

Parameters:

• appId (required): The app ID

• accessType (required): Type of analytics (ONGOING or ONE_TIME_SNAPSHOT)

• frequency (optional): Report frequency for ongoing reports (DAILY, WEEKLY, MONTHLY)

• startDate (optional): Start date (YYYY-MM-DD)

• endDate (optional): End date (YYYY-MM-DD)

Example:

list_analytics_reports

Get available analytics reports for a request.

Parameters:

• reportRequestId (required): The report request ID

• limit (optional): Maximum results (default: 100, max: 200)

• filter (optional): Filter by category, name, or date

Example:

list_analytics_report_segments

Get segments for a specific analytics report.

Parameters:

• reportId (required): The analytics report ID

• limit (optional): Maximum results (default: 100, max: 200)

Example:

download_analytics_report_segment

Download data from an analytics report segment.

Parameters:

• url (required): The segment download URL

Example:

💰 Sales & Finance Reports Tools (Requires Vendor Number)

download_sales_report

Download sales and trends reports.

Parameters:

• frequency (required): Report frequency (DAILY, WEEKLY, MONTHLY, YEARLY)

• reportDate (required): Date in appropriate format

• reportType (required): Type of report (SALES, SUBSCRIPTION, SUBSCRIPTION_EVENT, SUBSCRIBER, NEWSSTAND, PREORDER)

• reportSubType (required): SUMMARY or DETAILED

• vendorNumber (optional): Override default vendor number

• version (optional): Report version (default: 1_0)

Example:

download_finance_report

Download finance reports for a specific region.

Parameters:

• reportDate (required): Report date (YYYY-MM)

• regionCode (required): Region code (e.g., 'Z1' for worldwide)

• vendorNumber (optional): Override default vendor number

Example:

🔧 Xcode Development Tools

list_schemes

List all available schemes in an Xcode project or workspace.

Parameters:

• projectPath (required): Path to .xcodeproj or .xcworkspace file

Example:

🚀 Workflow & Build Management Tools ✨ NEW

list_workflows

List all App Store Connect workflows (CI products) and their associated apps.

Parameters:

• limit (optional): Maximum number of workflows to return (default: 100, max: 200)

• sort (optional): Sort by name, -name, productType, or -productType

• filter (optional): Filter by productType (IOS, MAC_OS, TV_OS, VISION_OS)

• include (optional): Include related resources (app, bundleId, primaryRepositories)

• fields (optional): Select specific fields for ciProducts

Example:

list_build_runs

List build runs for a specific workflow/CI product, including detailed git commit information.

Parameters:

• ciProductId (required): The ID of the CI product (workflow) to list build runs for

• limit (optional): Maximum number of build runs to return (default: 100, max: 200)

• sort (optional): Sort by number, -number, createdDate, -createdDate, startedDate, -startedDate, finishedDate, -finishedDate

• filter (optional): Filter by:

  • number: Build run number

  • isPullRequestBuild: Whether it's a pull request build

  • executionProgress: PENDING, RUNNING, COMPLETE

  • completionStatus: SUCCEEDED, FAILED, ERRORED, CANCELED, SKIPPED

  • startReason: MANUAL, SCM_CHANGE, PULL_REQUEST_UPDATE, SCHEDULED

• include (optional): Include related resources (builds, workflow, product, sourceBranchOrTag, destinationBranch, pullRequest)

• fields (optional): Select specific fields for ciBuildRuns

Git Commit Information: Each build run includes detailed git commit information such as:

• Commit SHA (source and destination)

• Commit message

• Author and committer details

• Web URL for the commit

• Pull request information (if applicable)

Example:

list_ci_build_actions

List build actions (analyze, build, test, archive) for a specific build run.

Parameters:

• buildRunId (required): The ID of the build run to list actions for

• limit (optional): Maximum number of build actions to return (default: 100, max: 200)

• sort (optional): Sort by name, -name, actionType, -actionType, startedDate, -startedDate, finishedDate, -finishedDate

• filter (optional): Filter by:

  • actionType: ANALYZE, BUILD, TEST, ARCHIVE

  • executionProgress: PENDING, RUNNING, COMPLETE

  • completionStatus: SUCCEEDED, FAILED, ERRORED, CANCELED, SKIPPED

• include (optional): Include related resources (buildRun, issues, testResults)

• fields (optional): Select specific fields for ciBuildActions

Example:

get_ci_build_action

Get detailed information about a specific build action.

Parameters:

• buildActionId (required): The ID of the build action

• include (optional): Include related resources (buildRun, issues, testResults)

• fields (optional): Select specific fields for ciBuildActions

Example:

list_ci_issues

List issues and errors from a build run or build action.

Parameters:

• buildRunId (optional): The ID of the build run to list issues for (provide either buildRunId or buildActionId)

• buildActionId (optional): The ID of the build action to list issues for (provide either buildRunId or buildActionId)

• limit (optional): Maximum number of issues to return (default: 100, max: 200)

• sort (optional): Sort by issueType, -issueType, category, -category, message, -message

• filter (optional): Filter by:

  • issueType: ANALYZER_WARNING, ERROR, TEST_FAILURE, WARNING

  • category: Issue category string

• include (optional): Include related resources (buildAction, buildRun)

• fields (optional): Select specific fields for ciIssues

Example:

list_ci_test_results

List test results from a build run or build action.

Parameters:

• buildRunId (optional): The ID of the build run to list test results for (provide either buildRunId or buildActionId)

• buildActionId (optional): The ID of the build action to list test results for (provide either buildRunId or buildActionId)

• limit (optional): Maximum number of test results to return (default: 100, max: 200)

• sort (optional): Sort by className, -className, name, -name, status, -status, duration, -duration

• filter (optional): Filter by:

  • status: SUCCESS, FAILURE, SKIPPED

  • className: Test class name

  • name: Test method name

• include (optional): Include related resources (buildAction, buildRun)

• fields (optional): Select specific fields for ciTestResults

Example:

Error Handling

The server implements proper error handling for:

• Invalid authentication

• Missing required parameters

• API rate limits

• Network issues

• Invalid operations

Development

License

This project is licensed under the MIT License - see the LICENSE file for details.

Related Links

• Model Context Protocol Documentation

• App Store Connect API Documentation

• MCP TypeScript SDK