The upload, the release, the rollout percentage and the crash and ANR rates all sit behind one connection — so the decision to widen a staged rollout can be made against the vitals in the same exchange that widens it.
A Google Play Console interface covering the release path end to end: artifacts, tracks and releases, testers, and the Android Vitals numbers that decide whether a rollout should continue. It runs locally, started and stopped by your client with each session.
- Every track — internal, alpha, beta, production — listed with its releases and country availability, and any one track inspected for status, rollout percentage and release notes
- Releases created or replaced on any track with rollout percentage, release notes and country targeting, then updated or promoted onward
- Artifacts uploaded and listed, plus upload to internal app sharing for the builds that are not going through a track
- Testers read and updated for the closed tracks
- An Android Vitals summary, with crash rate and ANR rate available separately
- Wakelock and wakeup rates, for the battery problems that only show up after release
A Google Cloud service account with Play Console access, its JSON key path given as GOOGLE_APPLICATION_CREDENTIALS. Install with uvx, which needs no separate install step, or with pip. stdio is the default and needs no server to start; an HTTP transport exists if you want one.
One command plus a key — pip install google-play-mcp, then supply credentials