appstore-mcp
Manages App Store Connect metadata, in-app purchases, screenshots, custom product pages, and app previews from YAML files.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@appstore-mcpexport current in-app purchases to YAML"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
appstore-flow
A CLI + bundled MCP server for managing App Store Connect metadata, screenshots, and in-app purchases from YAML files. Designed for teams that want their store listing under version control instead of click-driven through the App Store Connect website.
📖 Documentation: https://zmij.github.io/appstore-cli/ (llms.txt available for agents at /llms.txt)
Naming note. The npm package is
appstore-flow. The GitHub repo iszmij/appstore-cliand the docs site lives atzmij.github.io/appstore-cli/— slugs kept from before the rebrand so existing links keep working. The local config filenameappstore-cli.config.yamlis also a legacy holdover.
What it does:
Pull every per-locale listing, IAP, subscription, custom-product-page, and screenshot summary into committed YAML.
Push YAML edits back to ASC: localised copy, prices, availability, subscription intro offers, review screenshots.
Create new IAPs and subscriptions from YAML.
Two-way reconcile: pull live state into committed YAML without overwriting hand-edits; field-level diff with paths like
subscriptions/my_sub/intro_offers/FREE_TRIAL+ONE_WEEK+1+__global/start_date.Migrate existing subscribers when a price changes.
Same code is exposed as an MCP server so an agent can read/list/update store state without shelling out.
Originally extracted from a working Lazy Sudoku setup. Defaults match that layout (
.secret-stuff/+l10n/metadata/apple/); downstream projects can either adopt the same conventions (no config needed) or override viaappstore-cli.config.yaml/ env vars — see Configuration.
Install
npm install -g appstore-flow
# or, from a checkout (the GitHub repo is still `appstore-cli` — only the
# npm package name has been rebranded to `appstore-flow`):
git clone https://github.com/zmij/appstore-cli.git
cd appstore-cli && npm install && npm run build && npm linkRelated MCP server: asc-mcp
Authentication
You need an App Store Connect API key. The .p8 file plus the issuer ID + app ID go in a config file:
# .secret-stuff/appstore-config.yaml (gitignored — never commit)
issuer_id: "8a8a8a8a-1234-5678-9abc-def012345678"
app_id: "1234567890"
keys:
app_manager:
key_id: "ABCDE12345"
key_file: "AuthKey_ABCDE12345.p8"
build_upload:
key_id: "FGHIJ67890"
key_file: "AuthKey_FGHIJ67890.p8"
default_key: "app_manager"Multiple keys let you separate concerns (one for build uploads, one for metadata edits). Pick a non-default key per call with --key-id.
See docs/auth.md for key creation and the JWT lifecycle.
Configuration
The defaults match the layout this tool was extracted from:
What | Default | Where |
Secrets directory |
| Holds |
Metadata directory |
| Holds |
To override, drop an appstore-cli.config.yaml at the worktree root (preferred) or project root:
# appstore-cli.config.yaml
secrets_dir: config/appstore-secrets # relative to project root
metadata_dir: store-metadata/apple # relative to worktree rootEnv vars win over the file:
APPSTORE_SECRETS_DIR=/path/to/secrets
APPSTORE_METADATA_DIR=/path/to/metadataThe CLI uses git to find the project root (so secrets live with the main repo, not in worktrees) and the worktree root (so per-branch metadata edits stay local).
Quickstart
# 1. Pull current ASC state into YAML
appstore iap export --output l10n/metadata/apple/iap.yaml
# 2. Edit the YAML in your editor
$EDITOR l10n/metadata/apple/iap.yaml
# 3. Preview the push
appstore iap sync --dry-run
# 4. Push
appstore iap syncSame flow for listings:
appstore listings update --all --dry-run
appstore listings update --allSee docs/workflow.md for the full export → edit → sync → pull loop.
Commands
App + version info
appstore info # bundle ID, name, SKU, primary locale
appstore versions list # all app versionsListings
appstore listings list --version-id X
appstore listings show --lang en-GB
appstore listings update --all [--dry-run]
appstore listings update --lang en-GB --field whats_new
appstore listings diff # YAML vs liveIn-App Purchases + subscriptions
appstore iap list # quick stats
appstore iap show <productId> # full detail
appstore iap export --output l10n/metadata/apple/iap.yaml # overwrites file
appstore iap sync [--product-id X] [--dry-run] # YAML → ASC
appstore iap create [--product-id X] [--dry-run] # provision new
appstore iap pull [--product-id X] [--dry-run] # ASC → YAML (additive)
appstore iap diff [--product-id X] # field-level divergence
appstore iap migrate-prices --product-id X [--territory T] [--confirm]Subscriptions, subscription groups, intro offers, review screenshots all round-trip through iap.yaml. See docs/iap-schema.md for the YAML schema.
Screenshots
appstore screenshots list --lang en-GB
appstore screenshots upload --source ./shots --lang en-GB --mode replace
appstore screenshots upload --source ./shots --all --mode replace
appstore screenshots reorder --allModes: replace (drop + re-upload), add (append), reorder (no upload, reorder existing).
Custom Product Pages
appstore pages listApp Previews (video)
appstore previews list --lang en-GB
appstore previews upload --source ./reels --lang en-GBMCP Server
The package ships a bundled MCP server (appstore-mcp) using the same client code as the CLI. Any MCP-aware agent — Claude Code, Cursor, Windsurf, Cline, Continue, Zed — can talk to it over stdio.
Prerequisites
appstore-mcp must be on $PATH. The Install step puts it there (either npm install -g appstore-flow or npm link from a checkout). Verify:
which appstore-mcpIf you'd rather not install globally, register an absolute path instead — see below.
Register with Claude Code
# Run from the project whose store listing you manage — that becomes the
# server's working directory, which is where config + metadata YAMLs are
# resolved from. See "Working directory and auth" below.
claude mcp add appstore appstore-mcpclaude mcp add defaults to local scope (your account, this directory). Pick the scope that fits:
Scope | Where it's stored | Use when |
|
| Personal experiments in one repo |
|
| Everyone in the repo gets it |
|
| You want it everywhere |
If you skipped npm link, register the build output directly:
claude mcp add appstore node /absolute/path/to/appstore-cli/build/mcp/server.jsRegister with other MCP clients
Clients that read a JSON config (Cursor, Windsurf, Cline, Continue, Zed, …) take this shape. Point command at the binary on $PATH, or use an absolute path:
{
"mcpServers": {
"appstore": {
"command": "appstore-mcp"
}
}
}Consult your client's docs for where this config file lives — common paths are ~/.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, or a workspace-level file.
Working directory and auth
The MCP server inherits its working directory from the client that spawns it. Path resolution (where appstore-config.yaml and metadata YAMLs live) starts from git rev-parse --show-toplevel of that cwd, with one refinement: when the server detects it's running inside a git submodule (via git rev-parse --show-superproject-working-tree), it resolves paths against the parent worktree instead of the submodule's own root.
Practical implications:
Launch your MCP client from the repo whose store listing you manage. The server then finds
.secret-stuff/appstore-config.yamland the metadata YAMLs from there.If your client launches from somewhere else, override paths via env vars passed through the client config:
{
"mcpServers": {
"appstore": {
"command": "appstore-mcp",
"env": {
"APPSTORE_SECRETS_DIR": "/abs/path/to/secrets",
"APPSTORE_METADATA_DIR": "/abs/path/to/metadata"
}
}
}
}See Configuration for the full env var list.
Verify
claude mcp listThen in a session, ask the agent to call appstore_get_app_info — the first tool call confirms wiring. An "auth failed" error means wiring is fine and you just need a valid appstore-config.yaml.
Tools exposed
Tool | Description |
| Bundle ID, name, SKU, primary locale, relationships |
| All app versions |
| Per-locale metadata (with |
| One locale on the editable version |
| Patch one locale's fields (only supplied fields touched) |
| All in-app purchases |
| All subscription groups |
| All custom product pages |
| Per-locale × per-device screenshot counts |
Auth + paths come from the same config files as the CLI; no separate setup.
Key selection
Priority order:
--key-id <name>flagAPPSTORE_KEY_IDenv vardefault_keyfrom the config file
# Use a specific key
appstore versions list --key-id build_uploadApple quirks worth knowing
The Apple side has several non-obvious gotchas the CLI works around. Captured in docs/quirks.md:
Edit sessions are listings-only. IAPs and subscriptions skip the session.
preserveCurrentPriceis the migration discriminator.iap syncwritestrue(new subscribers only);iap migrate-priceswritesfalse(existing too).Subscription price points are per-territory. No "auto-equalise everywhere" call — the anchor migration only affects the anchor's territory.
Apple chooses the consent flow from the price delta. Decreases auto-apply; increases trigger Apple's notification + opt-in flow.
subscriptionPrices.createrequires picking a tier price point ID — you can't pass a free-form$4.99. The CLI finds the matching tier for you.
Project layout
appstore-cli/
├── src/
│ ├── auth.ts # config loading + JWT
│ ├── client.ts # SDK wrapper (read + write methods)
│ ├── paths.ts # secrets + metadata path resolution
│ ├── project.ts # git-root discovery
│ ├── types.ts # YAML schema types
│ ├── index.ts # CLI entry (commander)
│ ├── commands/ # one file per command group
│ └── mcp/server.ts # MCP server (stdio)
├── docs/ # auth / workflow / iap-schema / listings-schema / quirks
├── package.json # bin: appstore + appstore-mcp
└── README.md # this fileContributing
See CLAUDE.md for agent-facing development notes.
For human contributors: PRs welcome. Run npx tsc --noEmit to typecheck. There are no unit tests yet — verify against a real ASC account via --dry-run flags first.
Adopters
I built this to manage Lazy Sudoku's App Store listing — 14 locales, 12 IAP products across 173 territories of pricing, plus subscription groups with intro offers. Editing YAML in my editor and running
appstore listings sync/appstore iap syncis dramatically less error-prone than clicking through App Store Connect's per-locale tabs, and lets every store change land via normal PR review.— Sergei Fedorov, Lazy Sudoku
Using appstore-flow somewhere? Open a PR adding yourself to this section.
Licence
MIT.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zmij/appstore-cli'
If you have feedback or need assistance with the MCP directory API, please join our Discord server