Skip to main content
Glama
AgiMaulana

Google Play Console

by AgiMaulana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Google Play Console

No user-submitted related servers found.

    Related Servers

    • playstore-release

      beydemirfurkan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables end-to-end Android app publishing to Google Play via the Developer API, including readiness checks, releases, promotions, reviews, and subscriptions.
      2
      MIT

    • play-store-mcp

      petropentsak
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables to interact with Google Play Console, allowing release management, app vitals monitoring, and APK/AAB deployment via a service account.
      -

    • 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
      41 PyPI
      Apache 2.0

    • 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
      29 npm
      1
      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

    A3.9/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions, but list_tracks and get_track_info overlap somewhat, and create_release vs upload_artifact could be confused since upload_artifact also creates a release. Descriptions are specific enough to resolve most ambiguity.

    Naming Consistency5/5

    All tool names consistently follow a lowercase snake_case verb_noun pattern (list_, get_, create_, update_, promote_, publish_, upload_). The few longer names like upload_to_internal_sharing still fit the pattern clearly.

    Tool Count4/5

    16 tools is slightly above the ideal 3-15 range but appropriate given the server covers releases, artifacts, testers, and vitals. Each tool serves a distinct purpose and none feel redundant.

    Completeness4/5

    Core release lifecycle, artifact upload, tester management, and vitals monitoring are well covered. Minor gaps exist around removing artifacts/releases and listing all apps, but these are workable via existing tools.

    Maintenance

    ActivityInactive
    ResponsivenessResponsive

    Resources