All servers / Developer / App Store Connect MCP server
App Store Connect MCP server
App Store Connect MCP server: your AI agent ships your iOS app, from a new bundle id to App Store review. A fastlane alternative for AI agents. 44 tools: regist
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-19 on package version 1.14.0. Package: @pofky/asc-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (3.3 seconds including download)
- Tools offered: 3
- Last published: 2026-11-18
- Weekly downloads (npm): 1,274
- License: MIT · Direct dependencies: 2
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
asc_setup_checkno parametersDiagnose your setup: checks the .p8 key, Key ID, Issuer ID, a LIVE authenticated connection to App Store Connect, and your license tier. For anything wrong, returns the exact fix. Run this first if something isn't working. Free.
asc_guide1 of 1 parameter describedSTART HERE. Returns the exact end-to-end playbook for an App Store task, with every manual ASC-website/Xcode step that no API can do flagged inline. Free.
asc_connect2 of 2 parameters describedConnect the user's App Store Connect account from this chat, so no config file or terminal is needed. Ask the user for their Issuer ID (the UUID above the keys list at https://appstoreconnect.apple.com/access/integrations/api); never invent one. It finds their downloaded AuthKey_XXXXXXXXXX.p8 (in ~/.appstoreconnect/private_keys, ~/Downloads or ~/Desktop) and moves it into ~/.appstoreconnect/private_keys, tests the pair against Apple, saves the Issuer ID in ~/.asc-mcp/credentials.json, and unlocks every tool in this session. Free.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.