Mağaza MCP
App Store Connect and Google Play, in one MCP server. Let your AI assistant manage both stores.
Potencia tu agente
Instalación del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
Aún no hay una versión empaquetada en el registro. Sigue el README del repositorio.
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirYou don't type anything into a terminal to install this. Drop this line on your AI assistant, it handles the rest:
https://github.com/tunaarikaya/magaza-mcp — install this, read AGENTS.md
You: How much is Nota Defteri's monthly subscription on App Store vs. Play in Turkey?
Assistant: ₺129.99 on the App Store, ₺99.99 on Play. Play is noticeably cheaper — if you want the same price in both stores, you need to update the base plan on Play.
No other MCP server can answer that in a single call, because they all look at
one store. magaza-mcp sees both at once.
No server sits in the middle: the package runs on your own machine, talks
directly to Apple and Google, and your keys never leave your Keychain.
Almost every MCP server on the market covers a single store. If you want both, you install two separate servers, juggle two separate tool sets, and manually stitch together any question that needs a comparison.
The real win isn't more tools: it's tools that can query both stores in the same call, which is only possible once both are in one server.
Tell your assistant (Claude Code, Antigravity, Cursor, Codex, Gemini CLI…):
https://github.com/tunaarikaya/magaza-mcp — install this, read AGENTS.md
The assistant reads AGENTS.md and handles the entire setup. All you do is answer its questions:
You › https://github.com/tunaarikaya/magaza-mcp — install this, read AGENTS.md
Assistant › Looking for your keys on this machine...
Found two keys:
App Store : ~/Downloads/AuthKey_ABC123DEFG.p8 (Key ID ABC123DEFG)
Play : ~/.config/play/account.json ([email protected]...)
Want me to use these? If there's another file, tell me the path,
or copy the key and paste it — either works.
You › yes, use them
Assistant › I need the Issuer ID for App Store. It's the UUID above the key
list on App Store Connect → Users and Access → Integrations.
You › 69a6de70-0000-0000-0000-000000000000
Assistant › ✓ App Store Connect connected — 4 apps found
✓ Google Play connected — 3 apps found
✓ Registered in Claude Code and Antigravity settings
Restart Claude Code, then ask:
"List my apps across both stores"
If it can't find your key, it will ask you how to proceed: give it the file path, copy the key to your clipboard, or — if you don't have a key yet — it'll walk you through getting one step by step.
[!IMPORTANT] The assistant never sees the contents of your key. It runs the setup, but the commands take the file's path, read its contents themselves, and write it straight into the Keychain. Even when you paste the key via clipboard (
pbpaste | …), the content flows through a pipe and never enters the assistant's context. AGENTS.md tells the assistant this explicitly.
After setup, restart any open applications — MCP servers only load at startup.
Your existing config is left untouched — only the magaza-mcp entry is
added or updated, a .magaza-mcp-yedek backup is taken before every write,
and the write itself is atomic.
If you're not using an assistant, a wizard does the same job:
npx magaza-mcp kur
Mağaza MCP setup
App Store Connect + Google Play, in one setup
1. Which stores should we connect?
App Store Connect (iOS / macOS)? [Y/n] y
Google Play (Android)? [Y/n] y
2. App Store Connect key
Key ID: ABC123DEFG
Issuer ID: 00000000-0000-0000-0000-000000000000
Path to .p8 file: ~/Downloads/AuthKey_ABC123DEFG.p8
Connecting to Apple... ✓ 4 apps found
✓ Key saved (macOS Keychain)
3. Google Play service account
Path to service account JSON: ~/.config/play/account.json
Connecting to Google... ✓ 3 apps found
✓ Key saved (macOS Keychain)
4. Which clients should it be installed to?
Claude Code? [Y/n] y
Antigravity (IDE + CLI)? [Y/n] y
Cursor? [y/N] n
Setup complete.
Keys are never written to the config file. On macOS they're saved to the
Keychain; the config file only gets which stores are enabled (MAGAZALAR).
On systems without Keychain access, it falls back to a file with 0600
permissions.
npx magaza-mcp tara # Search the machine for .p8 and service account keys
npx magaza-mcp anahtar ... # Verify a key and write it to the vault (below)
npx magaza-mcp kaydet # Register the server in clients' configs
npx magaza-mcp durum # Show what's connected (--json for machine-readable)
npx magaza-mcp araclar # List installed tools (✎ = can modify data)
npx magaza-mcp kur # Manual setup wizard
npx magaza-mcp surum # Print version
npx magaza-mcp yardim # Help
Registering a key (the command-line equivalent of the wizard's Q&A step):
npx magaza-mcp anahtar --apple-p8 ~/Downloads/AuthKey_ABC123DEFG.p8 \
--issuer-id 69a6de70-0000-0000-0000-000000000000
npx magaza-mcp anahtar --play-json ~/.config/play/account.json
pbpaste | npx magaza-mcp anahtar --play-json - # from clipboard, no file
npx magaza-mcp anahtar --sil appstore # remove from the vault
If --key-id isn't given, it's read from the filename. A key is never
written to the vault without being verified against Apple/Google with a real
request; if verification fails, the existing key in the vault is left
untouched.
No — and that's not an accident, it's the design itself.
1. Tool names are separated by prefix. Every tool going to App Store
starts with appstore__, every tool going to Play starts with play__. A
tool never talks to both APIs. There's no shared name, so there's nothing to
mix up.
2. Tools for the store you didn't pick are never loaded. On startup, the
server reads the MAGAZALAR variable and builds the tool list from it — the
other store's tools aren't even loaded into memory, aren't shown to the
model, and cost zero tokens.
3. Cross-store tools only exist when both stores are enabled. In a single-store setup they're never created at all — they'd have no meaning.
4. The dispatch tools know their scope too. The magaza parameter on
magaza__endpoint_ara and magaza__cagir is an enum that only accepts the
stores you've set up. If you only installed Play, the model can't make a call
with magaza: "appstore" — the schema doesn't allow it.
The app names in the examples are made up; you'd use your own app's name.
Both stores at once
App Store
Google Play
Apple terminates developer accounts every year for spam, copycat apps and review manipulation — and many developers find out only when the email arrives. Most of them never knew they were doing anything wrong: the same screenshots in five apps, "Instagram" in the keywords, someone else's copyright left over from a template.
appstore__hesap_sagligi scans the whole account and scores the risk from
0 to 100:
You › Is my developer account safe?
Assistant › ACCOUNT RISK: 72/100 🔴 HIGH
Clones / spam (4.3) ██████████ critical (3)
Metadata & trademarks (2.3/5.2) █████░░░░░ high (4)
Reviews & money (5.6/3.1) ██░░░░░░░░ low (2)
Review history & account ██████░░░░ medium (3)
1. [CRITICAL] Same screenshots in 6 apps
2. [HIGH] Photo Pro: "instagram" in the keywords
3. [HIGH] 3 apps carry someone else's copyright
…
Every finding comes with the Apple guideline, why it's risky and the steps to fix it.
Fixing. Findings marked automatic can be fixed with
appstore__hesap_duzelt. It always shows the change first and only writes
with onayla=true:
appstore__hesap_duzelt(bulgular: ["anahtar-marka:1234567:en-US"])
→ preview: keywords "photo,instagram,edit" → "photo,edit"
appstore__hesap_duzelt(bulgular: ["anahtar-marka:1234567:en-US"], onayla: true)
→ applied
Findings that need a value (privacy URL, copyright, demo account) take it
through degerler. If there's no editable version, it tells you instead of
creating one. Heavy moves — pulling an app from sale, demoting an admin —
are only explained, never done.
Quiet fixes. The advice never pushes you to knock on Apple's door: issues are fixed on your side, ideally in your next regular update; reporting reviews, messaging App Review unprompted or volunteering explanations is not recommended. If Apple asks, answer briefly and honestly. Every finding comes with a "don't" list — the reflexes that draw attention.
What it can't see. The API doesn't expose Apple's internal flags, rejection reasons or Resolution Center messages, or links to other accounts (same device, card or freelancer — the most common unexplained termination). So the tool reports risk signals, not a verdict, and says what it couldn't check.
Ask things like:
The prefix tells you which store a tool goes to. Tools marked ✎ modify
data and won't run without onayla=true.
These tools only load when both stores are connected.
magaza__cagir is marked ✎ here because it can also run operations that
modify data. In npx magaza-mcp araclar output it doesn't show ✎ though:
since it's also the single gateway to every read endpoint in the catalog, it
isn't dropped from the list in read-only mode — only write operations through
it are blocked.
The curated tools cover most day-to-day work. For everything else, the server carries the entire API surface of both stores:
When the curated tools aren't enough, the model first finds the operation it
needs with magaza__endpoint_ara, then runs it with magaza__cagir.
MCP tool definitions get loaded into context on every request — the installed tool list is paid for again on every message, even if you don't use any of them.
[!NOTE] Nothing is locked away: all 1,440 operations are reachable, but the ones you don't use cost nothing. There's no "should I turn this feature on, it costs tokens" setting either — there's nothing to turn on.
The catalogs are generated from Apple's and Google's official
specifications: Apple's published App Store Connect OpenAPI file, and
Google's Android Publisher and Play Developer Reporting discovery documents.
There's no hand-written endpoint list. The 159 operations Apple marks as
deprecated aren't dropped from the catalog — some of them are the only way to
reach that capability — but their summaries start with [ESKİMİŞ]
(deprecated) and are pushed down in search results.
App Store Connect — The App Manager role is enough when creating the key; Admin isn't required. Exceptions: user/access management endpoints and some analytics reports need higher privileges.
Google Play — Both steps are required:
[!WARNING] Contract, tax, and banking information cannot be read with any API key. Apple never exposes this data to the API at all; only the Account Holder can see it in the dashboard.
.p8 and Google service account
JSON are stored in the macOS Keychain; never written to config files,
environment variables, or the repo.anahtar command takes the file's path, reads the content itself, and
writes it straight to the vault; a key given via clipboard also flows
through a pipe. The key's content never appears in any command's output —
durum only prints the last four characters of the Key ID, tara only
prints file paths.onayla=true. This is enforced server-side — it doesn't depend on
the client's approval UI.--salt-okunur (or SALT_OKUNUR=1) removes every
write-capable tool from the list entirely: the model can't see them or call
them. 41 tools become 27. magaza__cagir stays in the list because it's
also the single gateway for read endpoints in the catalog — but it refuses
write operations when read-only mode is on.. and .. are rejected. For
absolute URLs the target host is validated, so no request can carry a token
to anywhere other than Apple or Google.annotations (readOnlyHint, destructiveHint).api.appstoreconnect.apple.com,
androidpublisher.googleapis.com, playdeveloperreporting.googleapis.com,
and oauth2.googleapis.com for tokens. The one exception is
the two fiyat_analizi tools, which read public purchasing-power figures from
api.worldbank.org (no key, nothing of yours is sent). There's no server in
the middle; data flows directly between your machine and Apple/Google.The Key ID, Issuer ID, and .p8 file might not belong together — all three
need to be from the same key. If they match, check the system clock: the
signed JWT lives 20 minutes, and a token produced on a machine with a drifted
clock gets rejected by Apple. Also make sure the .p8 file is an App Store
Connect API key — StoreKit or push keys don't work here.
The key's role isn't sufficient for that operation. App Manager covers most things; user management and some reports need more.
Worth knowing upfront: contract, tax, and banking information can't be read with any API key. A 403 here isn't a misconfiguration, it can't be fixed.
The app has moved to Google's new product model; the legacy inappproducts
endpoint is now closed and oneTimeProducts should be used instead. The
play__urunler tool handles this itself: it tries the new endpoint first,
falls back to the legacy one if needed, and tells you in the output which
model it used.
The service account may not have been invited to the app in Play Console. After inviting it, permissions can take a few minutes to propagate. If the invite is already in place, verify that Android Publisher API and Play Developer Reporting API are enabled on the Cloud project.
Because the Android Publisher API has no app-listing endpoint — Google
never published one. Since no Publisher call can be made without knowing the
package name, the list is pulled from the Play Developer Reporting API's
apps:search endpoint instead. That's why the Reporting API needs to be
enabled not just for crash metrics, but for basic usage too.
On Play, channel information can only be read from within an "edit session." The read tools open this session themselves, read from it, and leave it without committing — so it creates no changes — but it does mean two extra HTTP calls.
git clone https://github.com/tunaarikaya/magaza-mcp.git
cd magaza-mcp
npm install
npm run build # Compile TypeScript
npm run kontrol # Type-check (tsc --noEmit)
npm run dev # Compile in watch mode
To regenerate the tool catalogs from the specs:
node scripts/uret-katalog.mjs
This reads the three spec files under spec/ and rewrites the catalogs under
src/katalog/. The operation list is never hand-edited.
There are good projects in this space that came before this one. If your needs are limited to a single store, we genuinely recommend looking at them:
Our difference: all of these look at a single store. magaza-mcp combines
both in one setup and offers tools that can compare both stores in the same
call — exactly what a single-store server can't do.
MIT — see LICENSE for details. See THIRD-PARTY-NOTICES.md for third-party sources.
App Store, TestFlight, App Store Connect, Google Play, and Play Console are trademarks of their respective owners. This is an independent open-source project; it is not affiliated with, endorsed, sponsored, or supported by Apple Inc. or Google LLC.
One MCP server, two stores: App Store Connect + Google Play.
Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
Magaza se ejecuta localmente por stdio.
Última comprobación: 2026-10-27. One MCP server, two stores: App Store Connect + Google Play.