Skip to main content
Glama
JohnBilousov

appstore-play-mcp

by JohnBilousov

Related Servers

Alternatives to appstore-play-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only interaction with App Store Connect via MCP tools, including listing apps, versions, builds, and review submissions, with compliance boundaries and no write operations by default.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables an AI assistant to manage both App Store Connect and Google Play from one server, covering 27 tools across apps, versions, TestFlight builds, reviews, subscriptions, pricing, and purchase diagnostics. Cross-store tools compare subscription prices and match iOS/Android app listings in a single call, while credentials stay in the macOS Keychain.
      27
      311 npm
      78
      MIT
    • F
      license
      C
      quality
      D
      maintenance
      Enables querying and retrieving data from App Store and Google Play Store, including app details, reviews, ratings, rankings, permissions, and search capabilities across both iOS and Android platforms.
      20
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query live App Store and Google Play data — keyword demand, rank history, top charts, competitor sets, reviews and ratings — across 100+ countries, directly inside a chat instead of a dashboard. Exposes 35 read-only tools covering app search, ASO keyword profiling, ranking trajectories, and worldwide market comparisons through a remote OAuth-authenticated endpoint.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables retrieval of App Store and Google Play reviews, ratings summaries, and ASO keyword rankings for any app using its store ID or package name.
      245 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct aspect: health, app listing, app details, release status, and reviews. There is no overlap in purpose, and the descriptions clarify boundaries (e.g., get_app is for specific apps, list_apps for discovery). An agent can unambiguously select the right tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (stores_health, list_apps, get_app, get_releases, get_reviews). The verbs are clear and the nouns are straightforward, making the set highly predictable.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose of aggregating app store data. Each tool covers a necessary function without redundancy, and the count fits comfortably within the ideal 3-15 range.

    Completeness4/5

    The tool surface covers the core read operations for app store monitoring: health, listing, details, releases, and reviews. Minor gaps exist, such as lack of write/edit capabilities, but given the server's apparent focus on observation (and explicit note that Play edits are temporary), these are not critical. The inclusion of a health check and pagination for reviews shows good consideration of workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues