Skip to main content
Glama
denshinji

play-console-mcp

by denshinji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

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

    • play-listings-mcp

      FrankBurmo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read and improve Google Play store listings for Android apps by fetching localized texts, creating validated local drafts with diffs, and optionally applying approved changes only after explicit confirmation.
      GPL 3.0

    • Google Play Console MCP

      abd3lraouf-studios
      A
      license
      B
      quality
      C
      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
      65 PyPI
      2
      Apache 2.0
    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

    B3.2/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions, and the edit lifecycle tools are well separated. Minor overlap exists between stage_store_dir and the lower-level listing/image tools, and between upload_bundle and set_track_release, though the descriptions clarify the intended boundaries.

    Naming Consistency4/5

    Almost all tools use consistent snake_case verb_noun naming. The main deviation is edit_summary, which is a noun phrase rather than a verb-led operation name.

    Tool Count4/5

    The 17 tools cover several distinct Google Play Console areas and each appears to earn its place. The total is slightly above the typical well-scoped range but remains reasonable for publishing, graphics, tracks, reviews, and edit management.

    Completeness4/5

    The surface covers the core publishing workflow: app details, listings, images, tracks, edit validation/commit, and review replies. There are minor gaps such as no explicit create_edit or update_app_details tool, but these are workable within the described flow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources