idoo/app-store-connect-mcp

MCP server for App Store Connect. MCP is the plug-in format AI clients like Claude, Cursor and Codex use, so with this one your agent can read and manage your App Store Connect account. Read-only by default, and it asks before anything goes public. The binary is app-store-connect-mcp.
## Install
Paste this into whatever AI is writing your app right now (we won't tell):
text
Set up the app-store-connect-mcp server for me: https://github.com/idoo/app-store-connect-mcp/blob/main/docs/INSTALL.md
Or by hand, in three steps:
sh
curl -fsSL https://github.com/idoo/app-store-connect-mcp/releases/latest/download/install.sh | sh # or: brew install idoo/tap/app-store-connect-mcp
app-store-connect-mcp auth add # asks for your API key, tests it with Apple
app-store-connect-mcp config install claude-code # or claude-desktop, cursor, codex, vscode, windsurf
Details in docs/INSTALL.md. Upgrading, key rotation and fixes for common errors: docs/FAQ.md.
## Why you can trust it
You're handing it an App Store Connect key, so here's what you can check yourself instead of taking my word for it:
All of it is here. MIT, no closed parts. Build it yourself with go install github.com/idoo/app-store-connect-mcp/cmd/app-store-connect-mcp@latest.
Read-only until you say otherwise. Write tools aren't even listed until you turn writes on, and anything public or hard to undo shows a preview and waits for your yes. docs/SAFETY.md
No telemetry. It talks to api.appstoreconnect.apple.com, the presigned upload and report URLs Apple hands back (sent without your token), and the public iTunes Search API for storelookup. After web login it also reads appstoreconnect.apple.com (App Analytics, Payments, the web toolset) and Apple's own sign-in pages. The JWT is signed on your machine and only ever goes to the API. SECURITY.md
Your key stays where you put it. It's read from a file, an env var or the OS keychain. The config holds only a path or keychain reference, is written 0600, and is refused if anyone else can write to it. Apple ID cookies live in the Keychain. No MCP tool can add or change credentials.
Releases are signed and traceable to their source. Every release is built by release.yml from a tag, published as an immutable release, and ships an SPDX SBOM per archive, a cosign keyless signature on checksums.txt, and build provenance attestations. The macOS binaries are also signed with my Developer ID and notarized by Apple, so Gatekeeper opens them without a warning.
CI scans every push with CodeQL and govulncheck, and a tag can't ship with a known reachable vulnerability.
Check a download with the GitHub CLI:
sh
gh attestation verify app-store-connect-mcp .tar.gz --repo idoo/app-store-connect-mcp
or with cosign:
sh
cosign verify-blob --bundle checksums.txt.sigstore.json \
--certificate-identity-regexp '^https://github.com/idoo/app-store-connect-mcp/\.github/workflows/release\.yml@refs/tags/v' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com checksums.txt
shasum -a 256 -c checksums.txt --ignore-missing
On a Mac, spctl -a -vv -t install app-store-connect-mcp should say source=Notarized Developer ID.
The .mcpb and tools.json are listed in checksums-extra.txt with their own checksums-extra.txt.sigstore.json. Both checks above work on them the same way.