play-console-mcp
Related Servers
Alternatives to play-console-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables end-to-end Android app publishing to Google Play via the Developer API, including readiness checks, releases, promotions, reviews, and subscriptions.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables terminal and MCP clients to manage Google Play, App Store Connect, and AdMob through official APIs, including listings, releases, reviews, vitals, sales, and reports, with dry-run safety by default.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to query Google Play app reviews, ratings, crash and ANR rates, and release information, with an optional tool for replying to reviews. It connects through the Play Developer and Reporting APIs using a service account, and can also run in a mock mode without Google access.1MIT
- AlicenseAqualityDmaintenanceAn MCP server that drives Google Play releases: bundle upload, track releases (internal/closed/open/production), listing metadata, store graphics, and review replies.8MIT
- AlicenseAqualityBmaintenanceEnables AI agents to upload Android builds, manage tracks and staged rollouts, edit store listings and screenshots, manage in-app products and subscriptions, and read or reply to reviews through the Android Publisher API, with dry-run and safe-mode guardrails.72369 npm1MIT
- AlicenseNot gradedqualityDmaintenanceManages Google Play Store listing text through the official Android Publisher API with dry-run-first safety, supporting CLI for humans/CI and MCP tools for agents.MIT
TDQS
Scored across 41 tools
Most tools have clearly distinct purposes: upload_internal_sharing, upload_bundle and deploy are cleanly separated by intent, and the six vitals metrics are individually identifiable. The main overlap cluster is list_tracks/get_track/list_releases/release_status, four tools that all describe track-and-release state with subtly different scopes, which could cause misselection.
The action family consistently uses verb_noun snake_case (list_releases, create_release, promote_release, update_rollout, halt_rollout, reply_to_review), and the vitals family consistently uses metric-noun names (crash_rate, anr_rate, vitals_summary). A few noun-only names like release_status and app_overview deviate from the verb_noun convention, but the pattern stays predictable overall.
41 tools is well above the well-scoped range and sits in the heavy category, even accounting for the fact that Play Console spans releases, vitals, reviews, listings, images and testers. Some consolidation is plausible (e.g. merging track/release listing tools, or wrapping per-metric vitals tools behind a parameterised call).
Coverage is unusually thorough across release/rollout lifecycle, bundle uploads, vitals and error reporting, reviews, listings, images, testers and app details, with sensible dry-run/confirm semantics. Remaining gaps are adjacent domains rather than dead ends: no monetization (in-app products/subscriptions), no release deletion or rollback, and no way to create or manage tracks themselves.