Skip to main content
Glama
Mağaza MCP
by tunaarikaya

Related Servers

Alternatives to Mağaza MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      An 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.
      60
      19
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Gives 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.
      500
      136 npm
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage Apple App Store Connect operations including app management, TestFlight, analytics, reviews, subscriptions, and more through 54 tools.
      61
      68 npm
      11
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Manages 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.
      10
      31 npm
      3
      MIT

    TDQS

    A3.7/5.0

    Scored across 27 tools

    Disambiguation4/5

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

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.