Skip to main content
Glama
OrellBuehler

play-console-mcp

by OrellBuehler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to play-console-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      18 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

    • Google Play Console MCP

      abd3lraouf-studios
      A
      license
      B
      quality
      A
      maintenance
      Enables managing releases, monitoring Android vitals, analyzing earnings and search terms, optimizing ASO, and preflighting store assets through natural language, with a confirmation gate before destructive writes.
      170
      38 PyPI
      Apache 2.0

    • MCP Google Play Store Server

      BlocktopusLtd
      A
      license
      Not graded
      quality
      D
      maintenance
      Integrates Google Play Store management tools with AI assistants to handle app listings, releases, and user reviews. It enables users to manage Play Console tasks like updating store information and retrieving performance statistics through natural language.
      32 npm
      10
      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/5.0

    Scored across 44 tools

    Disambiguation4/5

    Most tools are clearly distinct by resource and action (e.g., list_tracks vs get_track, list_releases vs promote_release). However, the many query_* vitals tools (crash, ANR, error counts, slow start, slow rendering, wakeup, wakelock, LMK, memory) could be confused by an agent, though descriptions clarify each metric.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern: list_*, get_*, create_*, update_*, delete_*, query_*, search_*, promote_*, halt_*. Minor deviations like 'get_release_filter_options' and 'query_slow_start_rate' are still predictable. The pattern is strong overall.

    Tool Count3/5

    44 tools is on the heavy side, but the server covers a broad domain (releases, listings, reviews, vitals, error reporting, device tiers). The count is justified by the scope, though it borders on overwhelming and could be consolidated (e.g., many query_* tools).

    Completeness4/5

    The surface covers core workflows: release management (create/promote/rollout/halt), listings (list/get/update), reviews (list/get/reply), vitals queries, and error search. Minor gaps: no tool to upload bundles/APKs (explicitly noted as external), no delete for tracks or listings, and no tool to manage asset packs or subscriptions.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources