A
licenseNot graded
qualityD
maintenanceEnables to interact with Google Play Console, allowing release management, app vitals monitoring, and APK/AAB deployment via a service account.
MIT
Google Play Console
by AgiMaulana
This server lets you manage the full Google Play Store release lifecycle — from uploading builds to monitoring Android Vitals — directly through an AI assistant.
Tracks & Releases:
list_tracks— List all release tracks (internal, alpha, beta, production) with rollout percentages, statuses, and country availabilityget_track_info— Get detailed info for a specific track including releases, version codes, and release notescreate_release— Create or replace a release on any track with rollout %, status, release notes, and country targetingupdate_release— Update rollout %, halt, resume, or complete an existing releasepromote_release— Promote a release between tracks (e.g. internal → alpha → beta → production)publish_managed_release— Send approved changes live when Managed Publishing is enabled
Artifact Management:
list_artifacts— List all APKs and AABs with version codes and SHA hashesupload_artifact— Upload an APK or AAB and create a release on a track in one atomic stepupload_to_internal_sharing— Upload a build to Internal App Sharing and get a shareable download URL
Tester Management:
get_testers— Retrieve tester email addresses and Google Groups for internal/alpha tracksupdate_testers— Replace the tester list for an internal or alpha testing track
Android Vitals:
get_crash_rate— Fetch daily crash rate and user-perceived crash rate by version codeget_anr_rate— Fetch daily ANR rate and user-perceived ANR rate by version codeget_vitals_summary— Get a combined crash + ANR overview with bad behavior threshold flagsget_wakelock_rate— Fetch stuck background wake lock rate by version code (battery health)get_wakeup_rate— Fetch excessive CPU wakeup rate by version code (battery health)
Provides tools to monitor Android Vitals, including crash rates, ANR rates, and battery-related metrics like wakelocks and excessive wakeups.
Integrates with Google Cloud projects and service accounts to authenticate and access the Google Play Android Developer and Reporting APIs.
Automates the full Google Play Store release lifecycle, including artifact uploads, release track management, staged rollouts, and tester administration.
Google Play Console MCP
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.
claude mcp add google-play-mcp \
-e GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json \
-- uvx google-play-mcpRequires
uv— install withbrew install uvorcurl -Lsf https://astral.sh/uv/install.sh | sh
Option B — pip install
If you prefer a permanent install:
pip install google-play-mcp
claude mcp add google-play-mcp \
-e GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json \
-- google-play-mcpOption C — HTTP (local server)
Only needed if you want to connect via HTTP transport instead of stdio:
# Terminal 1 — start the server
GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json \
uvx google-play-mcp --transport http --port 8080
# Terminal 2 — register with Claude
claude mcp add --transport http google-play-mcp http://localhost:8080How 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.
Related MCP server: Google Play Store MCP Server
Features
Tracks & Releases
Tool | Description |
| List all tracks (internal, alpha, beta, production) with releases and country availability |
| Get detailed status, rollout %, and release notes for a specific track |
| Create or replace a release on any track with rollout %, release notes, and country targeting |
| Update rollout %, halt, resume, or complete an existing release |
| Promote a release between tracks (e.g. internal → alpha → beta → production) |
Artifact Management
Tool | Description |
| List all APKs and AABs with their version codes and SHA hashes |
| Upload an APK or AAB and create a release on a track in one step |
| Upload a build to Internal App Sharing and get a shareable download URL |
Tester Management
Tool | Description |
| Get tester email addresses and Google Groups for internal/closed testing |
| Replace the tester list for an internal or closed testing track |
Android Vitals
Tool | Description |
| Daily crash rate and user-perceived crash rate by version code |
| Daily ANR rate and user-perceived ANR rate by version code |
| Combined crash + ANR overview with bad behavior threshold indicators |
| Daily stuck background wake lock rate by version code (battery health) |
| Daily excessive wakeup rate by version code (battery health) |
Prerequisites
uv— install guideA 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
Tools | Minimum permission required |
| Release to production, exclude devices, and use app signing by Google Play |
| Release to testing tracks |
| View app information and download bulk reports (read-only) |
| View app information and download bulk reports (read-only) + Reporting API enabled |
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):
{
"mcpServers": {
"google-play": {
"command": "uvx",
"args": ["google-play-mcp"],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "/absolute/path/to/service-account.json"
}
}
}
}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
package_name : str — e.g. "com.example.myapp"Returns all tracks with their releases, rollout percentages, statuses, and country availability.
get_track_info
package_name : str
track : str — "internal" | "alpha" | "beta" | "production" (default: "production")Returns a human-readable summary plus releases with status, rollout %, version codes, and release notes.
create_release
package_name : str
track : str — "internal" | "alpha" | "beta" | "production"
version_codes : list[int] — e.g. [1042]
rollout_percentage : float — default 10.0 (used when status is "inProgress")
status : str — "draft" (default) | "inProgress" | "halted" | "completed"
release_name : str — optional
release_notes : dict — optional, e.g. {"en-US": "Bug fixes", "fr-FR": "Corrections"}
country_codes : list[str] — optional ISO 3166-1 alpha-2 codes, e.g. ["US", "GB"]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
package_name : str
track : str — default "production"
rollout_percentage : float — optional; pass 100 to complete the rollout
status : str — optional; "inProgress" | "halted" | "completed" | "draft"
version_codes : list[int] — optional filter; targets first matching release if omittedUpdate 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
package_name : str
from_track : str — "internal" | "alpha" | "beta"
to_track : str — "alpha" | "beta" | "production"
version_codes : list[int]
rollout_percentage : float — default 10.0
release_name : str — optional override
release_notes : dict — optional override; inherits from source if omittedCopies a release from one track to another. Release notes and name are inherited from the source release unless explicitly overridden.
list_artifacts
package_name : strReturns all APKs and AABs sorted by version code (newest first) with SHA hashes.
upload_artifact
package_name : str
file_path : str — absolute local path to .apk or .aab
track : str — default "internal"
status : str — "draft" (default) | "inProgress" | "completed"
rollout_percentage : float — default 10.0 (used when status is "inProgress")
release_name : str — optional
release_notes : dict — optionalUploads 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
package_name : str
file_path : str — absolute local path to .apk or .aabUploads 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
package_name : str
track : str — "internal" (default) | "alpha"Returns the list of tester email addresses and Google Groups for the track.
update_testers
package_name : str
track : str — "internal" (default) | "alpha"
emails : list[str] — optional; full replacement list of tester emails
google_groups : list[str] — optional; full replacement list of Google Group emailsWarning: 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
package_name : str
days : int — look-back window, 1–30 (default 7)
version_code : str — optional single version code to filterReturns daily crashRate, userPerceivedCrashRate, and distinctUsers per version code.
Google's bad behavior threshold for user-perceived crash rate is ~1.09%.
get_anr_rate
package_name : str
days : int — look-back window, 1–30 (default 7)
version_code : str — optional single version code to filterReturns daily anrRate, userPerceivedAnrRate, and distinctUsers per version code.
Google's bad behavior threshold for user-perceived ANR rate is ~0.47%.
get_vitals_summary
package_name : str
days : int — look-back window, 1–30 (default 7)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
package_name : str
days : int — look-back window, 1–30 (default 7)
version_code : str — optional single version code to filterReturns 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
package_name : str
days : int — look-back window, 1–30 (default 7)
version_code : str — optional single version code to filterReturns 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
403 Client Error: Forbidden for url: https://playdeveloperreporting.googleapis.com/...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
Registry | Link |
| |
search | |
|
License
MIT
Available Tools
16 toolscreate_releaseA
Create or replace a release on a track.
NOTE: With Managed Publishing enabled, the edit is held pending approval. Call publish_managed_release to send live.
Args: package_name: Package name, e.g. com.example.myapp track: "internal", "alpha", "beta", or "production". version_codes: Version codes to include, e.g. [1234]. rollout_percentage: Rollout % when status is "inProgress". Default 10%. status: "draft" (default), "inProgress" (staged), "halted", or "completed". release_name: Optional human-readable name. release_notes: Optional {lang: text} dict, e.g. {"en-US": "Bug fixes"}. country_codes: Optional ISO 3166-1 alpha-2 codes. Empty list removes restrictions. submit_for_review: If True, submits changes for Google Play review. Set to False to keep as draft without submitting for review.
Inputs: track (required), package_name (required), version_codes (required), status, +5 more.
get_anr_rateA
Fetch ANR (Application Not Responding) rate from Android Vitals.
Returns daily anrRate, userPerceivedAnrRate, and distinctUsers by version code. Bad behavior threshold: userPerceivedAnrRate > 0.47% may cause Play Store ranking penalties.
Args: package_name: Package name, e.g. com.example.myapp days: Past days to include (default 7, max 30). version_code: Optional version code filter.
Inputs: package_name (required), days, version_code.
get_crash_rateA
Fetch user-perceived crash rate from Android Vitals.
Returns daily crashRate, userPerceivedCrashRate, and distinctUsers by version code. Bad behavior threshold: userPerceivedCrashRate > 1.09% may cause Play Store ranking penalties.
Args: package_name: Package name, e.g. com.example.myapp days: Past days to include (default 7, max 30). version_code: Optional version code filter.
Inputs: package_name (required), days, version_code.
get_testersB
Get tester emails and Google Groups for an internal or alpha track.
Args: package_name: Package name, e.g. com.example.myapp track: "internal" (default) or "alpha".
Inputs: package_name (required), track.
get_track_infoA
Get detailed info for a specific release track.
Returns releases with status, rollout %, version codes, release notes, and country availability.
Args: package_name: Package name, e.g. com.example.myapp track: "internal", "alpha", "beta", or "production". Default "production".
Inputs: package_name (required), track.
get_vitals_summaryA
Get combined Android Vitals: crash rate and ANR rate per version code.
Returns averages over the period with threshold flags. Thresholds: userPerceivedCrashRate > 1.09%, userPerceivedAnrRate > 0.47%.
Args: package_name: Package name, e.g. com.example.myapp days: Past days to include (default 7, max 30).
Inputs: package_name (required), days.
get_wakelock_rateA
Fetch stuck background wake lock rate from Android Vitals.
Returns daily stuckBackgroundWakelockRate and distinctUsers by version code. Excessive wakelock holding (>1 hour in background) may be penalized.
Args: package_name: Package name, e.g. com.example.myapp days: Past days to include (default 7, max 30). version_code: Optional version code filter.
Inputs: package_name (required), days, version_code.
get_wakeup_rateB
Fetch excessive CPU wakeup rate from Android Vitals.
Returns daily excessiveWakeupRate and distinctUsers by version code. Frequent CPU wakeups above platform thresholds may be penalized.
Args: package_name: Package name, e.g. com.example.myapp days: Past days to include (default 7, max 30). version_code: Optional version code filter.
Inputs: package_name (required), days, version_code.
list_artifactsA
List all APKs and AABs uploaded to the app.
Returns version codes and SHA hashes. Useful for finding version codes available to assign to a track.
Args: package_name: Package name, e.g. com.example.myapp
Inputs: package_name (required).
list_tracksA
List all release tracks with their current releases.
Returns tracks (internal, alpha, beta, production) with rollout percentages, statuses, and country availability.
Args: package_name: Package name, e.g. com.example.myapp
Inputs: package_name (required).
promote_releaseA
Promote a release from one track to another.
Copies version codes from source to destination. Common: internal→alpha→beta→production. Release notes/name are inherited unless overridden.
Args: package_name: Package name, e.g. com.example.myapp from_track: Source — "internal", "alpha", or "beta". to_track: Destination — "alpha", "beta", or "production". version_codes: Version codes to promote, e.g. [1234]. rollout_percentage: Rollout % at destination. Default 10%. Use 100 for full release. release_name: Optional name override. release_notes: Optional {lang: text} override, e.g. {"en-US": "New features"}. submit_for_review: If True, submits changes for Google Play review. Set to False to keep as draft without submitting for review.
Inputs: to_track (required), from_track (required), package_name (required), version_codes (required), +4 more.
publish_managed_releaseA
Send approved changes live when Managed Publishing is enabled.
Call after changes committed via create_release/update_release/promote_release have been reviewed in Play Console. No-op if Managed Publishing is off.
Args: package_name: Package name, e.g. com.example.myapp
Inputs: package_name (required).
update_releaseA
Update rollout percentage and/or status of an existing release.
Examples: increase rollout (rollout_percentage=50), complete (=100), halt (status="halted"), resume (status="inProgress").
NOTE: With Managed Publishing enabled, changes are held pending approval. Call publish_managed_release to send live.
Args: package_name: Package name, e.g. com.example.myapp track: Track to update. Default "production". rollout_percentage: New rollout % (0–100). Pass 100 to complete. status: "inProgress", "halted", "completed", or "draft". version_codes: Filter to release containing these codes. Default: first release found. submit_for_review: If True, submits changes for Google Play review. Set to False to keep as draft without submitting for review.
Inputs: package_name (required), track, status, version_codes, +2 more.
update_testersA
Replace the tester list for an internal or alpha track.
WARNING: Full replacement — omitted testers lose access. Call get_testers first to preserve existing testers.
Args: package_name: Package name, e.g. com.example.myapp track: "internal" (default) or "alpha". emails: Tester email addresses. Empty list removes all individuals. google_groups: Google Group addresses. Empty list removes all groups. submit_for_review: If True, submits changes for Google Play review. Set to False to keep as draft without submitting for review.
Inputs: package_name (required), track, emails, google_groups, +1 more.
upload_artifactA
Upload an APK or AAB and create a release on the given track.
File type auto-detected from extension (.apk/.aab). Upload and track assignment are atomic.
Args: package_name: Package name, e.g. com.example.myapp file_path: Absolute local path to the APK or AAB. track: "internal" (default), "alpha", "beta", or "production". status: "draft" (default), "inProgress", or "completed". rollout_percentage: Rollout % when status is "inProgress". Default 10%. release_name: Optional human-readable name. release_notes: Optional {lang: text} dict, e.g. {"en-US": "Initial release"}. submit_for_review: If True, submits changes for Google Play review. Set to False to keep as draft without submitting for review.
Inputs: file_path (required), package_name (required), track, status, +4 more.
upload_to_internal_sharingA
Upload APK or AAB to Internal App Sharing and get a shareable link.
Shares a build via URL without assigning it to a track. Ideal for quick one-off testing. File type auto-detected from extension (.apk/.aab).
Args: package_name: Package name, e.g. com.example.myapp file_path: Absolute local path to the APK or AAB.
Inputs: file_path (required), package_name (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
A3.9/5.0
Scored across 16 tools
Disambiguation4/5
Most tools target clearly distinct resources and actions, but list_tracks and get_track_info overlap somewhat, and create_release vs upload_artifact could be confused since upload_artifact also creates a release. Descriptions are specific enough to resolve most ambiguity.
Naming Consistency5/5
All tool names consistently follow a lowercase snake_case verb_noun pattern (list_, get_, create_, update_, promote_, publish_, upload_). The few longer names like upload_to_internal_sharing still fit the pattern clearly.
Tool Count4/5
16 tools is slightly above the ideal 3-15 range but appropriate given the server covers releases, artifacts, testers, and vitals. Each tool serves a distinct purpose and none feel redundant.
Completeness4/5
Core release lifecycle, artifact upload, tester management, and vitals monitoring are well covered. Minor gaps exist around removing artifacts/releases and listing all apps, but these are workable via existing tools.
Maintenance
ActivityInactive
ResponsivenessNo recent community issues
Related MCP Connectors
Manage App Store and Google Play apps: listings, screenshots, builds, releases, reviews, metrics.
Share iOS and Android test builds: upload, install links, testers, store readiness and releases.
Ship a new Android app from chat. AI runs Google Play Console listings, screenshots, releases, uplo…
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to automate Android release workflows via the Google Play Android Publisher API, including deploying builds, managing listings, and replying to reviews.40MIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage Google Play Console reviews and Android app releases, including replying to reviews, promoting releases, managing staged rollouts, and checking crash/ANR vitals.4460 npm2MIT
- AlicenseBqualityBmaintenanceEnables 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.17059 PyPI2Apache 2.0