play-store-mcp
Provides tools for managing app releases, store listings, reviews, monetization, testers, and analytics for Google Play Console.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
play-store-mcp
Local stdio MCP server for Google Play Console. Credentials (a Google service-account
key) come only from environment variables; OAuth tokens are minted locally by
google-auth-library; every request goes directly to *.googleapis.com. Nothing is sent to
any third party.
TypeScript reimplementation — the Kotlin project antoniolg/play-store-mcp
was used only as a reference for the API flow and tool design.
Available tools
23 tools, grouped by capability.
Releases & rollout
Tool | Description | Key inputs |
| Current releases/deployments per track |
|
| Upload an APK/AAB and assign it to a track (optional staged rollout) |
|
| Promote an existing version from one track to another |
|
| Change a staged-rollout fraction, or halt/complete the in-progress release |
|
| Batch-complete the in-progress staged rollout across multiple apps |
|
| Set release notes on the current release of a track (no redeploy) |
|
Store listing
Tool | Description | Key inputs |
| Store listing text (title, short/full description) for every locale |
|
| Update a store listing for one locale and commit |
|
| App-level details (default language, contact email/phone/website) |
|
| Upload a store-listing graphic (icon, screenshots, feature graphic, …) for a locale |
|
Reviews
Tool | Description | Key inputs |
| Recent user reviews (rating, text, app version, device) |
|
| Post a developer reply to a user review |
|
Monetization
Tool | Description | Key inputs |
| List managed in-app products (SKUs) |
|
| List subscription products |
|
| Update an existing managed IAP (status / default price) and commit |
|
| List refunded/revoked (voided) purchases |
|
| Refund a single order, optionally revoking the entitlement |
|
Testers
Tool | Description | Key inputs |
| Read (omit groups) or set the Google Groups of testers for a closed track |
|
Analytics & reports
Tool | Description | Key inputs |
| Distinct users per app version over N days (Reporting API) |
|
| Latest crash rate and ANR rate (Reporting API) |
|
| Install base per app version + monthly net growth, from the statistics GCS reports |
|
| Raw install/uninstall report rows for one month and dimension, from the statistics GCS reports |
|
Meta
Tool | Description | Key inputs |
| List the apps this service account can access (Reporting API) | — |
get_users_by_versionuses the Reporting API's vitals-scopeddistinctUsersmetric — a proxy for the active user base, ideal for the version-adoption split, not an exact install count (the Reporting API has no install-count metric; real install counts live in the statistics GCS reports, read byget_install_statsandget_install_reports).
get_install_reportsreadsstats/installs/installs_{package}_{YYYYMM}_{dimension}.csv(dimension∈overview|country|app_version, defaultoverview) from the reports bucket. These CSVs are UTF-16LE with a BOM; the server decodes and parses them. SetPLAY_REPORTS_BUCKET(Play Console → Download reports → Statistics → Copy Cloud Storage URI; thepubsite_prod_*value) and grant the service account Storage Object Viewer on it.
Related MCP server: google-cloud-console-mcp
Setup
Google Cloud: create a project, enable Google Play Android Developer API and Google Play Developer Reporting API, create a service account, and download its JSON key.
Play Console → Users and permissions: invite the service-account email; grant it the apps and the "View app information / bulk reports" + "Releases" permissions.
Configure the MCP (
~/.claude.json):
{
"mcpServers": {
"play-store": {
"command": "npx",
"args": ["-y", "github:petropentsak/play-store-mcp"],
"env": {
"PLAY_SERVICE_ACCOUNT_KEY_PATH": "/absolute/path/to/service-account-key.json",
"PLAY_DEFAULT_TRACK": "internal"
}
}
}
}PLAY_SERVICE_ACCOUNT_KEY (raw or base64 JSON) is accepted as an alternative to the path.
Build / release
dist/ is committed so npx github: works with no build step. The config is not pinned to a
tag — it tracks the default-branch HEAD, so every commit must be installable (build + commit dist/).
To ship: npm run build → commit (incl. dist/) → push HEAD to the default branch → clear
~/.npm/_npx if a stale tarball is cached → reconnect / cold-start the MCP client.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Manage App Store and Google Play apps: listings, screenshots, builds, releases, reviews, metrics.
Run App Store Connect from your IDE: pricing, listings, screenshots, releases, AI visibility.
Read, search, analyze and draft replies to App Store and Google Play reviews (OAuth sign-in).
Provides tools for searching Google Workspace documentation and much more.
Related MCP Servers
- AlicenseAqualityDmaintenanceManage the full Google Play Store release lifecycle directly — from uploading artifacts to managing testers, rollouts, and Android Vitals.167MIT
- AlicenseBqualityCmaintenanceGives AI assistants hands-on control over Google Play Console and Google Cloud Console using an authorized Google identity. Exposes 95 tools for shipping app builds and release tracks, managing store listings, reviews, in-app products, GCP projects and IAM, Firebase projects and App Distribution, and Cloud Storage or Artifact Registry resources.95MIT
- 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 gradedqualityCmaintenanceEnables autonomous AI agents and developers to programmatically manage Google Play apps via the Play Developer API v3, including uploading Android App Bundles, managing release tracks, updating store listings, and replying to user reviews.3MIT