App Store Connect Mcp

io.github.gjeltepPublished by GitHub account gjeltepv0.3.0Updated Oct 24, 2026

Interact with Apple's App Store Connect API

Overview

AI-generated overview

Local MCP server that lets an assistant query Apple's App Store Connect API for reviews, TestFlight crashes, analytics reports and Xcode Cloud builds.

What you can do
  • List, search and read customer reviews with rating, territory and date filters
  • List and search TestFlight crash submissions, read details and fetch raw crash logs
  • Browse analytics report requests, reports, instances and segments, and download report data to a TSV file
  • List Xcode Cloud products, workflows, builds, artifacts, issues and test results, and start a new build
  • List SCM providers, repositories, pull requests, branches and tags
When to use it
Useful when you want an assistant to inspect an iOS or macOS app's App Store reviews, beta crash reports, analytics exports or Xcode Cloud CI status without opening App Store Connect by hand. It fits read-heavy triage and reporting work for app developers and release managers.
Requirements
Runs locally over stdio from the PyPI package app-store-connect-mcp (Python). Needs an App Store Connect API key: APP_STORE_KEY_ID, APP_STORE_ISSUER_ID and APP_STORE_PRIVATE_KEY_PATH pointing to a .p8 file; optional APP_STORE_APP_ID, APP_STORE_KEY_TYPE, APP_STORE_SCOPE and APP_STORE_SUBJECT. Network access to Apple's API.
Before you install
Requires an App Store Connect API private key file and key identifiers; keep the .p8 file and credentials out of shared configs. Most tools only read data, but builds.start triggers a real Xcode Cloud build, and report_instances.download_data writes a TSV file to disk. Analytics and crash data are sent to the model provider through the assistant.

Installation

In SourceWeft

  1. Open App Store Connect Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

App Store Connect MCP Server

[Test] [PyPI] [Python Version] [MCP Registry]

Talk to App Store Connect about your app. Modular tools, async I/O, and OpenAPI‑driven typing so your agent stays accurate as Apple evolves.

Why this is different

  • Spec‑aware: Fields and enums are derived from Apple’s OpenAPI spec at runtime, reducing drift and surprise breakage.
  • Fast by default: Async httpx client, server‑side filtering, and smart pagination to keep payloads lean.
  • Smart filtering: Server‑side + client‑side filtering with chainable filter engine for complex queries.
  • Modular domains: Clean separation of tool schemas and handlers; add new domains without touching the core; optimized LLM discovery/ usage
  • MCP‑native: Stdio transport, capability declarations, and tool wiring align with the official SDK python‑sdk README.

Installation

From PyPI
bash
pip install app-store-connect-mcp
From Source
bash
git clone https://github.com/gjeltep/app-store-connect-mcp.gitcd app-store-connect-mcpuv pip install -e ".[dev]"

Configuration

Set these environment variables:

bash
# Requiredexport 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"
# Optionalexport APP_STORE_APP_ID="YOUR_APP_ID"export APP_STORE_KEY_TYPE="team"  # or "individual"

Usage

Run with your environment variables set (recommended):

bash
app-store-connect-mcp

Or use a .env file during development:

bash
# Copy and configure .env filecp .env.example .env# Edit .env with your credentials
# Run with --env-file flagapp-store-connect-mcp-dev --env-file .env
# Validate configuration without starting serverapp-store-connect-mcp-dev --env-file .env --validate-only

Use with any MCP‑compatible client; the server announces tools and handles calls over stdio.

Generate or update API models

Models are generated from Apple's official OpenAPI spec (fetched automatically from Apple's developer site). You can override the source with APP_STORE_CONNECT_OPENAPI_URL to point to a local JSON file.

bash
uv pip install -e .[dev]python scripts/generate_models.py

Development

For development setup, testing, and contribution guidelines, see CONTRIBUTING.md.

Tools

Tools use a resource-first naming convention (resource.verb) with category tags for discoverability.

App Tools
  • reviews.list: List customer reviews with filters (rating, territory, appStoreVersion).
  • reviews.search: Advanced search with rating ranges, territory matching, date windows, and content search.
  • reviews.get: Get detailed review information.
TestFlight Tools
  • crashes.list: List crash submissions from beta testers with filters (device_model, os_version, app_platform, device_platform, build_id, tester_id).
  • crashes.search: Advanced search with:
    • Server‑side filters (appPlatform, deviceModel, osVersion)
    • Post‑filters: OS ranges (min/max), device model substrings (e.g., "iPhone 15"), and date windows (created_since_days, created_after, created_before).
  • crashes.get_by_id: Get detailed information about a specific crash submission.
  • crashes.get_log: Retrieve the raw crash log text for a specific submission.
Analytics Tools

Requests:

  • analytics_report_requests.list: List analytics report requests for an app with filters (access_type).
  • report_requests.create: Create new analytics report requests for specific metrics and timeframes.
  • report_requests.get: Get detailed information about a specific analytics report request.

Reports:

  • report_requests.list_reports: List available reports within a request with filters (name, category).
  • reports.get: Get specific analytics report information.
  • reports.list_instances: List report instances with filters (granularity, processing_date).
  • report_instances.get: Get detailed information about a specific report instance.

Segments:

  • report_instances.list_segments: List data segments for a report instance.
  • report_segments.get: Get segment download information (checksum, URL, size).
  • report_instances.download_data: Download analytics report data to a TSV file.
Xcode Cloud Tools

Products & Workflows:

  • products.list: List all Xcode Cloud products with filters (product_type).
  • products.get: Get detailed information about a specific product.
  • workflows.list: List workflows for a product with filters (is_enabled).
  • workflows.get: Get detailed workflow information (note: create/update/delete operations not supported for safety).

Builds:

  • builds.list: List builds for a product or workflow with filters (execution_progress, completion_status, is_pull_request_build).
  • builds.get: Get detailed build information including status, duration, and issue counts.
  • builds.start: Start a new build for a workflow with optional branch/tag or pull request specification.

Build Artifacts & Results:

  • artifacts.list: List downloadable artifacts for a build.
  • issues.list: List issues (errors, warnings) for builds or workflows.
  • test_results.list: List test results including status, duration, and failure messages.

SCM Integration:

  • scm_providers.list: List configured SCM providers (GitHub, GitLab, Bitbucket).
  • repositories.list: List Git repositories for an SCM provider.
  • pull_requests.list: List pull requests for a repository.
  • git_references.list: List branches and tags for a repository.

Architecture

mermaid
graph TD    %% Entry Point    subgraph "Entry Point"        SERVER[server.py<br/>MCP stdio server]    end
    %% Domain Implementations    subgraph "Domain Handlers"        TESTFLIGHT[testflight/handlers.py<br/>TestFlight crash<br/>management]        APP[app/handlers.py<br/>App Store review<br/>management]        ANALYTICS[analytics/handlers.py<br/>Analytics report<br/>management]        XCODE_CLOUD[xcode_cloud/handlers.py<br/>Xcode Cloud CI/CD<br/>management]    end
    %% Core Architecture    subgraph "Core Components"        subgraph "Core Framework"            PROTOCOLS[protocols.py<br/>Abstract interfaces]            BASE_HANDLER[base_handler.py<br/>Abstract base class]            QUERY_BUILDER[query_builder.py<br/>Fluent query construction]            FILTERS[filters.py<br/>Chainable filter engine]            RESPONSE_HANDLER[response_handler.py<br/>API response processing]            CONTAINER[container.py<br/>Dependency injection]            ERRORS[errors.py<br/>Structured error handling]        end
        subgraph "API Layer"            ASC_CLIENT[app_store_connect.py<br/>App Store Connect client<br/>with JWT auth]            HTTP_CLIENT[http_client.py<br/>Base HTTP client]            MODELS[app_store_connect_models.py<br/>Auto-generated Pydantic<br/>models from OpenAPI spec]        end
        subgraph "Data & Tools"            OPENAPI[app_store_connect_api_openapi.json<br/>Apple's OpenAPI spec]            GENERATE_SCRIPT[scripts/generate_models.py<br/>Model generation script]        end    end
    %% Vertical Stack Relationships    SERVER -->|"routes to"| ANALYTICS    ANALYTICS -->|"uses"| ASC_CLIENT
    %% Styling    classDef entry fill:#f3e5f5,stroke:#4a148c,stroke-width:2px    classDef core fill:#fff3e0,stroke:#e65100,stroke-width:2px    classDef domain fill:#fce4ec,stroke:#880e4f,stroke-width:2px
    class SERVER entry    class PROTOCOLS,BASE_HANDLER,QUERY_BUILDER,FILTERS,RESPONSE_HANDLER,CONTAINER,ERRORS,ASC_CLIENT,HTTP_CLIENT,MODELS,OPENAPI,GENERATE_SCRIPT core    class TESTFLIGHT,APP,ANALYTICS,XCODE_CLOUD domain

Credits

Built on the official Model Context Protocol Python SDK — see the docs and examples in the python‑sdk README.


See CONTRIBUTING.md if you'd like to help.

Source: README.md at commit fae0418

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts