Other · Local MCP server
Appstore Connect MCP
MCP server for Apple Store Connect API integration with OAuth authentication support.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ryaker/appstore-connect-mcp- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2025-09-10
- Updated
- 2025-09-10
- Publisher
- ryaker (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ryaker) · how
- Repository
- github.com/ryaker/appstore-connect-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @ryaker/appstore-connect-mcp | 1.0.0 | stdio |
How to connect Appstore Connect MCP
Appstore Connect MCP runs locally from a Node.js package published to the npm registry: @ryaker/appstore-connect-mcp version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @ryaker/appstore-connect-mcp@1.0.0. It reads these environment variables: APPLE_KEY_ID (required, secret), APPLE_ISSUER_ID (required, secret), APPLE_PRIVATE_KEY (required, secret), APPLE_BUNDLE_ID, APPLE_APP_STORE_ID, OAUTH_ENABLED, OAUTH_ISSUER, OAUTH_AUDIENCE, OAUTH_JWKS_URI and SERVER_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"appstore-connect-mcp": {
"command": "npx",
"args": [
"-y",
"@ryaker/appstore-connect-mcp@1.0.0"
],
"env": {
"APPLE_KEY_ID": "<secret>",
"APPLE_ISSUER_ID": "<secret>",
"APPLE_PRIVATE_KEY": "<secret>",
"APPLE_BUNDLE_ID": "<value>",
"APPLE_APP_STORE_ID": "<value>",
"OAUTH_ENABLED": "<value>",
"OAUTH_ISSUER": "<value>",
"OAUTH_AUDIENCE": "<value>",
"OAUTH_JWKS_URI": "<value>",
"SERVER_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| ApproveKitAudit apps against App Store, Google Play and Google OAuth review rules; get the required docs. | Remote · HTTPLive check: ✓ handshake |
| appsflyer.comAnalyze your campaigns any way you want, with AI. | Remote · HTTPLive check: sign-in required |
| AppSkyline App RankingsTrack your apps' keyword rankings, reviews and store listings on App Store, Google Play and more. | Remote · HTTPLive check: ✓ handshake |
| Appstore ConnectMCP server for Apple's App Store Connect API. Manage apps, TestFlight, and more. | Local · stdio |
| Appstore Release MCPApp Store release pilot - version bump, TestFlight upload, metadata, review submission. | Local · stdio |
| Appstore ReviewsApple App Store reviews as structured JSON via the Apify Reviews API Actor, hosted MCP. | Remote · HTTPLive check: sign-in required |
| Appstore ScreenshotsGenerate professional App Store screenshots by matching any top app's style. | Local · stdio |
| AppStorePackCreate App Store screenshots, app icons and store copy, then push them to App Store Connect. | Remote · HTTPLive check: sign-in required |