
App Store Connect Mcp
- 1 repo stars
- Updated January 5, 2026
- gjeltep/app-store-connect-mcp
App Store Connect MCP is an MCP server that lets coding agents interact with Apple's App Store Connect API for store and release tasks.
About
App Store Connect MCP is a stdio MCP server distributed on PyPI that wraps Apple's App Store Connect API for agent-driven mobile launch work. iOS developers can register it in Claude Code or similar hosts so the model can perform store operations that normally require the Connect portal or custom scripts. Required secrets are the standard trio: key ID, issuer ID, and path to the.p8 API key file, with optional app ID and scope variables to narrow operations. It sits squarely in the Launch phase under ASO and distribution sub-work: versioning, metadata, and release logistics rather than feature implementation. Expect intermediate complexity because Apple API credentials, roles, and key storage are easy to misconfigure on a account.
- Python PyPI package `app-store-connect-mcp` (version 0.3.0) with stdio transport
- Authenticates with App Store Connect API Key ID, Issuer ID, and a .p8 private key path
- Supports optional defaults: `APP_STORE_APP_ID`, `APP_STORE_KEY_TYPE`, `APP_STORE_SCOPE`
- Exposes Apple's App Store Connect API to MCP clients for automated store workflows
- Team vs individual key type configurable via environment
App Store Connect Mcp by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --env APP_STORE_KEY_ID=YOUR_APP_STORE_KEY_ID --env APP_STORE_ISSUER_ID=YOUR_APP_STORE_ISSUER_ID --env APP_STORE_PRIVATE_KEY_PATH=YOUR_APP_STORE_PRIVATE_KEY_PATH --env APP_STORE_APP_ID=YOUR_APP_STORE_APP_ID --env APP_STORE_KEY_TYPE=YOUR_APP_STORE_KEY_TYPE --env APP_STORE_SCOPE=YOUR_APP_STORE_SCOPE --env APP_STORE_SUBJECT=YOUR_APP_STORE_SUBJECT app-store-connect-mcp -- uvx app-store-connect-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Package | app-store-connect-mcp |
| Transport | STDIO |
| Auth | Required |
| Last updated | January 5, 2026 |
| Repository | gjeltep/app-store-connect-mcp ↗ |
What it does
Let your agent read and update App Store Connect metadata, builds, and listing data without clicking through Apple's web console.
Who is it for?
Best when you're shipping Apple apps and already have App Store Connect API keys and want agent-assisted metadata, build, and listing workflows.
Skip if: Web-only or Android-only products with no App Store Connect account, or developers unwilling to manage.p8 keys and issuer IDs securely.
What you get
After MCP registration with valid Connect API credentials, your agent can call App Store Connect operations through stdio tools instead of manual dashboard steps.
- MCP-exposed App Store Connect API operations for your default or configured app
- Credential-driven authentication using team or individual key type settings
- Repeatable agent workflows for store-facing launch tasks
By the numbers
- Server version 0.3.0 on PyPI identifier `app-store-connect-mcp`
- Three required environment variables for API authentication (key ID, issuer ID, private key path)
- stdio transport only in published package metadata
README.md
App Store Connect MCP Server
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
httpxclient, 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
pip install app-store-connect-mcp
From Source
git clone https://github.com/gjeltep/app-store-connect-mcp.git
cd app-store-connect-mcp
uv pip install -e ".[dev]"
Configuration
Set these environment variables:
# Required
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"
Usage
Run with your environment variables set (recommended):
app-store-connect-mcp
Or use a .env file during development:
# Copy and configure .env file
cp .env.example .env
# Edit .env with your credentials
# Run with --env-file flag
app-store-connect-mcp-dev --env-file .env
# Validate configuration without starting server
app-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.
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).
- Server‑side filters (
- 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
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.
Recommended MCP Servers
How it compares
Apple API MCP bridge, not an ASO copywriting skill or TestFlight replacement UI.
FAQ
Who is App Store Connect MCP for?
iOS/macOS developers using AI agents who need programmatic access to App Store Connect during launch and listing updates.
When should I use App Store Connect MCP?
Use it in Launch when you are preparing releases, adjusting store metadata, or automating Connect tasks after the app build exists.
How do I add App Store Connect MCP to my agent?
Install the PyPI package, configure stdio MCP with `APP_STORE_KEY_ID`, `APP_STORE_ISSUER_ID`, and `APP_STORE_PRIVATE_KEY_PATH` to your.p8 file, then optionally set app ID and scope env vars.