Skip to content
Back to search

magaza-mcp

Tek MCP sunucusu, iki mağaza: App Store Connect + Google Play. Tamamen Türkçe.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/tunaarikaya/magaza-mcp with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/tunaarikaya/magaza-mcp'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/tunaarikaya--magaza-mcp/badge.svg)](/listings/tunaarikaya--magaza-mcp)

HTML

<a href="/listings/tunaarikaya--magaza-mcp"><img src="/api/listings/tunaarikaya--magaza-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

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](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         (publish@project.iam...)

            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.

<details> <summary><b>Supported clients and config files</b></summary>

<br>

| Client | Config file | | --- | --- | | Claude Code | `~/.claude.json` | | Claude Desktop | `~/Library/Application Support/Claude/claude_desktop_config.json` | | Antigravity (IDE + CLI) | `~/.gemini/config/mcp_config.json` | | Cursor | `~/.cursor/mcp.json` | | Windsurf | `~/.codeium/windsurf/mcp_config.json` | | Codex | `~/.codex/config.toml` |

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.

</details>

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 726 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <div align="center">
  2. # Mağaza MCP
  3. **App Store Connect and Google Play, in one MCP server.**
  4. Let your AI assistant manage both stores.
  5. [![npm](https://img.shields.io/npm/v/magaza-mcp.svg?color=cb3837&label=npm)](https://www.npmjs.com/package/magaza-mcp)
  6. [![CI](https://github.com/tunaarikaya/magaza-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/tunaarikaya/magaza-mcp/actions/workflows/ci.yml)
  7. [![Stars](https://img.shields.io/github/stars/tunaarikaya/magaza-mcp?color=f5a623&label=stars)](https://github.com/tunaarikaya/magaza-mcp/stargazers)
  8. [![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
  9. [![Node](https://img.shields.io/badge/node-%3E%3D18-brightgreen.svg)](https://nodejs.org)
  10. **You don't type anything into a terminal to install this.**
  11. Drop this line on your AI assistant, it handles the rest:
  12. ```
  13. https://github.com/tunaarikaya/magaza-mcp — install this, read AGENTS.md
  14. ```
  15. [Türkçe README](README.tr.md)
  16. </div>
  17. ---
  18. > **You:** How much is Nota Defteri's monthly subscription on App Store vs. Play in Turkey?
  19. >
  20. > **Assistant:** ₺129.99 on the App Store, ₺99.99 on Play. Play is noticeably
  21. > cheaper — if you want the same price in both stores, you need to update the
  22. > base plan on Play.
  23. No other MCP server can answer that in a single call, because they all look at
  24. one store. `magaza-mcp` sees both at once.
  25. <p align="center">
  26. <picture>
  27. <source media="(prefers-color-scheme: dark)" srcset="docs/architecture-dark.svg">
  28. <img src="docs/architecture-light.svg" alt="magaza-mcp runs on your machine between your AI assistant and the App Store Connect and Google Play APIs; keys stay in your Keychain." width="880">
  29. </picture>
  30. </p>
  31. No server sits in the middle: the package runs on your own machine, talks
  32. directly to Apple and Google, and your keys never leave your Keychain.
  33. ---
  34. ## 📚 Table of contents
  35. | | |
  36. | --- | --- |
  37. | [🎯 Why this exists](#-why-this-exists) | The difference from single-store servers |
  38. | [⚡ Setup](#-setup) | Have your assistant do it — you don't type commands |
  39. | [🧑‍💻 Manual setup](#-manual-setup) | If you're not using an assistant |
  40. | [🧩 Do the two stores mix up?](#-do-the-two-stores-mix-up) | No — here's why |
  41. | [💬 What you can ask](#-what-you-can-ask) | Example prompts |
  42. | [🚨 Account health](#-account-health) | Is your Apple account at risk? |
  43. | [🧰 Tools](#-tools) | Full list of all 41 tools |
  44. | [🌐 Full API access](#-full-api-access) | 1,440 operations, ~9,000 tokens |
  45. | [🔑 Required permissions](#-required-permissions) | What Apple and Google require |
  46. | [🔒 Security](#-security) | Keys, approval gates, telemetry |
  47. | [🩺 Troubleshooting](#-troubleshooting) | Common errors |
  48. ---
  49. ## 🎯 Why this exists
  50. Almost every MCP server on the market covers a single store. If you want
  51. both, you install two separate servers, juggle two separate tool sets, and
  52. manually stitch together any question that needs a comparison.
  53. | Question | With single-store servers | With `magaza-mcp` |
  54. | --- | --- | --- |
  55. | "How much is this subscription in both stores?" | Two separate queries, manual comparison | One call, side by side |
  56. | "User paid but didn't get premium, what's wrong?" | You figure out which store first | Scans both at once, ranks findings |
  57. | "Where is what published?" | Two lists, manual matching | One list with iOS/Android pairs already matched |
  58. The real win isn't more tools: **it's tools that can query both stores in the
  59. same call, which is only possible once both are in one server.**
  60. ---
  61. ## ⚡ Setup
  62. Tell your assistant (Claude Code, Antigravity, Cursor, Codex, Gemini CLI…):
  63. ```
  64. https://github.com/tunaarikaya/magaza-mcp — install this, read AGENTS.md
  65. ```
  66. The assistant reads [AGENTS.md](AGENTS.md) and handles the entire setup. All
  67. you do is answer its questions:
  68. ```
  69. You › https://github.com/tunaarikaya/magaza-mcp — install this, read AGENTS.md
  70. Assistant › Looking for your keys on this machine...
  71. Found two keys:
  72. App Store : ~/Downloads/AuthKey_ABC123DEFG.p8 (Key ID ABC123DEFG)
  73. Play : ~/.config/play/account.json (publish@project.iam...)
  74. Want me to use these? If there's another file, tell me the path,
  75. or copy the key and paste it — either works.
  76. You › yes, use them
  77. Assistant › I need the Issuer ID for App Store. It's the UUID above the key
  78. list on App Store Connect → Users and Access → Integrations.
  79. You › 69a6de70-0000-0000-0000-000000000000
  80. Assistant › ✓ App Store Connect connected — 4 apps found
  81. ✓ Google Play connected — 3 apps found
  82. ✓ Registered in Claude Code and Antigravity settings
  83. Restart Claude Code, then ask:
  84. "List my apps across both stores"
  85. ```
  86. **If it can't find your key**, it will ask you how to proceed: give it the
  87. file path, copy the key to your clipboard, or — if you don't have a key yet —
  88. it'll walk you through getting one step by step.
  89. > [!IMPORTANT]
  90. > **The assistant never sees the contents of your key.** It runs the setup,
  91. > but the commands take the file's **path**, read its contents themselves, and
  92. > write it straight into the Keychain. Even when you paste the key via
  93. > clipboard (`pbpaste | …`), the content flows through a pipe and never enters
  94. > the assistant's context. AGENTS.md tells the assistant this explicitly.
  95. After setup, restart any open applications — MCP servers only load at
  96. startup.
  97. <details>
  98. <summary><b>Supported clients and config files</b></summary>
  99. <br>
  100. | Client | Config file |
  101. | --- | --- |
  102. | Claude Code | `~/.claude.json` |
  103. | Claude Desktop | `~/Library/Application Support/Claude/claude_desktop_config.json` |
  104. | Antigravity (IDE + CLI) | `~/.gemini/config/mcp_config.json` |
  105. | Cursor | `~/.cursor/mcp.json` |
  106. | Windsurf | `~/.codeium/windsurf/mcp_config.json` |
  107. | Codex | `~/.codex/config.toml` |
  108. Your existing config is left untouched — only the `magaza-mcp` entry is
  109. added or updated, a `.magaza-mcp-yedek` backup is taken before every write,
  110. and the write itself is atomic.
  111. </details>
  112. ---
  113. ## 🧑‍💻 Manual setup
  114. If you're not using an assistant, a wizard does the same job:
  115. ```bash
  116. npx magaza-mcp kur
  117. ```
  118. <details>
  119. <summary><b>What does the wizard ask?</b></summary>
  120. <br>
  121. ```
  122. Mağaza MCP setup
  123. App Store Connect + Google Play, in one setup
  124. 1. Which stores should we connect?
  125. App Store Connect (iOS / macOS)? [Y/n] y
  126. Google Play (Android)? [Y/n] y
  127. 2. App Store Connect key
  128. Key ID: ABC123DEFG
  129. Issuer ID: 00000000-0000-0000-0000-000000000000
  130. Path to .p8 file: ~/Downloads/AuthKey_ABC123DEFG.p8
  131. Connecting to Apple... ✓ 4 apps found
  132. ✓ Key saved (macOS Keychain)
  133. 3. Google Play service account
  134. Path to service account JSON: ~/.config/play/account.json
  135. Connecting to Google... ✓ 3 apps found
  136. ✓ Key saved (macOS Keychain)
  137. 4. Which clients should it be installed to?
  138. Claude Code? [Y/n] y
  139. Antigravity (IDE + CLI)? [Y/n] y
  140. Cursor? [y/N] n
  141. Setup complete.
  142. ```
  143. | # | Question | Note |
  144. | --- | --- | --- |
  145. | 1 | Which stores? | App Store, Play, or both |
  146. | 2 | App Store key | Key ID, Issuer ID, `.p8` path — verified with a real request to Apple before saving |
  147. | 3 | Play service account | Path to the JSON key — also verified against Google |
  148. | 4 | Which clients? | Clients detected on your machine come pre-checked |
  149. | 5 | Read-only? | No by default |
  150. </details>
  151. **Keys are never written to the config file.** On macOS they're saved to the
  152. Keychain; the config file only gets which stores are enabled (`MAGAZALAR`).
  153. On systems without Keychain access, it falls back to a file with `0600`
  154. permissions.
  155. <details>
  156. <summary><b>All commands</b></summary>
  157. <br>
  158. ```bash
  159. npx magaza-mcp tara # Search the machine for .p8 and service account keys
  160. npx magaza-mcp anahtar ... # Verify a key and write it to the vault (below)
  161. npx magaza-mcp kaydet # Register the server in clients' configs
  162. npx magaza-mcp durum # Show what's connected (--json for machine-readable)
  163. npx magaza-mcp araclar # List installed tools (✎ = can modify data)
  164. npx magaza-mcp kur # Manual setup wizard
  165. npx magaza-mcp surum # Print version
  166. npx magaza-mcp yardim # Help
  167. ```
  168. Registering a key (the command-line equivalent of the wizard's Q&A step):
  169. ```bash
  170. npx magaza-mcp anahtar --apple-p8 ~/Downloads/AuthKey_ABC123DEFG.p8 \
  171. --issuer-id 69a6de70-0000-0000-0000-000000000000
  172. npx magaza-mcp anahtar --play-json ~/.config/play/account.json
  173. pbpaste | npx magaza-mcp anahtar --play-json - # from clipboard, no file
  174. npx magaza-mcp anahtar --sil appstore # remove from the vault
  175. ```
  176. If `--key-id` isn't given, it's read from the filename. A key is never
  177. written to the vault without being verified against Apple/Google with a real
  178. request; if verification fails, the existing key in the vault is left
  179. untouched.
  180. </details>
  181. ---
  182. ## 🧩 Do the two stores mix up?
  183. No — and that's not an accident, it's the design itself.
  184. **1. Tool names are separated by prefix.** Every tool going to App Store
  185. starts with `appstore__`, every tool going to Play starts with `play__`. A
  186. tool never talks to both APIs. There's no shared name, so there's nothing to
  187. mix up.
  188. **2. Tools for the store you didn't pick are never loaded.** On startup, the
  189. server reads the `MAGAZALAR` variable and builds the tool list from it — the
  190. other store's tools aren't even loaded into memory, aren't shown to the
  191. model, and cost zero tokens.
  192. | Setup | Tools loaded |
  193. | --- | --- |
  194. | Both stores | 41 |
  195. | App Store only | 22 |
  196. | Play only | 19 |
  197. | Read-only (both stores) | 27 |
  198. **3. Cross-store tools only exist when both stores are enabled.** In a
  199. single-store setup they're never created at all — they'd have no meaning.
  200. **4. The dispatch tools know their scope too.** The `magaza` parameter on
  201. `magaza__endpoint_ara` and `magaza__cagir` is an enum that only accepts the
  202. stores you've set up. If you only installed Play, the model can't make a call
  203. with `magaza: "appstore"` — the schema doesn't allow it.
  204. ---
  205. ## 💬 What you can ask
  206. The app names in the examples are made up; you'd use your own app's name.
  207. **Both stores at once**
  208. - *"List my apps across both stores — where's each one published?"*
  209. - *"What's Nota Defteri's monthly subscription on App Store vs. Play in Turkey? Is there a difference?"*
  210. - *"A user says they paid but didn't get premium. Check the purchase setup in both stores."*
  211. **App Store**
  212. - *"Which of my versions is stuck in review?"*
  213. - *"Did yesterday's TestFlight build finish processing?"*
  214. - *"Summarize the 1- and 2-star reviews from the last week — what's the most common complaint?"*
  215. - *"Update the 'What's New' text for the version in preparation."*
  216. **Google Play**
  217. - *"Which version is on the production channel and what percentage of users does it reach?"*
  218. - *"Has the crash rate gone up over the last 14 days?"*
  219. - *"Is this purchase token valid, is the subscription still active?"*
  220. - *"Draft a polite reply to this review, but show me first."*
  221. ---
  222. ## 🚨 Account health
  223. Apple terminates developer accounts every year for spam, copycat apps and
  224. review manipulation — and many developers find out only when the email
  225. arrives. Most of them never knew they were doing anything wrong: the same
  226. screenshots in five apps, "Instagram" in the keywords, someone else's
  227. copyright left over from a template.
  228. `appstore__hesap_sagligi` scans the whole account and scores the risk from
  229. 0 to 100:
  230. ```
  231. You › Is my developer account safe?
  232. Assistant › ACCOUNT RISK: 72/100 🔴 HIGH
  233. Clones / spam (4.3) ██████████ critical (3)
  234. Metadata & trademarks (2.3/5.2) █████░░░░░ high (4)
  235. Reviews & money (5.6/3.1) ██░░░░░░░░ low (2)
  236. Review history & account ██████░░░░ medium (3)
  237. 1. [CRITICAL] Same screenshots in 6 apps
  238. 2. [HIGH] Photo Pro: "instagram" in the keywords
  239. 3. [HIGH] 3 apps carry someone else's copyright
  240. …
  241. ```
  242. | Section | What it looks for |
  243. | --- | --- |
  244. | Clones / spam | Identical screenshots across apps, near-identical names and descriptions, `app1, app2…` bundle IDs, saturated categories, foreign copyright, many apps in a short time |
  245. | Metadata & trademarks | Brand names (Apple, Instagram, ChatGPT…) in names and keywords, "best / #1 / free" in the name, keyword stuffing, Android mentions, missing privacy or support URL, media downloaders, fake-function apps |
  246. | Reviews & money | Scam / refund complaints, 5-star bursts, copy-paste reviews, misleading review replies, refund rate, apps with no downloads, overpriced weekly subscriptions, rejected IAPs |
  247. | Review history & account | Rejections, reviews stuck for days, apps Apple removed, apps not updated in 3+ years, EU trader status, missing declarations (content rights, encryption, demo account, review notes, age rating), too many admins |
  248. Every finding comes with the Apple guideline, why it's risky and the steps
  249. to fix it.
  250. | Parameter | What it does |
  251. | --- | --- |
  252. | `uygulama` | Scan a single app (Apple id, bundle ID or name). Clone detection needs the whole account. |
  253. | `bolum` | Only these sections: `klon`, `metadata`, `yorum_para`, `inceleme_hesap` |
  254. | `derin` | All languages and 1,000 reviews per app (slower). Default: primary language + en-US, 200 reviews |
  255. | `satici_no` | Vendor number — adds the refund rate and 12-month download checks |
  256. **Fixing.** Findings marked automatic can be fixed with
  257. `appstore__hesap_duzelt`. It always shows the change first and only writes
  258. with `onayla=true`:
  259. ```
  260. appstore__hesap_duzelt(bulgular: ["anahtar-marka:1234567:en-US"])
  261. → preview: keywords "photo,instagram,edit" → "photo,edit"
  262. appstore__hesap_duzelt(bulgular: ["anahtar-marka:1234567:en-US"], onayla: true)
  263. → applied
  264. ```
  265. Findings that need a value (privacy URL, copyright, demo account) take it
  266. through `degerler`. If there's no editable version, it tells you instead of
  267. creating one. Heavy moves — pulling an app from sale, demoting an admin —
  268. are only explained, never done.
  269. **Quiet fixes.** The advice never pushes you to knock on Apple's door: issues
  270. are fixed on your side, ideally in your next regular update; reporting
  271. reviews, messaging App Review unprompted or volunteering explanations is not
  272. recommended. If Apple asks, answer briefly and honestly. Every finding comes
  273. with a "don't" list — the reflexes that draw attention.
  274. > **What it can't see.** The API doesn't expose Apple's internal flags,
  275. > rejection reasons or Resolution Center messages, or links to other
  276. > accounts (same device, card or freelancer — the most common unexplained
  277. > termination). So the tool reports risk signals, not a verdict, and says
  278. > what it couldn't check.
  279. Ask things like:
  280. - *"Is my developer account safe?"*
  281. - *"Why is my review taking so long?"*
  282. - *"Fix the keyword problems you found, but show me first."*
  283. ---
  284. ## 🧰 Tools
  285. The prefix tells you which store a tool goes to. Tools marked **✎** modify
  286. data and won't run without `onayla=true`.
  287. <details open>
  288. <summary><b>Both stores at once — 3 tools</b> · <i>the heart of the project</i></summary>
  289. <br>
  290. These tools only load when both stores are connected.
  291. | Tool | What it does |
  292. | --- | --- |
  293. | `magaza__genel_bakis` | Collects apps from both stores into one list; puts the iOS/Android pair of the same product side by side, and separates out apps that only exist in one store. |
  294. | `magaza__abonelik_karsilastir` | Compares the same app's subscriptions across both stores: product IDs, durations, and prices in the requested country. Converts the country code to whichever format each store expects. |
  295. | `magaza__iap_teshis` | Diagnoses "paid but no premium" issues: are the products live, do they have a price in that country, is the plan open to new subscribers; if you give it a Play purchase token it verifies that too, and writes up its findings as a list. |
  296. </details>
  297. <details>
  298. <summary><b>App Store Connect — 21 tools</b> (<code>appstore__</code>)</summary>
  299. <br>
  300. | Tool | What it does |
  301. | --- | --- |
  302. | `appstore__uygulamalar` | Lists the apps on the account: name, bundle ID, SKU, primary language, and the `id` other tools need. |
  303. | `appstore__surumler` | Shows an app's App Store versions and their status (in preparation, in review, live, rejected). |
  304. | `appstore__buildler` | Lists TestFlight builds, their processing status, and expiry dates. |
  305. | `appstore__yorumlar` | Fetches customer reviews, newest first; filterable by rating and country, or only the ones without a reply yet. Shows the existing developer response if there is one. |
  306. | `appstore__yorum_yanitla` ✎ | Writes a developer response to a review (published after Apple's moderation). |
  307. | `appstore__abonelikler` | Lists subscription groups and the subscriptions in them: product ID, duration, status. |
  308. | `appstore__abonelik_fiyatlari` | Fetches a subscription's customer price and developer proceeds, country by country. |
  309. | `appstore__iap_urunler` | Lists one-time in-app purchase products. |
  310. | `appstore__testflight_gruplari` | Shows TestFlight beta groups, how many testers are in each, public invite links, and quotas. |
  311. | `appstore__metin_guncelle` ✎ | Updates the store text of the version in preparation: release notes, description, keywords, promotional text. |
  312. | `appstore__satis_raporu` | Downloads the sales/download report as TSV: daily, weekly, monthly, or yearly; sales, pre-order, installs, subscriptions, subscription events, subscribers, and offer code reports. |
  313. | `appstore__kurallar` | Fetches Apple's App Review Guidelines live on every call — never a baked-in copy, so it can't go stale. With no query, reports which rule numbers changed since the last check (local diff cache). With a query (a rule number or a keyword), returns the current full text of matching rules, for reviewing an app's code against. |
  314. | `appstore__abonelik_fiyat_ayarla` ✎ | Sets a subscription's price in **every country at once**: give one price (e.g. USA 9.99), Apple's equalization table fills in all ~175 countries and they're written in a single request. Add country-specific prices on top (`{"TUR": "349.99"}`), or change only those countries and leave the rest alone. |
  315. | `appstore__fiyat_analizi` | Regional pricing suggestion, writes nothing: starts from Apple's equalized price and applies a softened discount based on each country's purchasing power (World Bank). Never raises a price, never cuts more than half, leaves rich countries alone. The output plugs straight into `abonelik_fiyat_ayarla`. |
  316. | `appstore__iap_fiyat_ayarla` ✎ | Sets a one-time purchase's price from a single base country; Apple fills in the rest. |
  317. | `appstore__abonelik_ulkeleri` ✎ | Makes a subscription available in every country (or the ones you list) in one request. |
  318. | `appstore__abonelik_kur` ✎ | Creates a subscription from scratch behind one approval: group → subscription → localized names → availability → prices in all countries. |
  319. | `appstore__kalma_mesaji_kur` ✎ | Sets up a retention message shown when a subscriber starts to cancel: message → version → localized header/body → assigned to the subscription(s), behind one approval. Images/offers are optional add-ons via `magaza__cagir`; submitting the version for App Review is a separate manual step. |
  320. | `appstore__yas_derecelendirme` ✎ | Reads or fills in the age rating questionnaire (Apple's 2025 questions). Finds the editable app info by itself; only the answers you give change. |
  321. | `appstore__hesap_sagligi` | Scans the whole developer account for termination, removal and long-review risk: a 0–100 score, findings tied to Apple guidelines, why each one is risky and how to fix it. See [Account health](#-account-health). |
  322. | `appstore__hesap_duzelt` ✎ | Fixes findings from `hesap_sagligi` by id: shows current → new first, applies with `onayla=true`. Never creates a version, removes an app or changes roles. |
  323. </details>
  324. <details>
  325. <summary><b>Google Play — 16 tools</b> (<code>play__</code>)</summary>
  326. <br>
  327. | Tool | What it does |
  328. | --- | --- |
  329. | `play__uygulamalar` | Lists the apps the service account can access; this is where you get the package name other tools need. |
  330. | `play__kanallar` | Shows release channels (internal, alpha, beta, production) and the versions on each, with user rollout percentages. Requires the service account to have release-management permission. |
  331. | `play__yorumlar` | Fetches user reviews, translating them if asked. The Play API only returns roughly the last week. |
  332. | `play__yorum_yanitla` ✎ | Writes a developer response to a review (350 characters max). |
  333. | `play__abonelikler` | Lists subscriptions and their base plans: duration, status, number of priced countries. Includes archived ones if asked. |
  334. | `play__abonelik_fiyatlari` | Fetches a base plan's prices country by country, and whether it's open to new subscribers; also checks the "rest of world" fallback price for countries not listed individually. |
  335. | `play__urunler` | Lists one-time products; tries both the new (`oneTimeProducts`) and legacy (`inappproducts`) models. |
  336. | `play__satin_alma_dogrula` | Verifies a purchase token: subscription status, acknowledgment status, expiry date, whether it's a test purchase. |
  337. | `play__iade_edilenler` | Lists cancelled, refunded, or charged-back purchases; turns the refund reason and source into something readable. Google only returns the last 30 days. |
  338. | `play__cokme_orani` | Android vitals: crash and ANR rates (including the user-perceived rates Play uses for its bad-behavior thresholds), whether a threshold is exceeded, and the most frequent crash clusters with stack traces. Can be narrowed to one version code. |
  339. | `play__surum_yayinla` ✎ | Uploads an AAB/APK and releases it to a track in one approval: upload → assign to track → release notes → commit. Give a percentage for a staged rollout (e.g. production 10%). If anything fails, nothing is committed. |
  340. | `play__yayin_yonet` ✎ | Manages a track: change the rollout %, halt, resume, complete, promote a release to another track (internal → production), or update only the release notes. The preview shows the track before and after. |
  341. | `play__listeleme_guncelle` ✎ | Reads or updates store listing text (title, short and full description, video) for every language in one edit. |
  342. | `play__gorsel_yukle` ✎ | Uploads screenshots, the icon, or the feature graphic, optionally replacing the existing ones. |
  343. | `play__abonelik_fiyat_ayarla` ✎ | Sets a base plan's price in every country at once from a USD price (Google's own conversion), with optional country-specific prices on top, or changes only the countries you list. |
  344. | `play__fiyat_analizi` | Regional pricing suggestion for Play, writes nothing: same purchasing-power logic as the App Store version, rounded to natural-looking local prices. |
  345. </details>
  346. <details>
  347. <summary><b>Full API access — 3 tools</b> (<code>magaza__</code>)</summary>
  348. <br>
  349. | Tool | What it does |
  350. | --- | --- |
  351. | `magaza__endpoint_ara` | Searches for an endpoint across all connected stores' APIs; returns the operation name, HTTP method, path, and parameters. |
  352. | `magaza__cagir` ✎ | Runs the operation you found. Fills in path parameters automatically; operations that modify data won't run without `onayla=true`. |
  353. | `magaza__sema` | Shows what an operation's request body should look like; used before POST/PATCH calls. |
  354. `magaza__cagir` is marked ✎ here because it can also run operations that
  355. modify data. In `npx magaza-mcp araclar` output it doesn't show ✎ though:
  356. since it's also the single gateway to every read endpoint in the catalog, it
  357. isn't dropped from the list in read-only mode — only write operations through
  358. it are blocked.
  359. </details>
  360. ---
  361. ## 🌐 Full API access
  362. The curated tools cover most day-to-day work. For everything else, the server
  363. carries the **entire** API surface of both stores:
  364. | Source | Operations |
  365. | --- | --- |
  366. | App Store Connect API v4.5 | 1,270 |
  367. | Android Publisher API v3 | 145 |
  368. | Play Developer Reporting API v1beta1 | 25 |
  369. | **Total** | **1,440** |
  370. When the curated tools aren't enough, the model first finds the operation it
  371. needs with `magaza__endpoint_ara`, then runs it with `magaza__cagir`.
  372. ### Why aren't they all separate tools?
  373. MCP tool definitions get loaded into context **on every request** — the
  374. installed tool list is paid for again on every message, even if you don't use
  375. any of them.
  376. | | Tools | Paid on every message |
  377. | --- | --- | --- |
  378. | **magaza-mcp** | 41 | **~9,000 tokens** |
  379. | If all were separate tools | 1,440 | ~210,000 tokens |
  380. > [!NOTE]
  381. > Nothing is locked away: all 1,440 operations are reachable, but the ones
  382. > you don't use cost nothing. There's no "should I turn this feature on, it
  383. > costs tokens" setting either — there's nothing to turn on.
  384. The catalogs are generated from Apple's and Google's **official
  385. specifications**: Apple's published App Store Connect OpenAPI file, and
  386. Google's Android Publisher and Play Developer Reporting discovery documents.
  387. There's no hand-written endpoint list. The 159 operations Apple marks as
  388. deprecated aren't dropped from the catalog — some of them are the only way to
  389. reach that capability — but their summaries start with `[ESKİMİŞ]`
  390. (deprecated) and are pushed down in search results.
  391. ---
  392. ## 🔑 Required permissions
  393. **App Store Connect** — The **App Manager** role is enough when creating the
  394. key; Admin isn't required. Exceptions: user/access management endpoints and
  395. some analytics reports need higher privileges.
  396. **Google Play** — Both steps are required:
  397. 1. The service account must be invited from **Play Console → Users and
  398. permissions** and granted access to the relevant apps.
  399. 2. The **Android Publisher API** and **Play Developer Reporting API** must be
  400. enabled on the Cloud project. App listing and crash metrics come from the
  401. Reporting API, so the second one is genuinely required too.
  402. > [!WARNING]
  403. > Contract, tax, and banking information **cannot be read with any API key.**
  404. > Apple never exposes this data to the API at all; only the Account Holder can
  405. > see it in the dashboard.
  406. ---
  407. ## 🔒 Security
  408. - **Keys live in the Keychain.** The Apple `.p8` and Google service account
  409. JSON are stored in the macOS Keychain; never written to config files,
  410. environment variables, or the repo.
  411. - **The assistant never sees the key, even when it runs the setup.** The
  412. `anahtar` command takes the file's path, reads the content itself, and
  413. writes it straight to the vault; a key given via clipboard also flows
  414. through a pipe. The key's content never appears in any command's output —
  415. `durum` only prints the last four characters of the Key ID, `tara` only
  416. prints file paths.
  417. - **Operations that modify data require approval.** Write tools don't run on
  418. the first call: they return what would happen and the expected request
  419. body; the operation only runs once the user approves and it's called again
  420. with `onayla=true`. This is enforced **server-side** — it doesn't depend on
  421. the client's approval UI.
  422. - **Read-only mode.** `--salt-okunur` (or `SALT_OKUNUR=1`) removes every
  423. write-capable tool from the list entirely: the model can't see them or call
  424. them. 41 tools become 27. `magaza__cagir` stays in the list because it's
  425. also the single gateway for read endpoints in the catalog — but it refuses
  426. write operations when read-only mode is on.
  427. - **Path parameters are validated.** IDs passed to tools are encoded before
  428. entering a URL; path-traversal attempts like `.` and `..` are rejected. For
  429. absolute URLs the target host is validated, so no request can carry a token
  430. to anywhere other than Apple or Google.
  431. - **Clients can see which tools modify data.** The tool list ships with MCP
  432. `annotations` (`readOnlyHint`, `destructiveHint`).
  433. - **Package provenance is verifiable.** Every version published to npm is
  434. built inside GitHub Actions, and npm generates a Sigstore-signed provenance
  435. attestation: the **Provenance** section on the npm page shows which commit
  436. in this repo the tarball you downloaded was built from. No publish token is
  437. stored in the repo; GitHub issues a short-lived, signed identity on every
  438. release (trusted publishing), so there's no publish key to steal either.
  439. - **No telemetry.** No analytics, error reports, or usage data are sent.
  440. Network traffic only goes to `api.appstoreconnect.apple.com`,
  441. `androidpublisher.googleapis.com`, `playdeveloperreporting.googleapis.com`,
  442. and `oauth2.googleapis.com` for tokens. The one exception is
  443. the two `fiyat_analizi` tools, which read public purchasing-power figures from
  444. `api.worldbank.org` (no key, nothing of yours is sent). There's no server in
  445. the middle; data flows directly between your machine and Apple/Google.
  446. ---
  447. ## 🩺 Troubleshooting
  448. <details>
  449. <summary><b>Apple returns 401</b></summary>
  450. <br>
  451. The Key ID, Issuer ID, and `.p8` file might not belong together — all three
  452. need to be from the same key. If they match, check the system clock: the
  453. signed JWT lives 20 minutes, and a token produced on a machine with a drifted
  454. clock gets rejected by Apple. Also make sure the `.p8` file is an **App Store
  455. Connect API key** — StoreKit or push keys don't work here.
  456. </details>
  457. <details>
  458. <summary><b>Apple returns 403</b></summary>
  459. <br>
  460. The key's role isn't sufficient for that operation. App Manager covers most
  461. things; user management and some reports need more.
  462. Worth knowing upfront: **contract, tax, and banking information can't be read
  463. with any API key.** A 403 here isn't a misconfiguration, it can't be fixed.
  464. </details>
  465. <details>
  466. <summary><b>Play returns 403 on the <code>inappproducts</code> endpoint</b></summary>
  467. <br>
  468. The app has moved to Google's new product model; the legacy `inappproducts`
  469. endpoint is now closed and `oneTimeProducts` should be used instead. The
  470. `play__urunler` tool handles this itself: it tries the new endpoint first,
  471. falls back to the legacy one if needed, and tells you in the output which
  472. model it used.
  473. </details>
  474. <details>
  475. <summary><b>Play returns 403 in general</b></summary>
  476. <br>
  477. The service account may not have been invited to the app in Play Console.
  478. After inviting it, permissions can take a few minutes to propagate. If the
  479. invite is already in place, verify that Android Publisher API and Play
  480. Developer Reporting API are enabled on the Cloud project.
  481. </details>
  482. <details>
  483. <summary><b>Why does "list my Play apps" come from the Reporting API?</b></summary>
  484. <br>
  485. Because the Android Publisher API **has no app-listing endpoint** — Google
  486. never published one. Since no Publisher call can be made without knowing the
  487. package name, the list is pulled from the Play Developer Reporting API's
  488. `apps:search` endpoint instead. That's why the Reporting API needs to be
  489. enabled not just for crash metrics, but for basic usage too.
  490. </details>
  491. <details>
  492. <summary><b>Why is Play's version/channel info sometimes delayed?</b></summary>
  493. <br>
  494. On Play, channel information can only be read from within an "edit session."
  495. The read tools open this session themselves, read from it, and leave it
  496. without committing — so it creates no changes — but it does mean two extra
  497. HTTP calls.
  498. </details>
  499. ---
  500. ## 🛠 Development
  501. ```bash
  502. git clone https://github.com/tunaarikaya/magaza-mcp.git
  503. cd magaza-mcp
  504. npm install
  505. npm run build # Compile TypeScript
  506. npm run kontrol # Type-check (tsc --noEmit)
  507. npm run dev # Compile in watch mode
  508. ```
  509. To regenerate the tool catalogs from the specs:
  510. ```bash
  511. node scripts/uret-katalog.mjs
  512. ```
  513. This reads the three spec files under `spec/` and rewrites the catalogs under
  514. `src/katalog/`. The operation list is never hand-edited.
  515. ---
  516. ## 🤝 Similar projects
  517. There are good projects in this space that came before this one. If your
  518. needs are limited to a single store, we genuinely recommend looking at them:
  519. - **[Heimdall](https://github.com/erayendes/app-store-connect-mcp)** — Covers
  520. the entire App Store Connect API with 890 tools, with a profile system that
  521. lets you narrow the tool set down. The deepest project in this space if
  522. you're only interested in iOS.
  523. - **[app-store-connect-mcp-server](https://github.com/JoshuaRileyDev/app-store-connect-mcp-server)**
  524. — The first one. Established the idea of putting App Store Connect behind
  525. an MCP server; everyone who came after owes something to it.
  526. - **[google-play-developer-mcp](https://github.com/devinwang/google-play-developer-mcp)**
  527. — A comprehensive, mature server on the Play side. More than enough if
  528. you're only publishing on Android.
  529. Our difference: all of these look at a single store. `magaza-mcp` combines
  530. both in one setup and offers tools that can compare both stores in the same
  531. call — exactly what a single-store server can't do.
  532. ---
  533. ## 📄 License
  534. MIT — see [LICENSE](LICENSE) for details. See
  535. [THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md) for third-party sources.
  536. App Store, TestFlight, App Store Connect, Google Play, and Play Console are
  537. trademarks of their respective owners. This is an independent open-source
  538. project; it is not affiliated with, endorsed, sponsored, or supported by
  539. Apple Inc. or Google LLC.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.