home / mcp / app store connect mcp server
Provides MCP access to App Store Connect data and actions via modular, OpenAPI‑driven tools.
Configuration
View docs{
"mcpServers": {
"gjeltep-app-store-connect-mcp": {
"command": "app-store-connect-mcp",
"args": [],
"env": {
"APP_STORE_APP_ID": "YOUR_APP_ID",
"APP_STORE_KEY_ID": "YOUR_KEY_ID",
"APP_STORE_KEY_TYPE": "team",
"APP_STORE_ISSUER_ID": "YOUR_ISSUER_ID",
"APP_STORE_PRIVATE_KEY_PATH": "/path/to/AuthKey_XXXXX.p8"
}
}
}
}You can run the App Store Connect MCP Server to interact with App Store Connect through modular, OpenAPI‑driven tools. This server stays up to date with Apple’s specs, supports async I/O, and filters data efficiently to help your agent work accurately as Apple evolves.
You run the MCP server locally and connect to it with any MCP‑compatible client. Start the server with your App Store Connect credentials set in the environment, then dispatch tool calls through the client. The server announces available tools and handles calls over the MCP stdio transport.
Prerequisites you need before installing and running the server include Python and a compatible runtime for the chosen installation method.
# Install from PyPI
pip install app-store-connect-mcp
# Or install from source
git clone https://github.com/gjeltep/app-store-connect-mcp.git
cd app-store-connect-mcp
uv pip install -e ".[dev]"Set the required environment variables before starting the server. These keys authenticate you to App Store Connect and identify your app where applicable.
export APP_STORE_KEY_ID="YOUR_KEY_ID"
export APP_STORE_ISSUER_ID="YOUR_ISSUER_ID"
export APP_STORE_PRIVATE_KEY_PATH="/path/to/AuthKey_XXXXX.p8"
# Optional
export APP_STORE_APP_ID="YOUR_APP_ID"
export APP_STORE_KEY_TYPE="team" # or "individual"Run the MCP server with your credentials loaded in the environment. The standard startup command uses the server’s executable name.
app-store-connect-mcpDuring development you can validate your configuration or run with a local environment file.
# Copy and configure a local environment file if you maintain one
cp .env.example .env
# Edit .env with your credentials
# Run with an explicit env file
app-store-connect-mcp-dev --env-file .env
# Validate configuration without starting the server
app-store-connect-mcp-dev --env-file .env --validate-onlyList customer reviews with optional filters like rating, territory, and appStoreVersion.
Advanced search for reviews with rating ranges, territory matching, date windows, and content search.
Get detailed information about a specific review.
List crash submissions from beta testers with filters such as deviceModel, osVersion, appPlatform, and build_id.
Advanced crash search with server-side filters and post-filters for OS ranges, device substrings, and dates.
Get detailed information about a specific crash submission.
Retrieve the raw crash log text for a submission.
List analytics report requests for an app with filters like access_type.
Create new analytics report requests for specific metrics and timeframes.
Get detailed information about a specific analytics report request.
List available reports within a request with filters like name and category.
Get specific analytics report information.
List report instances with filters like granularity and processing_date.
Get detailed information about a specific report instance.
List data segments for a report instance.
Get segment download information including checksum, URL, and size.
Download analytics report data to a TSV file.
List all Xcode Cloud products with filters like product_type.
Get detailed information about a specific product.
List workflows for a product with filters like is_enabled.
Get detailed workflow information.
List builds for a product or workflow with filters like execution_progress and completion_status.
Get detailed build information including status and duration.
Start a new build for a workflow with optional branch, tag, or pull request specification.
List downloadable artifacts for a build.
List issues (errors, warnings) for builds or workflows.
List test results with status, duration, and failure messages.
List configured SCM providers like GitHub, GitLab, or Bitbucket.
List Git repositories for an SCM provider.
List pull requests for a repository.
List branches and tags for a repository.