Skip to main content
Glama
Sign In
Play Store MCP

Play Store MCP

by cntechio-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Play Store MCP

No user-submitted related servers found.

    Related Servers

    • play-console-mcp

      OrellBuehler
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to manage Google Play Console reviews and Android app releases, including replying to reviews, promoting releases, managing staged rollouts, and checking crash/ANR vitals.
      44
      84 npm
      2
      MIT

    • dev-publish

      willan23
      F
      license
      B
      quality
      B
      maintenance
      Enables AI agents to manage Google Play apps with scope-based permissions, including publishing internal releases, updating listings, replying to reviews, and promoting to production.
      11
      12 npm
      -

    • google-cloud-console-mcp

      kutleloove
      A
      license
      B
      quality
      C
      maintenance
      Gives AI assistants hands-on control over Google Play Console and Google Cloud Console using an authorized Google identity. Exposes 95 tools for shipping app builds and release tracks, managing store listings, reviews, in-app products, GCP projects and IAM, Firebase projects and App Distribution, and Cloud Storage or Artifact Registry resources.
      95
      MIT

    • play-console-mcp

      denshinji
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to manage Google Play store listings, icons, feature graphics, screenshots, app bundle releases, and user reviews, staging every change in a Play edit that stays unpublished until it is explicitly committed. Safety guards such as a production lock, package allowlist, asset-root restriction, and untrusted-review marking keep an agent's edits reviewable before they go live.
      17
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 22 tools

    Disambiguation4/5

    The tools split cleanly along resource lines (edits, tracks, listings, bundles, reviews, testers) and read vs. mutate operations are mostly self-evident from names. The only real overlaps are upload_bundle vs upload_internal_sharing_bundle and list_track_releases vs get_track, though the descriptions distinguish them by edit requirements and sharing destination.

    Naming Consistency5/5

    Every tool follows a consistent snake_case verb_noun pattern (list_reviews, get_review, create_edit, patch_store_listing, commit_edit, reply_to_review). The one-word suffix forms like create_edit/discard_edit are still verb_noun and highly predictable.

    Tool Count3/5

    22 tools is at the heavy end for a single server, and the surface spans several sub-domains (edits, tracks, listings, images, testers, reviews, bundles). Each tool arguably earns its place, but the count makes discovery and selection more burdensome than a tighter core set would.

    Completeness4/5

    The edit lifecycle is fully covered (create/get/validate/commit/discard), and tracks, listings, testers, bundles, and reviews each have read/write operations. Gaps remain: there is no way to delete listing images or listings, and no tool for app-level metadata or halting/rolling back a rollout.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources