Skip to main content
Glama
JohnBilousov

appstore-play-mcp

by JohnBilousov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to appstore-play-mcp

No user-submitted related servers found.

    Related Servers

    • appstoreconnect-codex-mcp

      AI-Scarlett
      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

    • Store Scraper MCP

      MiguelAlvRed
      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
      -

    • storelift-mcp

      vom-core
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables App Store and Google Play keyword rank tracking, competitor comparisons, and AI visibility checks through natural language, without requiring store credentials.
      217 npm
      MIT

    • aurora-mcp

      Hari-sys786
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables anonymous Google Play access through tools for searching apps, retrieving app info and version history, and downloading APKs to local paths without Google credentials.
      MIT

    • testflight-mcp

      OrellBuehler
      A
      license
      B
      quality
      A
      maintenance
      MCP server for TestFlight and App Store Connect that exposes the App Store Connect API as tools for AI agents, focusing on retrieving beta feedback (screenshots, crash logs) and related app/build/tester data, with read-only operations.
      41
      201 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources