Mağaza MCP
Related Servers
Alternatives to Mağaza MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server that lets AI agents drive App Store Connect, Google Play Console, and Expo EAS end to end — builds, listings, screenshots, privacy labels, in-app purchases, review submission and even replying to App Review. It automates roughly 60 tools so an app can go from a build to 'Waiting for Review' without clicking through two consoles.6019MIT
- AlicenseCqualityBmaintenanceGives AI assistants complete, spec-driven access to Apple's App Store Connect API through 1300+ tools covering the full surface — apps and versions, TestFlight, Xcode Cloud, Game Center, App Clips, in-app purchases and subscriptions, pricing, review submissions, provisioning, analytics, sales and finance reports. It lets users automate submission workflows, manage multi-account credentials, and orchestrate builds and releases across any MCP client.500136 npm3MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Apple App Store Connect operations including app management, TestFlight, analytics, reviews, subscriptions, and more through 54 tools.6168 npm11MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Apple App Store Connect resources like apps, builds, TestFlight, and reviews through natural language.209 npmMIT
- AlicenseAqualityDmaintenanceManages App Store Connect and Google Play Console metadata, releases, and ASO workflows locally through MCP tools, enabling store management directly from AI clients without manual console navigation.1031 npm3MIT
- AlicenseNot gradedqualityBmaintenanceAutomate App Store Connect from your AI agent. Manage versions, metadata, builds, and submissions through natural language.12 npm8MIT
TDQS
Scored across 27 tools
The appstore__/play__ namespaces plus the magaza__ cross-store tools make most purposes clearly distinct (list versions vs. list builds vs. list reviews vs. reply to review). The only real overlap is the meta-tool trio (endpoint_ara, cagir, sema) which can reach any operation that the specific tools already wrap, so an agent could occasionally pick cagir where a dedicated tool would be better. Descriptions mostly resolve this by describing a clear workflow (find → schema → call).
All names are lowercase snake_case with a consistent platform prefix (magaza__, appstore__, play__), which gives a strong predictable grouping. The internal pattern mixes pure-resource nouns (uygulamalar, surumler, yorumlar) with resource_action forms (yorum_yanitla, metin_guncelle, satin_alma_dogrula), a minor deviation but still readable and internally consistent within each namespace.
At 27 tools the set is heavy, sitting just above the 25-tool threshold, though the surface spans two independent platforms (App Store + Play) across ~10 resource types each, which explains most of the count. The three generic meta-tools (endpoint_ara, cagir, sema) partially overlap with the dedicated wrappers, so a handful of tools could arguably be collapsed. Borderline but largely justified by the domain breadth.
Coverage is strong: apps, versions, builds, reviews (with replies), subscriptions, IAP products, pricing, sales reports, purchase verification, refunds, crash rate, plus cross-store comparison and purchase diagnosis. Dedicated gaps exist (no Play metadata update, no build upload/submit-for-review tool), but magaza__cagir/endpoint_ara/sema provide an escape hatch to the full App Store Connect and Play APIs, so agents are unlikely to hit a dead end.