list_tracksLABSCO SUMMARY
Shipping and watching the result stop being two different tools.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command plus credentials — pip install google-play-mcp, then supply credentials
USE CASES
01
Shipping a new version to a track
Upload the artifact and create the release on the track you want, with the release notes and the initial rollout percentage set in the same step.
02
Deciding whether to widen a staged rollout
Read the crash rate and ANR rate for the version that is out, then move the rollout percentage up — or leave it — based on what they say.
03
Moving a build from testing to production
Promote the release from the track it was validated on rather than uploading it again, so what reaches production is the artifact that was actually tested.
04
Getting a build to testers quickly
Upload to internal app sharing for a build that does not need a track, or update the tester list on a closed track when the audience is what changed.
05
Checking the health of what is already live
Pull the Vitals summary in one call for a broad reading, before deciding which specific rate is worth digging into.
06
Chasing battery complaints
Read the wakelock and wakeup rates, which are where a release that looks stable on crashes turns out to be draining phones.
15 tools
Listed in project docs. Your client may show a different list.
get_track_infocreate_releaseupdate_releasepromote_releaselist_artifactsupload_artifactupload_to_internal_sharingget_testersupdate_testersget_crash_rateget_anr_rateget_vitals_summaryget_wakelock_rateget_wakeup_rateBEFORE YOU INSTALL
What to know first
Tools you get
15 tools named in the project's documentation.
Requires
GOOGLE_APPLICATION_CREDENTIALS in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
pip install google-play-mcpMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add google-play-mcp \
-e GOOGLE_APPLICATION_CREDENTIALS=<YOUR_GOOGLE_APPLICATION_CREDENTIALS> \
-- uvx google-play-mcpClaude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"google-play": {
"command": "uvx",
"args": [
"google-play-mcp"
],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "<YOUR_GOOGLE_APPLICATION_CREDENTIALS>"
}
}
}
}
