Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words
Beginner mode Off
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode Off
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

Hamn

by idooversion 0.1.3i★ –iRuns on your computer
Registry nameio.github.idoo/hamn

Install

Overview

Description from the maker (original English)

MCP server for App Store Connect: releases, TestFlight, reviews, reports. Read-only by default.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: ASC_KEY_ID, ASC_PRIVATE_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: ASC_KEY_ID, ASC_ISSUER_ID, ASC_PRIVATE_KEY, ASC_VENDOR_NUMBER, HAMN_ALLOW_WRITES

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Download the maker’s .mcpb file

The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.

Run this in your terminal

claude mcp add hamn --env ASC_KEY_ID=your-value --env ASC_ISSUER_ID=your-value --env ASC_PRIVATE_KEY=your-value --env ASC_VENDOR_NUMBER=your-value --env HAMN_ALLOW_WRITES=your-value -- docker run -i --rm -e ASC_KEY_ID -e ASC_ISSUER_ID -e ASC_PRIVATE_KEY -e ASC_VENDOR_NUMBER -e HAMN_ALLOW_WRITES ghcr.io/idoo/hamn:0.1.3

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "hamn": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ASC_KEY_ID",
        "-e",
        "ASC_ISSUER_ID",
        "-e",
        "ASC_PRIVATE_KEY",
        "-e",
        "ASC_VENDOR_NUMBER",
        "-e",
        "HAMN_ALLOW_WRITES",
        "ghcr.io/idoo/hamn:0.1.3"
      ],
      "env": {
        "ASC_KEY_ID": "your-value",
        "ASC_ISSUER_ID": "your-value",
        "ASC_PRIVATE_KEY": "your-value",
        "ASC_VENDOR_NUMBER": "your-value",
        "HAMN_ALLOW_WRITES": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "hamn": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ASC_KEY_ID",
        "-e",
        "ASC_ISSUER_ID",
        "-e",
        "ASC_PRIVATE_KEY",
        "-e",
        "ASC_VENDOR_NUMBER",
        "-e",
        "HAMN_ALLOW_WRITES",
        "ghcr.io/idoo/hamn:0.1.3"
      ],
      "env": {
        "ASC_KEY_ID": "your-value",
        "ASC_ISSUER_ID": "your-value",
        "ASC_PRIVATE_KEY": "your-value",
        "ASC_VENDOR_NUMBER": "your-value",
        "HAMN_ALLOW_WRITES": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • ASC_KEY_ID required env
    App Store Connect API key ID
  • ASC_ISSUER_ID env
    Issuer ID (omit for an Individual API key)
  • ASC_PRIVATE_KEY secret required env
    Contents of the .p8 key (PEM or base64 PEM)
  • ASC_VENDOR_NUMBER env
    Vendor number for sales and finance reports
  • HAMN_ALLOW_WRITES env
    Set to 1 to expose write and destructive tools

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account idoo, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32545 servers in this category
  • Published to the registry more recently than 75% of the other 32545 servers in this category
  • Basic checks equal to or better than 100% of the other 32545 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Hamn safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: ASC_KEY_ID, ASC_PRIVATE_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 12 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB, Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Python MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Python MCP

by Files-com

Local-only Python MCP server for the Files.com API.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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):

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 for store_lookup. 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:

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 oneforgeopszelentsovJoshua (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, 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 and replying to App Review each wait for your yes. Details in docs/CONFIG.md.

License

MIT © Ivan Verevkin

Ask PopNx