appstore-mcp
An MCP server that exposes the Apple App Store Connect API to AI agents, enabling management of apps, metadata, in-app purchases, subscriptions, TestFlight, provisioning, reviews, analytics, and more through 113 curated tools plus two generic JSON:API escape-hatch tools.
README
appstore-mcp
An MCP server, written in Rust, that exposes the Apple App Store Connect API to AI agents. It covers the full product lifecycle — apps & metadata, in-app purchases, subscriptions and their offers, pricing & availability, App Store versions, App Review submission, TestFlight, provisioning & signing, asset uploads, promoted purchases, customer reviews, phased release, users & access, in-app events, Xcode Cloud, and analytics reports — across 113 tools, and can reach any other App Store Connect endpoint through two generic JSON:API tools.
Built on the official rmcp SDK over stdio.
📖 Full tool reference → docs/TOOLS.md — every tool's purpose and parameters.
Design: hybrid coverage
The App Store Connect API has hundreds of endpoints but is uniformly JSON:API. Rather than a tool per endpoint, this server is hybrid:
- Curated tools (111) for the common, multi-step, or error-prone workflows — apps & metadata, IAPs, subscriptions & offers, versions, pricing, availability, App Review submission, TestFlight, provisioning, asset uploads, promoted purchases, customer reviews, phased release, users, in-app events, Xcode Cloud, analytics reports, and custom product pages.
- Two generic escape-hatch tools —
appstore_requestandappstore_list— that can call any endpoint with raw JSON:API documents.
Tools
| Group | Tools |
|---|---|
| Generic | appstore_request, appstore_list |
| Apps & metadata | list_apps, get_app, update_app, list_app_infos, update_app_info, set_age_rating, create_app_info_localization, update_app_info_localization |
| In-app purchases (v2) | list_in_app_purchases, create_in_app_purchase, update_in_app_purchase, delete_in_app_purchase, create_iap_localization, set_iap_price_schedule, upload_iap_review_screenshot |
| Subscriptions | list_subscription_groups, create_subscription_group, create_subscription, update_subscription, create_subscription_localization, set_subscription_price |
| Versions & metadata | list_app_store_versions, create_app_store_version, create_version_localization, update_version_localization |
| App Review submission | create_review_submission, add_review_submission_item, submit_review_submission, list_review_submissions, submit_in_app_purchase, set_app_review_detail, create_app_encryption_declaration, assign_build_encryption_declaration |
| Pricing | list_territories, list_iap_price_points, list_subscription_price_points |
| Availability | set_iap_availability, set_subscription_availability, set_app_availability |
| TestFlight | list_builds, list_beta_groups, create_beta_group, add_beta_tester, submit_build_for_beta_review, set_build_test_notes, set_build_beta_detail, set_beta_app_review_detail, expire_build, add_build_to_beta_group |
| Provisioning & signing | list_bundle_ids, create_bundle_id, enable_bundle_id_capability, disable_bundle_id_capability, list_certificates, create_certificate, list_devices, register_device, list_profiles, create_profile |
| Assets | upload_app_screenshot, upload_app_preview, create_screenshot_set, create_preview_set, delete_screenshot_set, delete_preview_set, reorder_screenshots |
| Subscription offers | create_introductory_offer, create_promotional_offer, create_winback_offer, list_winback_offers |
| Offer codes | create_offer_code, generate_one_time_use_codes, create_custom_offer_code, list_offer_codes |
| Promoted purchases | create_promoted_purchase, update_promoted_purchase, set_promoted_purchase_order, list_promoted_purchases |
| Customer reviews | list_customer_reviews, respond_to_review, delete_review_response |
| Phased release | start_phased_release, update_phased_release |
| Users & access | list_users, invite_user, update_user, remove_user |
| In-app events | create_app_event, create_app_event_localization, upload_app_event_screenshot |
| Xcode Cloud | list_ci_products, list_ci_workflows, start_ci_build, get_ci_build_run, list_ci_build_actions |
| Analytics reports | request_analytics_report, list_analytics_reports, list_analytics_report_instances, list_analytics_report_segments |
| Custom product pages | list_custom_product_pages, get_custom_product_page, create_custom_product_page, update_custom_product_page, delete_custom_product_page, list_custom_product_page_versions, create_custom_product_page_version, list_custom_product_page_localizations, create_custom_product_page_localization, update_custom_product_page_localization, create_cpp_screenshot_set, create_cpp_preview_set |
See docs/TOOLS.md for each tool's description and parameters. Custom product page
images are uploaded with the existing upload_app_screenshot / upload_app_preview tools.
Install
Prebuilt binaries for macOS (universal), Linux (x86-64), and Windows (x86-64) are attached to every GitHub Release. Pick the channel for your client; all of them need credentials (see Credentials).
Claude Desktop — one-click bundle
Download appstore-mcp.mcpb from the latest release and open it with Claude Desktop
(Settings → Extensions → Install Extension…, or drag the file onto the window).
It prompts for your Issuer ID, Key ID, and .p8 key file. The bundle ships
all three platforms' binaries and selects the right one automatically.
Claude Code — plugin marketplace
/plugin marketplace add forgeopslabs/appstore-mcp
/plugin install appstore-mcp@forgeopslabs
The plugin launches the appstore-mcp binary from your PATH, so install it first —
download the binary for your OS from the latest release
and put it on your PATH, or cargo install --git https://github.com/forgeopslabs/appstore-mcp.
Set ASC_ISSUER_ID, ASC_KEY_ID, and ASC_PRIVATE_KEY_PATH in the environment you start
Claude Code from.
Codex
Codex configures MCP servers directly (no marketplace). With appstore-mcp on your PATH:
codex mcp add appstore \
--env ASC_ISSUER_ID=... --env ASC_KEY_ID=... \
--env ASC_PRIVATE_KEY_PATH=/path/AuthKey_XXXXXX.p8 \
-- appstore-mcp
or in ~/.codex/config.toml:
[mcp_servers.appstore]
command = "appstore-mcp"
args = []
env = { ASC_ISSUER_ID = "...", ASC_KEY_ID = "...", ASC_PRIVATE_KEY_PATH = "/path/AuthKey_XXXXXX.p8" }
MCP Registry
Published as io.github.forgeopslabs/appstore-mcp (metadata in
server.json) so any MCP-aware client can discover it.
From source
cargo build --release # -> target/release/appstore-mcp
Credentials
Generate a Team Key in App Store Connect → Users and Access → Integrations →
App Store Connect API, and download the .p8 file. Then set:
| Variable | Required | Description |
|---|---|---|
ASC_ISSUER_ID |
✅ | Issuer UUID shown above the keys table. |
ASC_KEY_ID |
✅ | The API key's Key ID. |
ASC_PRIVATE_KEY |
one of | Inline .p8 PEM contents. |
ASC_PRIVATE_KEY_PATH |
one of | Path to the downloaded .p8 file. |
ASC_BASE_URL |
optional | Override the API origin. |
ASC_LOG |
optional | Log filter (to stderr). Default info. |
See .env.example. The server authenticates each request with a
short-lived ES256 JWT signed by your key (cached and refreshed automatically).
The server starts even without credentials so a client can list its tools; tool calls then return an actionable configuration error until creds are set.
Build & run
cargo build --release
ASC_ISSUER_ID=... ASC_KEY_ID=... ASC_PRIVATE_KEY_PATH=/path/AuthKey_XXX.p8 \
./target/release/appstore-mcp
The server speaks MCP over stdio. Logs go to stderr; stdout is the protocol channel.
Use with an MCP client
Example client config (e.g. Claude Desktop's mcpServers):
{
"mcpServers": {
"appstore": {
"command": "/absolute/path/to/appstore-mcp/target/release/appstore-mcp",
"env": {
"ASC_ISSUER_ID": "00000000-0000-0000-0000-000000000000",
"ASC_KEY_ID": "ABCD123456",
"ASC_PRIVATE_KEY_PATH": "/absolute/path/to/AuthKey_ABCD123456.p8"
}
}
}
}
Inspect with the MCP Inspector
npx @modelcontextprotocol/inspector ./target/release/appstore-mcp
Usage notes
- IDs are opaque. List/get first to resolve app, IAP, subscription, set, and price-point IDs, then pass them to create/update tools.
- Pricing needs a price point. Use
list_iap_price_points/list_subscription_price_pointsto get theidforset_iap_price_schedule/set_subscription_price. - Asset uploads (
upload_*) take a local file path and run the full reserve → chunked upload → MD5 commit flow in one call. Screenshots/previews require an existingappScreenshotSet/appPreviewSet; create those with the generic tools if needed. - Anything not listed is reachable via
appstore_request(raw method + path + JSON:API body) orappstore_list(paginated GET). Example:appstore_request { "method": "GET", "path": "/v1/apps/123/customerReviews" }. - Not covered: sales/finance report endpoints return gzipped TSV (not JSON:API) and are out of scope for these tools.
Limitations (enforced by Apple)
- You cannot create an app via the API. The
appsresource only allows GET and UPDATE —POST /v1/appsreturns403 FORBIDDEN_ERROR. Create the app record in the App Store Connect website (Apps → ➕ → New App); you can pre-create its bundle ID withcreate_bundle_id. All other tools operate on an existing app. - A deleted in-app purchase's
productIdis permanently reserved by Apple and cannot be reused.
Development
cargo test # unit tests (JWT signing, MD5, body builders)
cargo clippy --all-targets -- -D warnings
cargo fmt --check
Regenerate the tool reference after adding/changing tools (needs the release binary; no credentials required):
cargo build --release && python3 scripts/gen_tools_doc.py # rewrites docs/TOOLS.md
Live integration tests
scripts/integration_test.py drives the compiled server against the real API.
Read-only by default; --write adds a self-cleaning IAP lifecycle.
cargo build --release
# Credentials via env (ASC_ISSUER_ID/ASC_KEY_ID/ASC_PRIVATE_KEY_PATH) or local
# appstore-connect.txt + AuthKey_*.p8 in the repo root (both gitignored).
python3 scripts/integration_test.py --app <APP_ID> # read-only sweep
python3 scripts/integration_test.py --app <APP_ID> --write # + write lifecycle
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。