Appstore Connect MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 62 installs a week from npm. Last commit 28 Aug 2026.
MCP server for Apple Store Connect API integration with OAuth authentication support
What the code does
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
result = subprocess.run(
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add appstore-connect-mcp -e 'APPLE_KEY_ID=<APPLE_KEY_ID>' -e 'APPLE_ISSUER_ID=<APPLE_ISSUER_ID>' -e 'APPLE_PRIVATE_KEY=<APPLE_PRIVATE_KEY>' -- npx -y @ryaker/appstore-connect-mcp{
"mcpServers": {
"appstore-connect-mcp": {
"command": "npx",
"args": [
"-y",
"@ryaker/appstore-connect-mcp"
],
"env": {
"APPLE_ISSUER_ID": "<APPLE_ISSUER_ID>",
"APPLE_KEY_ID": "<APPLE_KEY_ID>",
"APPLE_PRIVATE_KEY": "<APPLE_PRIVATE_KEY>"
}
}
}
}[mcp_servers.appstore-connect-mcp]
command = "npx"
args = ["-y", "@ryaker/appstore-connect-mcp"]
env = { APPLE_KEY_ID = "<APPLE_KEY_ID>", APPLE_ISSUER_ID = "<APPLE_ISSUER_ID>", APPLE_PRIVATE_KEY = "<APPLE_PRIVATE_KEY>" }{
"mcpServers": {
"appstore-connect-mcp": {
"command": "npx",
"args": [
"-y",
"@ryaker/appstore-connect-mcp"
],
"env": {
"APPLE_ISSUER_ID": "<APPLE_ISSUER_ID>",
"APPLE_KEY_ID": "<APPLE_KEY_ID>",
"APPLE_PRIVATE_KEY": "<APPLE_PRIVATE_KEY>"
}
}
}
}{
"servers": {
"appstore-connect-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ryaker/appstore-connect-mcp"
],
"env": {
"APPLE_ISSUER_ID": "<APPLE_ISSUER_ID>",
"APPLE_KEY_ID": "<APPLE_KEY_ID>",
"APPLE_PRIVATE_KEY": "<APPLE_PRIVATE_KEY>"
}
}
}
}Put your own values in place of
<APPLE_KEY_ID> (Apple App Store Connect API Key ID), <APPLE_ISSUER_ID> (Apple App Store Connect Issuer ID), <APPLE_PRIVATE_KEY> (Apple App Store Connect Private Key (base64 encoded or raw)).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
APPLE_BUNDLE_ID (Optional: Specific Bundle ID to filter apps), APPLE_APP_STORE_ID (Optional: Specific App Store ID), OAUTH_ENABLED (Enable OAuth authentication (true/false)), OAUTH_ISSUER (OAuth issuer URL (e.g., https://your-tenant.auth0.com)), OAUTH_AUDIENCE (OAuth audience URL), OAUTH_JWKS_URI (OAuth JWKS URI for token validation), SERVER_URL (Server URL for OAuth deployment).
Alternatives to Appstore Connect MCP
same job, measured the same wayMCP server for Google Docs integration with OAuth2 and service account support.
MCP server for SSH remote server management with SSH agent authentication support.
Lean Gmail MCP server with auto authentication support
MCP server for Redmine API integration with AI agents.
MCP server for Backlog API integration with AI agents.
MCP server for Azure API integration
MCP server for Chanty API integration
MCP server for UiPath API integration
Appstore Connect MCP — questions
Answers built from our own checks of this server.