app-store-connect-mcp

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.

Category
访问服务器

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_apps
  • get_app
  • list_app_infos
  • get_app_info_localizations
  • get_app_store_versions
  • get_app_store_version_localizations

Analytics tools

  • list_analytics_report_requests
  • create_analytics_report_request
  • get_analytics_report_request_status
  • diagnose_analytics_pipeline
  • list_analytics_reports
  • list_analytics_report_instances
  • list_analytics_report_segments
  • download_analytics_report_segment
  • reset_analytics_report_request

Sales and finance tools

  • download_sales_report
  • summarize_app_sales_report
  • download_finance_report

Metadata tools

  • update_app_info_localization
  • update_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=true before any metadata update
  • Real metadata changes require dryRun=false and confirm=true

The server only reads credentials from environment variables:

  • APP_STORE_CONNECT_ISSUER_ID
  • APP_STORE_CONNECT_KEY_ID
  • APP_STORE_CONNECT_PRIVATE_KEY_PATH
  • APP_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 source
  • npm run build — compile TypeScript to dist/
  • npm start — start the built MCP server
  • npm run test:connection — test the App Store Connect connection
  • npm 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 apps
  • Use get_app for a specific app ID
  • Use list_app_infos for app 123456789 and include localizations
  • Use get_app_info_localizations for a specific app info ID
  • Use get_app_store_versions for app 123456789 and include localizations
  • List analytics report requests for app 123456789
  • Create an ONGOING analytics report request for app 123456789
  • Diagnose the analytics pipeline for app 123456789
  • Get analytics request status for request abc123
  • Reset analytics report request abc123 for app 123456789 as ONGOING
  • Summarize the latest SALES summary report for app 123456789
  • Download the SUBSCRIPTION daily report for my vendor number
  • Run update_app_info_localization in dry run mode to compare a title or subtitle change
  • Run 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:

  1. Run diagnose_analytics_pipeline for the app ID.
  2. If the result is NO_REQUEST, create an ONGOING request.
  3. 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.
  4. If the result is STOPPED_DUE_TO_INACTIVITY, use reset_analytics_report_request to replace the inactive request.
  5. If you need older backfill, create a ONE_TIME_SNAPSHOT request. 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_SNAPSHOT request.

Notes on permissions

Different App Store Connect API roles can unlock different endpoints.

  • App metadata and localization work typically require App Manager or 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

  • stdout is reserved for MCP protocol traffic
  • Logs are sent to stderr
  • Credentials and private key contents are never printed by this project

License

MIT

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选