play-console-mcp
An MCP server for inspecting and safely managing a Google Play Console app through Google Play APIs.
Read release state: tracks, releases, rollout status, bundles, and app overviews.
Manage releases: create releases, deploy AABs with mapping files and notes, promote releases, and update/halt/resume staged rollouts.
Upload artifacts: app bundles, deobfuscation files, internal-sharing builds, and listing images.
Inspect Android vitals: crash/ANR/slow-start/rendering/wakeup/wakelock rates, summaries, version comparisons, anomalies, error issues/reports, and data freshness.
Work with reviews: list, filter, get, and publicly reply with dry-run preview.
Manage store presence: list/update listings, app details, and images.
Manage testers: view and update tester Google Groups, with destructive replace gated off by default.
List visible apps and get a combined app overview.
Read install/rating statistics when
PLAY_MCP_REPORTS_BUCKETis configured.Check Digital Asset Links for Trusted Web Activities.
Use guarded writes with dry runs, explicit production confirmation, read-only mode, and destructive tools disabled by default.
Provides tools for interacting with the Google Play Console API, enabling management of app releases and staged rollouts, bundles, Android vitals, reviews, store listings, testers, app overviews, and Trusted Web Activity asset-link checks.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@play-console-mcp promote the latest bundle to production with a 10% staged rollout"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
play-console-mcp
An MCP server for the Google Play Console: releases and staged rollouts, Android vitals, reviews, store listing, testers, install and ratings statistics, and a Digital Asset Links check for Trusted Web Activities. Write tools are on by default but guarded, so a careless call gives you a preview, not a release.
stdio only (no network listener), Node ≥ 20
three runtime dependencies:
@modelcontextprotocol/sdk,zod,josesigns in with a service-account key or keylessly by impersonating the account from your gcloud login
talks straight to the Google REST APIs over
fetch; the bearer token can only go to a hard-coded list of Google hostspublished from CI with npm provenance, so you can check that the tarball was built from this repository
Install
Pin an exact version. Don't use a floating latest:
claude mcp add -s user play-console \
-e PLAY_MCP_KEY_PATH=/path/to/service-account.json \
-e PLAY_MCP_PACKAGE=com.example.app \
-- npx -y @ilativity/play-console-mcp@1.0.0Or in any MCP client's JSON config:
{
"mcpServers": {
"play-console": {
"command": "npx",
"args": ["-y", "@ilativity/play-console-mcp@1.0.0"],
"env": { "PLAY_MCP_KEY_PATH": "/path/to/service-account.json", "PLAY_MCP_READ_ONLY": "1" }
}
}
}Check the published build: npm view @ilativity/play-console-mcp@1.0.0 and the provenance
panel on npmjs.com.
Related MCP server: playstore-release-mcp
Service account: grant the narrowest role
The real security boundary is the service account's role in Play Console. This server's gates are a second layer on top of it.
In Google Cloud, create a service account and a JSON key, then enable the Google Play Android Developer API and the Google Play Developer Reporting API.
In Play Console → Users and permissions, invite the service account's email. Give it access to only the apps it needs, with only the permissions you want an agent to have. For a read-only setup that means View app information and View app quality information. Add the release permissions only if you'll use the release tools.
Keep the key file outside any repository.
Install and ratings statistics (optional)
Neither Play API serves install counts. Play writes them as monthly CSV files into a Cloud Storage bucket that belongs to your developer account, and the four stats tools read those files.
In Play Console → Users and permissions → the service account → Account permissions, turn on View app information and download bulk reports. It must be an account permission, not an app permission. A new grant can take hours, sometimes up to a day, to reach the bucket.
In Play Console → Manage account → Play apps reports → Statistics, press Copy Cloud Storage URI.
Set
PLAY_MCP_REPORTS_BUCKETto what you copied (for examplegs://pubsite_prod_1234567890/stats/installs/).
Only then does the server register the stats tools and ask Google for the extra
devstorage.read_only scope. Without the variable it requests exactly the scopes it always did.
Play posts the files with a 3–7 day delay, so the current month is always partial.
Keyless mode (no key file)
If your organisation discourages downloading service-account keys, let your own Google login impersonate the service account instead:
gcloud iam service-accounts add-iam-policy-binding <sa-email> \
--member=user:<you> --role=roles/iam.serviceAccountTokenCreator
gcloud auth application-default loginThen set PLAY_MCP_IMPERSONATE=<sa-email> and leave out the key variables. The server refreshes
your gcloud user token and exchanges it for a short-lived service-account token through the IAM
Credentials API. Every Play call is still made as the service account.
What this improves, and nothing more: no long-lived private key exists on disk. The gcloud file still holds a user refresh token, which is a secret too. You can revoke it from your Google account, and it can only mint tokens for service accounts you're allowed to impersonate.
Configuration
Variable | Meaning |
| Path to the service-account JSON key (preferred). |
| The key JSON inline (for secret managers). |
| Fallback key path. In keyless mode, the path of the gcloud ADC file (default: gcloud's own location). |
| Service-account email for keyless mode. When set, it wins over the key variables. |
| Default package name; every tool also accepts |
| Register only read tools. The client never sees a write tool. |
| Register the destructive tools (delete images or listings) and allow replacing a whole tester list. |
| If set, upload tools only read files under this directory. Symlinks are resolved first, so they can't escape it. |
| The reports bucket from Copy Cloud Storage URI ( |
The token is cached in memory only. The key and the token never appear in tool output or logs.
Safety model
Writes are on, but guarded. Use
PLAY_MCP_READ_ONLY=1to turn them off completely.There is no default rollout. A release with status
inProgressneedsrollout_percentage. Leaving it out is an error. It never becomes a silent 100%.Production needs explicit confirmation. Any write that touches
production(or a form-factor production track such aswear:production) needsconfirm_production: true. That covers creating, deploying, promoting into it, and changing, halting, resuming or completing its rollout. Without the flag the call runs as a dry run: the edit is validated, then discarded, and you get back what would have happened.Dry runs everywhere. Edit-based writes accept
validate_only.reply_to_reviewacceptsdry_run.Destructive tools are off unless you set
PLAY_MCP_ALLOW_DESTRUCTIVE=1.Every tool has MCP annotations (
readOnlyHint,destructiveHint,idempotentHint,openWorldHint), so your client can ask you before a write.Edits never leak. Every edit that isn't committed is deleted, whether the call fails or was a dry run. For apps with managed publishing, a commit that Google won't send for review is committed without sending, and the result tells you to send it from Play Console.
Releases keep what must stay. When a staged rollout starts, the completed release that still serves everyone else stays on the track.
promote_releasekeeps the destination's other releases instead of replacing them.
Tools
R = read, W = write, D = destructive (off by default).
Area | Tools |
Releases |
|
Bundles |
|
Vitals |
|
Reviews |
|
Store listing |
|
Testers |
|
Apps |
|
Statistics (needs |
|
TWA |
|
What the Play APIs don't offer
Google provides no API for these, so this server can't do them: the Data safety form, content rating, the production access questionnaire, and tester opt-in counts.
Two other limits are worth knowing:
Reviews: the API returns only reviews from about the last week. Older ones are in Play Console only.
Vitals: values lag a day or two. Use
vitals_freshnessto see the latest date available.
Out of scope on purpose: purchases, subscriptions, refunds and in-app products; managing Play Console users and permissions; app recovery; HTTP transport.
Development
npm ci
npm run lint && npm run typecheck && npm test
npm run build # → dist/Tests use vitest with fetch mocked: a stateful fake of the edits API, driven through a real
MCP client over an in-memory transport.
License
MIT, see LICENSE. Credits for design ideas are in NOTICE.md.
Available Tools
41 toolsanr_rateANR rateARead-onlyIdempotent
Daily anr rate from Android vitals (Play Developer Reporting API), including 7- and 28-day user-weighted values. Rates are fractions (0.01 = 1%).
Inputs: days, filter, dimensions, package_name.
app_overviewApp overviewARead-onlyIdempotent
"How is my app doing" in one call: release status on every track, the vitals summary against Google's thresholds, and the number of unanswered recent reviews. Each part reports its own error without failing the others.
Inputs: package_name.
check_asset_linksCheck Digital Asset LinksARead-onlyIdempotent
For a Trusted Web Activity: fetches https:///.well-known/assetlinks.json and compares its SHA-256 fingerprints for this package with the app-signing certificate Play reports (generatedApks). A mismatch is the classic reason a TWA shows the browser URL bar. Sends no credentials to the domain. If Play reports no signing certificate, pass fingerprint instead.
Inputs: domain (required), fingerprint, package_name, version_code.
crash_rateCrash rateARead-onlyIdempotent
Daily crash rate from Android vitals (Play Developer Reporting API), including 7- and 28-day user-weighted values. Rates are fractions (0.01 = 1%).
Inputs: days, filter, dimensions, package_name.
create_releaseCreate releaseA
Creates a release of already-uploaded version codes on a track. Keeps the track's other releases that must stay (e.g. the completed release during a staged rollout). Production requires confirm_production: true, otherwise this is a dry run.
Inputs: track (required), status (required), version_codes (required), package_name, +6 more.
deployDeployA
Uploads an .aab, optionally its mapping.txt, and creates the release with notes — all in ONE edit, so a failure at any step leaves nothing half-done. With validate_only (or on production without confirm_production) the bundle is uploaded into a throwaway edit, validated and discarded.
Inputs: track (required), status (required), file_path (required), package_name, +7 more.
excessive_wakeup_rateExcessive wakeup rateARead-onlyIdempotent
Daily excessive wakeup rate from Android vitals (Play Developer Reporting API), including 7- and 28-day user-weighted values. Rates are fractions (0.01 = 1%).
Inputs: days, filter, dimensions, package_name.
get_app_detailsGet app detailsBRead-onlyIdempotent
Returns the app's default language and contact email, phone and website.
Inputs: package_name.
get_listingGet store listingBRead-onlyIdempotent
Returns the store listing for one language.
Inputs: language (required), package_name.
get_reviewGet reviewBRead-onlyIdempotent
Returns one review with any developer reply.
Inputs: review_id (required), package_name, translation_language.
get_testersGet testersBRead-onlyIdempotent
Returns the Google Groups of testers for a testing track.
Inputs: track (required), package_name.
get_trackGet trackARead-onlyIdempotent
Returns one track with its full release objects, as Google reports them.
Inputs: track (required), package_name.
halt_rolloutHalt rolloutAIdempotent
Halts a staged rollout: no new users get the release (existing installs keep it). On production this requires confirm_production: true, otherwise it is a dry run.
Inputs: track (required), package_name, validate_only, confirm_production, +1 more.
list_anomaliesList anomaliesCRead-onlyIdempotent
Lists anomalies Google detected in the app's vitals metrics.
Inputs: filter, page_size, page_token, package_name.
list_appsList appsARead-onlyIdempotent
Lists the apps this service account can see, according to its Play permissions (Play Developer Reporting API apps:search).
Inputs: no named parameters.
list_bundlesList bundlesBRead-onlyIdempotent
Lists the app bundles (AABs) uploaded for the app, with version codes and hashes.
Inputs: package_name.
list_imagesList imagesCRead-onlyIdempotent
Lists the images of one type (screenshots, icon, feature graphic…) for a language.
Inputs: language (required), image_type (required), package_name.
list_listingsList store listingsARead-onlyIdempotent
Lists the store listing (title, descriptions) for every language.
Inputs: package_name.
list_releasesList releasesARead-onlyIdempotent
Lists releases on one track, or on every track when no track is given.
Inputs: track, package_name.
list_reviewsList reviewsARead-onlyIdempotent
Lists recent reviews, filterable by star rating, language and unanswered-only. The Play API only returns reviews created or edited in about the last week; older reviews are visible only in Play Console.
Inputs: limit, language, package_name, star_ratings, +2 more.
list_tracksList tracksBRead-onlyIdempotent
Lists the app's tracks and how many releases each has.
Inputs: package_name.
promote_releasePromote releaseA
Copies a release from one track to another (e.g. internal → production). The destination's other releases that must stay are kept, not replaced. Promoting into production requires confirm_production: true, otherwise this is a dry run.
Inputs: status (required), to_track (required), from_track (required), package_name, +7 more.
release_statusRelease statusARead-onlyIdempotent
One call, every track: each release's version codes, status, rollout percentage and halted flag, plus the highest version code per track.
Inputs: package_name.
reply_to_reviewReply to reviewAIdempotent
Posts a PUBLIC developer reply to a review (replacing any earlier reply). Max 350 characters. Use dry_run to preview without posting.
Inputs: review_id (required), reply_text (required), dry_run, package_name.
resume_rolloutResume rolloutAIdempotent
Resumes a halted rollout at the percentage you give (required — the previous percentage is not assumed). On production this requires confirm_production: true, otherwise it is a dry run.
Inputs: track (required), rollout_percentage (required), package_name, validate_only, +2 more.
search_error_issuesSearch error issuesCRead-onlyIdempotent
Searches grouped crash/ANR issues (Reporting API errorIssues:search).
Inputs: filter, order_by, page_size, page_token, +1 more.
search_error_reportsSearch error reportsBRead-onlyIdempotent
Searches individual crash/ANR reports with stack traces (Reporting API errorReports:search).
Inputs: filter, page_size, page_token, package_name.
slow_rendering_rateSlow rendering rateARead-onlyIdempotent
Daily slow rendering rate from Android vitals (Play Developer Reporting API), including 7- and 28-day user-weighted values. Rates are fractions (0.01 = 1%).
Inputs: days, filter, dimensions, package_name.
slow_start_rateSlow start rateARead-onlyIdempotent
Daily slow start rate from Android vitals (Play Developer Reporting API), including 7- and 28-day user-weighted values. Rates are fractions (0.01 = 1%).
Inputs: days, filter, dimensions, package_name.
stuck_wakelock_rateStuck background wakelock rateARead-onlyIdempotent
Daily stuck background wakelock rate from Android vitals (Play Developer Reporting API), including 7- and 28-day user-weighted values. Rates are fractions (0.01 = 1%).
Inputs: days, filter, dimensions, package_name.
update_app_detailsUpdate app detailsBIdempotent
Updates the app's default language and/or contact email, phone and website.
Inputs: package_name, contact_email, contact_phone, validate_only, +2 more.
update_listingUpdate store listingAIdempotent
Updates the store listing for one language. Only the fields you pass change. Limits: title 30, short description 80, full description 4000 characters.
Inputs: language (required), title, video, package_name, +3 more.
update_rolloutUpdate rolloutAIdempotent
Changes the percentage of a staged (inProgress) rollout, or completes it to 100% with complete: true. On production this requires confirm_production: true, otherwise it is a dry run.
Inputs: track (required), complete, package_name, validate_only, +3 more.
update_testersUpdate testersAIdempotent
Adds and/or removes tester Google Groups on a testing track and shows the before/after difference. Replacing the whole list (replace) is destructive and needs PLAY_MCP_ALLOW_DESTRUCTIVE=1.
Inputs: track (required), add, remove, replace, +2 more.
upload_bundleUpload bundleA
Uploads an Android App Bundle (.aab) to the app's bundle library without assigning it to a track. Files over 10 MB use a resumable upload. Use deploy to upload and release in one step.
Inputs: file_path (required), package_name, validate_only.
upload_deobfuscation_fileUpload deobfuscation fileAIdempotent
Uploads a ProGuard/R8 mapping.txt for a version code, so crash stack traces are readable.
Inputs: file_path (required), version_code (required), package_name.
upload_imageUpload imageB
Uploads one listing image (PNG or JPEG, max 15 MB) of the given type for a language.
Inputs: language (required), file_path (required), image_type (required), package_name, +1 more.
upload_internal_sharingUpload for internal app sharingA
Uploads an .aab or .apk to internal app sharing and returns a download link for testers. Bypasses tracks and review; links are for testing only.
Inputs: file_path (required), package_name.
vitals_by_versionVitals by versionARead-onlyIdempotent
Compares vitals across version codes over a window (weighted by daily users), newest first, with the change versus the previous version — to see whether the last release made things worse.
Inputs: days, metric_sets, package_name.
vitals_freshnessVitals freshnessBRead-onlyIdempotent
For each vitals metric set, the latest date (and hour) for which data is available.
Inputs: package_name.
vitals_summaryVitals summaryARead-onlyIdempotent
All six vitals at once: the latest 28-day user-weighted value of each, flagged against Google's bad-behaviour thresholds (user-perceived crash rate 1.09%, user-perceived ANR rate 0.47%).
Inputs: package_name.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Manage App Store and Google Play apps: listings, screenshots, builds, releases, reviews, metrics.
Unofficial 42matters MCP — wraps the 42matters App Market Data API (42matters.com)
Manage Meta apps: creation, configuration, webhooks, permissions, compliance, and App Review.
Server-side purchase verification and entitlements for Google Play and Apple App Store over MCP.
Related MCP Servers
- 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
- AlicenseAqualityDmaintenanceAn MCP server that drives Google Play releases: bundle upload, track releases (internal/closed/open/production), listing metadata, store graphics, and review replies.8MIT
- 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