app-store-connect-mcp
MCP server for App Store Connect that enables reading app/version data, analytics reports, sales/finance reports, and safely preparing metadata updates via natural language.
README
App Store Connect MCP
An MCP server for App Store Connect that works with Claude Desktop and Claude Code.
It focuses on two practical workflows:
- Read App Store Connect app and version data
- Read App Analytics report pipelines and safely prepare metadata updates
Features
App tools
list_appsget_applist_app_infosget_app_info_localizationsget_app_store_versionsget_app_store_version_localizations
Analytics tools
list_analytics_report_requestscreate_analytics_report_requestget_analytics_report_request_statusdiagnose_analytics_pipelinelist_analytics_reportslist_analytics_report_instanceslist_analytics_report_segmentsdownload_analytics_report_segmentreset_analytics_report_request
Sales and finance tools
download_sales_reportsummarize_app_sales_reportdownload_finance_report
Metadata tools
update_app_info_localizationupdate_app_store_version_localization
Security
This project is designed to avoid storing credentials in source control.
- Do not commit
.env - Do not commit
*.p8 - Store your App Store Connect private key outside the repository
- Use
dryRun=truebefore any metadata update - Real metadata changes require
dryRun=falseandconfirm=true
The server only reads credentials from environment variables:
APP_STORE_CONNECT_ISSUER_IDAPP_STORE_CONNECT_KEY_IDAPP_STORE_CONNECT_PRIVATE_KEY_PATHAPP_STORE_CONNECT_VENDOR_NUMBER
Project structure
src/
index.ts
config.ts
auth.ts
client.ts
types.ts
tools/
apps.ts
analytics.ts
metadata.ts
shared.ts
Requirements
- Node.js 20+
- An App Store Connect API key
- Access to the App Store Connect API for your Apple account
Setup
1. Install dependencies
npm install
2. Create your environment file
Copy .env.example to .env and fill in your own values:
cp .env.example .env
Example:
APP_STORE_CONNECT_ISSUER_ID=YOUR_ISSUER_ID
APP_STORE_CONNECT_KEY_ID=YOUR_KEY_ID
APP_STORE_CONNECT_PRIVATE_KEY_PATH=/absolute/path/to/AuthKey_XXXXXXXXXX.p8
APP_STORE_CONNECT_VENDOR_NUMBER=YOUR_VENDOR_NUMBER
3. Build
npm run build
Run locally
Development:
npm run dev
Production build:
npm start
Scripts
npm run dev— run the server from TypeScript sourcenpm run build— compile TypeScript todist/npm start— start the built MCP servernpm run test:connection— test the App Store Connect connectionnpm run inspect— run a local MCP client against the server
Claude Code setup
Option 1: project-scoped config
This repository includes a shareable .mcp.json:
{
"mcpServers": {
"app-store-connect": {
"command": "npm",
"args": ["start"]
}
}
}
If Claude Code is opened in this project, it can use that project config.
Option 2: user-scoped config
claude mcp add app-store-connect -s user \
-e APP_STORE_CONNECT_ISSUER_ID=YOUR_ISSUER_ID \
-e APP_STORE_CONNECT_KEY_ID=YOUR_KEY_ID \
-e APP_STORE_CONNECT_PRIVATE_KEY_PATH=/absolute/path/to/AuthKey_XXXXXXXXXX.p8 \
-- node /absolute/path/to/app-store-connect-mcp/dist/index.js
Claude Desktop setup
Add this to claude_desktop_config.json:
{
"mcpServers": {
"app-store-connect": {
"command": "node",
"args": [
"/absolute/path/to/app-store-connect-mcp/dist/index.js"
],
"env": {
"APP_STORE_CONNECT_ISSUER_ID": "YOUR_ISSUER_ID",
"APP_STORE_CONNECT_KEY_ID": "YOUR_KEY_ID",
"APP_STORE_CONNECT_PRIVATE_KEY_PATH": "/absolute/path/to/AuthKey_XXXXXXXXXX.p8"
}
}
}
}
Restart Claude Desktop after saving the config.
Example prompts
Try these in Claude:
Run the list_apps tool and show my appsUse get_app for a specific app IDUse list_app_infos for app 123456789 and include localizationsUse get_app_info_localizations for a specific app info IDUse get_app_store_versions for app 123456789 and include localizationsList analytics report requests for app 123456789Create an ONGOING analytics report request for app 123456789Diagnose the analytics pipeline for app 123456789Get analytics request status for request abc123Reset analytics report request abc123 for app 123456789 as ONGOINGSummarize the latest SALES summary report for app 123456789Download the SUBSCRIPTION daily report for my vendor numberRun update_app_info_localization in dry run mode to compare a title or subtitle changeRun update_app_store_version_localization in dry run mode and compare the proposed changes
Troubleshooting analytics reports
If App Store Connect shows Analytics data in the web UI but MCP cannot download analytics reports, the usual cause is that Apple hasn't generated report instances yet for the Analytics Reports API.
Recommended workflow:
- Run
diagnose_analytics_pipelinefor the app ID. - If the result is
NO_REQUEST, create anONGOINGrequest. - If the result is
NO_INSTANCES, wait 1-2 days after the request was created. Apple documents that the first request can take that long before instances appear. - If the result is
STOPPED_DUE_TO_INACTIVITY, usereset_analytics_report_requestto replace the inactive request. - If you need older backfill, create a
ONE_TIME_SNAPSHOTrequest. Apple allows one snapshot request per month.
Important notes from Apple:
- The first time a report type is requested, an Admin role may be required.
- Once a report type has been requested, Sales and Reports or Finance roles can download generated reports.
- Report instances expire after 35 days, so historical recovery may require a new
ONE_TIME_SNAPSHOTrequest.
Notes on permissions
Different App Store Connect API roles can unlock different endpoints.
- App metadata and localization work typically require
App Manageror broader - Analytics report management may require
Admin, depending on the endpoint - Sales and Trends reports typically require
Sales and Reports - Finance reports typically require
Finance
If a tool returns 403 FORBIDDEN_ERROR, check the role attached to your App Store Connect API key.
Output behavior
stdoutis reserved for MCP protocol traffic- Logs are sent to
stderr - Credentials and private key contents are never printed by this project
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.