App Store Connect MCP server
Commit Nov 15, 2026Allows an AI agent to manage App Store Connect accounts, including releases, TestFlight, reviews, and sales reports.
Also known as idoo/hamn
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.3
- Last commit
- Nov 15, 2026
- License
- MIT
What is App Store Connect MCP?
App Store Connect allows an AI agent to manage App Store Connect accounts, including releases, TestFlight, reviews, and sales reports.
Summary generated from the project's README
About App Store Connect MCP server
Hamn provides an interface for AI agents to manage App Store Connect accounts through the Model Context Protocol. It allows developers to use clients like Claude, Cursor, or VS Code to handle app releases, TestFlight builds, metadata, reviews, and sales reports. The server operates as a single binary that works across different operating systems.
By default, the server runs in a read-only mode to ensure safety. It requires an App Store Connect API key for standard operations, which can be added via the auth command. For advanced tasks like creating new app records or managing App Privacy, users can enable the web toolset through a browser-based login process. This setup keeps sensitive credentials in the OS keychain or environment variables rather than within the agent itself. The system is designed to ask for permission before performing any public or irreversible actions.
What you can do with it
- 1Manage app releasesAn AI agent can handle the entire release process including metadata and screenshots.
- 2Monitor post-release healthDevelopers can use the insights toolset to track analytics funnels and keyword rankings.
- 3Respond to App ReviewThe agent can read rejection messages and draft replies in the Resolution Center.
- 4Analyze sales and performanceUsers can request summaries of app impressions, downloads, and sessions.
Written from the project's README. Every use case is checked against a quote from it.
How to install App Store Connect MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall App Store Connect MCP in Claude Code
$ claude mcp add --env 'ASC_PRIVATE_KEY=<YOUR_ASC_PRIVATE_KEY>' --env 'ASC_KEY_ID=<ASC_KEY_ID>' hamn -- docker run -i --rm ghcr.io/idoo/hamn:0.1.3Install App Store Connect MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"hamn": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/idoo/hamn:0.1.3"
],
"env": {
"ASC_PRIVATE_KEY": "<YOUR_ASC_PRIVATE_KEY>",
"ASC_KEY_ID": "<ASC_KEY_ID>"
}
}
}
}Install App Store Connect MCP in VS Code
.vscode/mcp.json
{
"servers": {
"hamn": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/idoo/hamn:0.1.3"
],
"env": {
"ASC_PRIVATE_KEY": "<YOUR_ASC_PRIVATE_KEY>",
"ASC_KEY_ID": "<ASC_KEY_ID>"
}
}
}
}Install App Store Connect MCP in VS Code CLI
$ code --add-mcp '{"name":"hamn","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/idoo/hamn:0.1.3"],"env":{"ASC_PRIVATE_KEY":"<YOUR_ASC_PRIVATE_KEY>","ASC_KEY_ID":"<ASC_KEY_ID>"}}'Install App Store Connect MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"hamn": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/idoo/hamn:0.1.3"
],
"env": {
"ASC_PRIVATE_KEY": "<YOUR_ASC_PRIVATE_KEY>",
"ASC_KEY_ID": "<ASC_KEY_ID>"
}
}
}
}Install App Store Connect MCP in Codex
$ codex mcp add hamn --env 'ASC_PRIVATE_KEY=<YOUR_ASC_PRIVATE_KEY>' --env 'ASC_KEY_ID=<ASC_KEY_ID>' -- docker run -i --rm ghcr.io/idoo/hamn:0.1.3Install App Store Connect MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.hamn] command = "docker" args = ["run", "-i", "--rm", "ghcr.io/idoo/hamn:0.1.3"] [mcp_servers.hamn.env] ASC_PRIVATE_KEY = "<YOUR_ASC_PRIVATE_KEY>" ASC_KEY_ID = "<ASC_KEY_ID>"
Install App Store Connect MCP in Gemini CLI
$ gemini mcp add -s user -e 'ASC_PRIVATE_KEY=<YOUR_ASC_PRIVATE_KEY>' -e 'ASC_KEY_ID=<ASC_KEY_ID>' hamn docker -- run -i --rm ghcr.io/idoo/hamn:0.1.3Install App Store Connect MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"hamn": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/idoo/hamn:0.1.3"
],
"env": {
"ASC_PRIVATE_KEY": "<YOUR_ASC_PRIVATE_KEY>",
"ASC_KEY_ID": "<ASC_KEY_ID>"
}
}
}
}Configuration
ASC_PRIVATE_KEYRequiredSecretContents of the .p8 key (PEM or base64 PEM)
ASC_KEY_IDRequiredApp Store Connect API key ID
ASC_ISSUER_IDIssuer ID (omit for an Individual API key)
ASC_VENDOR_NUMBERVendor number for sales and finance reports
HAMN_ALLOW_WRITESSet to 1 to expose write and destructive tools
| Name | Description | |
|---|---|---|
| ASC_PRIVATE_KEY | Contents of the .p8 key (PEM or base64 PEM) | RequiredSecret |
| ASC_KEY_ID | App Store Connect API key ID | Required |
| ASC_ISSUER_ID | Issuer ID (omit for an Individual API key) | |
| ASC_VENDOR_NUMBER | Vendor number for sales and finance reports | |
| HAMN_ALLOW_WRITES | Set to 1 to expose write and destructive tools |
Automated checks
Ran Nov 13, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableidoo/hamn is public and reachablegithub.com/idoo/hamn ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-11github.com/idoo/hamn ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the modelInstruction aimed at the model found in the description or READMEFinding
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubapp-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):
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:
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 forstore_lookup. Afterweb loginit also readsappstoreconnect.apple.com(App Analytics, Payments, thewebtoolset) 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:
gh attestation verify app-store-connect-mcp_<version>_<os>_<arch>.tar.gz --repo idoo/app-store-connect-mcp
or with cosign:
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.
Compared
| this one | forgeops | zelentsov | Joshua (archived) | asc |
|
|---|---|---|---|---|---|
| MCP | + | + | + | + | − |
| Read-only default | + | − | − | − | − |
| Asks before publishing | + | − | ~ | − | ~ |
| Injection guard | + | − | − | − | − |
| Release preflight | + | − | ~ | − | + |
| Sales reports | + | − | + | + | + |
| One binary, any OS | + | + | − | − | + |
~ partial
Security
It can't break anything until you let it. Anything public, money-moving or hard to undo for your users and team waits for your yes. Build uploads and Xcode Cloud branch runs don't ask; pull request runs do. A 1-star review that says "ignore previous instructions" is still just a 1-star review. More in docs/SAFETY.md.
What it does
Everything you'd click in App Store Connect: releases, TestFlight, listings, screenshots, reviews, sales, IAPs, signing, Xcode Cloud. For everything else there's raw API access. Tool list, config.
After launch it keeps watching, if you turn on the insights toolset: post-release health with a guard that pauses a phased rollout from cron, a "what's new since yesterday" digest, the analytics funnel, and keyword rank tracking. In Claude Desktop, claude.ai, ChatGPT and VS Code the release checklist, metadata diffs, screenshots, reviews and funnel show up as small interactive views.
A toolset is a group of tools you switch on or off, so your agent only sees what you use. The release, TestFlight, metadata, reviews, reports and screenshots ones are on out of the box. Add others with --toolsets +insights,+signing or ASC_MCP_TOOLSETS=+insights, or ask the agent to turn one on mid-chat. The list is in docs/CONFIG.md.
Stats without an Admin key or vendor number
Apple's Analytics Reports need an Admin key and a day or two before the first numbers, and sales need the vendor number, which the API doesn't expose. After app-store-connect-mcp web login neither matters: the vendor number is read from Payments once and remembered, and analytics_funnel_report and insights_summary read App Analytics the way the website does. insights_summary without an app lists every app's impressions, page views, downloads, sessions and crashes against the previous period.
Creating apps and App Privacy
Apple's API can't create an app record or fill in App Privacy. The opt-in web toolset can, through your Apple ID instead of the API key. You sign in once:
app-store-connect-mcp web login
A browser window opens on Apple's own sign-in page. Type your password, approve 2FA or use a passkey, and the window closes by itself. It's a separate browser profile just for this: your default browser if it's Brave, Chrome, Edge or Arc, another one of those if it isn't, or a downloaded Chrome for Testing when you have none. When the session runs out later, the same profile renews it headless, so mostly you won't see a window again. An agent can open the window too, with the web_login tool, when a tool says web_session_required.
Apple drops a session that sits unused for a day or so. To keep it alive, run this once:
app-store-connect-mcp web keepalive --install
It touches the session every 30 minutes (a LaunchAgent on macOS; elsewhere it prints a cron line). If Apple still wants you, you get one notification per dead session. The sign-in window, from web login or web_login, also posts a notification and waits 30 minutes.
No screen? web login --password keeps the old terminal flow (Apple ID, password, 2FA code), though Apple often refuses it with error -20209. On an SSH box, use web import with the cookies from a browser's "Copy as cURL" or a FASTLANE_SESSION.
Then turn the toolset on (--toolsets +web) and ask for apps_create, privacy_get, privacy_plan, privacy_apply, medical_device_get and medical_device_set (the "not a regulated medical device" declaration Apple wants from Health & Fitness and Medical apps), release_review_messages (what App Review wrote about a rejection) and release_review_reply (answer App Review in the Resolution Center). The agent never sees your Apple ID, password or cookies: the cookies stay in your Keychain and the password isn't stored anywhere. Creating an app, publishing App Privacy, declaring the medical device status and replying to App Review each wait for your yes. Details in docs/CONFIG.md.
License
MIT © Ivan Verevkin
App Store Connect MCP questions
How do I add App Store Connect MCP to Claude Code?
Run claude mcp add --env 'ASC_PRIVATE_KEY=<YOUR_ASC_PRIVATE_KEY>' --env 'ASC_KEY_ID=<ASC_KEY_ID>' hamn -- docker run -i --rm ghcr.io/idoo/hamn:0.1.3 in your terminal. Add --scope user to make it available in every project.
How do I add App Store Connect MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Is the server read-only?
Yes, it is read-only by default and requires explicit permission before performing any write actions or making anything public.
How can I use the web toolset for creating apps?
You can use the opt-in web toolset by running 'app-store-connect-mcp web login', which uses your Apple ID to perform actions the standard API cannot, such as creating app records.