Skip to main content
Glama
play-console-mcp
by ilativity

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, jose

  • signs 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 hosts

  • published 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.0

Or 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.

  1. 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.

  2. 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.

  3. 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.

  1. 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.

  2. In Play Console → Manage account → Play apps reports → Statistics, press Copy Cloud Storage URI.

  3. Set PLAY_MCP_REPORTS_BUCKET to what you copied (for example gs://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 login

Then 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

PLAY_MCP_KEY_PATH

Path to the service-account JSON key (preferred).

PLAY_MCP_KEY

The key JSON inline (for secret managers).

GOOGLE_APPLICATION_CREDENTIALS

Fallback key path. In keyless mode, the path of the gcloud ADC file (default: gcloud's own location).

PLAY_MCP_IMPERSONATE

Service-account email for keyless mode. When set, it wins over the key variables.

PLAY_MCP_PACKAGE

Default package name; every tool also accepts package_name.

PLAY_MCP_READ_ONLY=1

Register only read tools. The client never sees a write tool.

PLAY_MCP_ALLOW_DESTRUCTIVE=1

Register the destructive tools (delete images or listings) and allow replacing a whole tester list.

PLAY_MCP_FILE_ROOT

If set, upload tools only read files under this directory. Symlinks are resolved first, so they can't escape it.

PLAY_MCP_REPORTS_BUCKET

The reports bucket from Copy Cloud Storage URI (gs://pubsite_prod_…, with or without the path, or the bare name). Turns on the stats tools and the read-only storage scope.

The token is cached in memory only. The key and the token never appear in tool output or logs.

Safety model

  1. Writes are on, but guarded. Use PLAY_MCP_READ_ONLY=1 to turn them off completely.

  2. There is no default rollout. A release with status inProgress needs rollout_percentage. Leaving it out is an error. It never becomes a silent 100%.

  3. Production needs explicit confirmation. Any write that touches production (or a form-factor production track such as wear:production) needs confirm_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.

  4. Dry runs everywhere. Edit-based writes accept validate_only. reply_to_review accepts dry_run.

  5. Destructive tools are off unless you set PLAY_MCP_ALLOW_DESTRUCTIVE=1.

  6. Every tool has MCP annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint), so your client can ask you before a write.

  7. 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.

  8. Releases keep what must stay. When a staged rollout starts, the completed release that still serves everyone else stays on the track. promote_release keeps the destination's other releases instead of replacing them.

Tools

R = read, W = write, D = destructive (off by default).

Area

Tools

Releases

list_tracks R, get_track R, list_releases R, release_status R (all tracks in one call), create_release W, deploy W (upload AAB, add mapping, create release and notes in one edit), promote_release W, update_rollout W, halt_rollout W, resume_rollout W

Bundles

list_bundles R, upload_bundle W (resumable above 10 MB), upload_deobfuscation_file W, upload_internal_sharing W

Vitals

crash_rate, anr_rate, slow_start_rate, slow_rendering_rate, excessive_wakeup_rate, stuck_wakelock_rate, vitals_summary (flagged against Google's thresholds: user-perceived crash rate 1.09%, ANR rate 0.47%), vitals_by_version (did the last release make things worse?), search_error_issues, search_error_reports, list_anomalies, vitals_freshness. All R

Reviews

list_reviews R (filter by stars, language, unanswered only), get_review R, reply_to_review W (public; 350-character limit; dry_run)

Store listing

list_listings, get_listing, get_app_details, list_images R; update_listing, update_app_details, upload_image (PNG/JPEG, 15 MB) W; delete_image, delete_all_images, delete_listing D

Testers

get_testers R, update_testers W (add/remove with a before/after diff; replace is D)

Apps

list_apps R (the apps this service account can see), app_overview R (release status, vitals and unanswered reviews in one answer)

Statistics (needs PLAY_MCP_REPORTS_BUCKET)

list_reports R (which months and dimensions exist; the cheapest access check), get_install_stats R (one month: per-day rows and totals, or by country, device, app version, … with top-N and other), install_trend R (month by month with the change from the previous month), get_ratings_stats R (daily and lifetime average rating; never a meaningless mean of daily averages)

TWA

check_asset_links R: compares https://<domain>/.well-known/assetlinks.json with the app-signing certificate Play reports. A mismatch is the usual reason a TWA shows the browser URL bar. This is the only tool that contacts a non-Google host, and it sends no credentials there.

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_freshness to 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 tools
anr_rateANR rateA
Read-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 overviewA
Read-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.

crash_rateCrash rateA
Read-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 rateA
Read-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 detailsB
Read-onlyIdempotent

Returns the app's default language and contact email, phone and website.

Inputs: package_name.

get_listingGet store listingB
Read-onlyIdempotent

Returns the store listing for one language.

Inputs: language (required), package_name.

get_reviewGet reviewB
Read-onlyIdempotent

Returns one review with any developer reply.

Inputs: review_id (required), package_name, translation_language.

get_testersGet testersB
Read-onlyIdempotent

Returns the Google Groups of testers for a testing track.

Inputs: track (required), package_name.

get_trackGet trackA
Read-onlyIdempotent

Returns one track with its full release objects, as Google reports them.

Inputs: track (required), package_name.

halt_rolloutHalt rolloutA
Idempotent

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 anomaliesC
Read-onlyIdempotent

Lists anomalies Google detected in the app's vitals metrics.

Inputs: filter, page_size, page_token, package_name.

list_appsList appsA
Read-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 bundlesB
Read-onlyIdempotent

Lists the app bundles (AABs) uploaded for the app, with version codes and hashes.

Inputs: package_name.

list_imagesList imagesC
Read-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 listingsA
Read-onlyIdempotent

Lists the store listing (title, descriptions) for every language.

Inputs: package_name.

list_releasesList releasesA
Read-onlyIdempotent

Lists releases on one track, or on every track when no track is given.

Inputs: track, package_name.

list_reviewsList reviewsA
Read-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 tracksB
Read-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 statusA
Read-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 reviewA
Idempotent

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 rolloutA
Idempotent

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 issuesC
Read-onlyIdempotent

Searches grouped crash/ANR issues (Reporting API errorIssues:search).

Inputs: filter, order_by, page_size, page_token, +1 more.

search_error_reportsSearch error reportsB
Read-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 rateA
Read-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 rateA
Read-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 rateA
Read-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 detailsB
Idempotent

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 listingA
Idempotent

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 rolloutA
Idempotent

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 testersA
Idempotent

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 fileA
Idempotent

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 versionA
Read-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 freshnessB
Read-onlyIdempotent

For each vitals metric set, the latest date (and hour) for which data is available.

Inputs: package_name.

vitals_summaryVitals summaryA
Read-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

    B3.4/5.0

    Scored across 41 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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).

    Completeness4/5

    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

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers