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

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

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

    • playstore-release-mcp

      rabdulsal
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that drives Google Play releases: bundle upload, track releases (internal/closed/open/production), listing metadata, store graphics, and review replies.
      8
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.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