
Google Play Console MCP
io.github.AgiMaulanaPublished by GitHub account AgiMaulanav0.5.0Updated Oct 24, 2026
Google Play release lifecycle: tracks, testers, rollout, and Android Vitals.
Overview
A local MCP server that lets an assistant manage Google Play releases, testers, artifacts and Android Vitals through the Play Console APIs.
- What you can do
- List tracks and inspect a track's status, rollout percentage and release notes, and create, update, halt, resume or promote releases between tracks and stages of rollout. List APKs and AABs with version codes and hashes, upload an artifact and create a release in one step, or push a build to Internal App Sharing for a shareable link. Read and replace tester email lists and Google Groups for internal and closed testing tracks. Read Android Vitals: daily crash, ANR, stuck wake lock and excessive wakeup rates per version code, plus a combined summary with threshold flags.
- When to use it
- Useful when you ship Android apps and want an assistant to handle Play Store release chores: staged rollouts, track promotion, tester list changes, artifact uploads and checking crash or ANR health before or after a release.
- Requirements
- Runs locally as a Python package (uvx or pip install). Needs a Google Cloud service account JSON key, passed as the absolute path in GOOGLE_APPLICATION_CREDENTIALS, added to Play Console with the right account- and app-level permissions. The Google Play Android Developer API and Google Play Developer Reporting API must be enabled in the Cloud project.
Installation
In SourceWeft
- Open Google Play Console MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Google Play Console MCP
[Google Play Console MCP server]
[GooglePlayConsoleMcp MCP server] [MCP Badge] [License: MIT]
A Python Model Context Protocol server that lets AI assistants (Claude, etc.) manage the full Google Play Store release lifecycle directly — from uploading artifacts to managing testers, rollouts, and Android Vitals.
Quick start
Option A — uvx (recommended, no install needed)
Run this once. Claude automatically starts and stops the server for every session — you never have to touch it again.
Requires
uv— install withbrew install uvorcurl -Lsf https://astral.sh/uv/install.sh | sh
Option B — pip install
If you prefer a permanent install:
Option C — HTTP (local server)
Only needed if you want to connect via HTTP transport instead of stdio:
How stdio works: With Options A and B, there is no server to start manually. Claude launches the process in the background when a session opens and shuts it down when the session ends. Zero maintenance.
Features
Tracks & Releases
Artifact Management
Tester Management
Android Vitals
Prerequisites
uv— install guide- A Google Cloud service account with the JSON key downloaded.
- The service account added to Google Play Console with the correct permissions (see below).
- These APIs enabled in your Google Cloud project:
Required Play Console permissions
Important: Release Manager does not grant Reporting API access. You must also enable View app information and download bulk reports (read-only) — both at account level and per-app level — for the Vitals tools to work.
Claude Desktop integration
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
Restart Claude Desktop after saving.
Service account setup
- Go to IAM & Admin → Service Accounts in your GCP project.
- Create a service account (or use an existing one) and download a JSON key.
- In Google Play Console → Setup → API access:
- Link your Google Cloud project.
- Find the service account → Manage Play Console permissions.
- Under Account permissions, enable View app information and download bulk reports (read-only).
- Under App permissions for each app, enable:
- View app information and download bulk reports (read-only)
- Release to production… (if you need write access)
- Click Apply → Invite user.
Permissions must be granted at both account level and per-app level. Account-level alone is not sufficient for the Reporting API.
Tool reference
list_tracks
Returns all tracks with their releases, rollout percentages, statuses, and country availability.
get_track_info
Returns a human-readable summary plus releases with status, rollout %, version codes, and release notes.
create_release
Creates or replaces a release on the given track. Use status="inProgress" with a
rollout_percentage for a staged production rollout, or status="completed" to release
to all users immediately.
update_release
Update an existing release. Common use cases:
- Increase rollout:
update_release(pkg, rollout_percentage=50) - Complete rollout:
update_release(pkg, rollout_percentage=100) - Halt rollout:
update_release(pkg, status="halted") - Resume rollout:
update_release(pkg, status="inProgress")
promote_release
Copies a release from one track to another. Release notes and name are inherited from the source release unless explicitly overridden.
list_artifacts
Returns all APKs and AABs sorted by version code (newest first) with SHA hashes.
upload_artifact
Uploads an APK or AAB (auto-detected from extension) and creates a release on the given track in a single atomic operation. Returns the assigned version code.
upload_to_internal_sharing
Uploads a build to Internal App Sharing (bypasses track assignment) and returns a
shareable downloadUrl. Testers must have Internal App Sharing enabled in their Play
Store settings. Ideal for quick one-off testing without affecting any release track.
get_testers
Returns the list of tester email addresses and Google Groups for the track.
update_testers
Warning: This is a full replacement. Testers not in the new list will lose access. Call
get_testersfirst to retrieve the current list if you only want to add/remove individuals.
get_crash_rate
Returns daily crashRate, userPerceivedCrashRate, and distinctUsers per version code.
Google's bad behavior threshold for user-perceived crash rate is ~1.09%.
get_anr_rate
Returns daily anrRate, userPerceivedAnrRate, and distinctUsers per version code.
Google's bad behavior threshold for user-perceived ANR rate is ~0.47%.
get_vitals_summary
Returns a combined crash + ANR summary aggregated per version code, with averages over
the period and exceedsCrashThreshold / exceedsAnrThreshold flags. The latest version
is highlighted as latestVersionSummary.
get_wakelock_rate
Returns daily stuckBackgroundWakelockRate and distinctUsers per version code.
Relevant for 2026 Google Play battery health enforcement — apps with an excessive
proportion of sessions holding a partial wake lock for more than 1 hour in the background
may be penalized.
get_wakeup_rate
Returns daily excessiveWakeupRate and distinctUsers per version code.
Relevant for 2026 Google Play battery health enforcement — apps that wake the CPU too
frequently (above platform thresholds) may be penalized.
Troubleshooting
403 Forbidden on Vitals tools
This error has two common causes — check both:
1. Google Play Developer Reporting API not enabled
Enable it in your Google Cloud project: console.cloud.google.com/apis/library/playdeveloperreporting.googleapis.com
2. Service account lacks per-app Reporting API access
- Play Console → Setup → API access → find the service account → Manage Play Console permissions.
- Under App permissions, select the app and enable View app information and download bulk reports (read-only).
- Save and wait a few minutes for the change to propagate.
404 Package not found
The service account must be linked to the same Google Play Console account that owns the app. Go to Play Console → Setup → API access and verify the service account is listed and has been invited.
Marketplaces
License
MIT
Source: README.md at commit 9003e63
Tools
0Version history
1- v0.5.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts