Play Console Mcp
Google Play Console listings, releases, rollouts, reviews and vitals, with staged edits and guards
An MCP server for the Google Play Console: store listings, icon, feature graphic, screenshots, app bundle releases, staged rollouts, testers, user reviews, Android vitals (crash and ANR rates and issues), and a read-only view of in-app products and subscriptions. It runs over stdio and works with Claude Code or any other MCP client.
It is built to be safe to hand to an AI agent:
- Changes are staged, never published implicitly. Write tools put their changes in a Play edit and return its
editId. Nothing goes live untilcommit_editis called, so the agent can show youedit_summaryfirst and wait for your approval. - A staged edit is never discarded by accident. Google Play keeps one open edit per app, and opening another deletes it. While an edit the server staged is open, a read or write without
edit_idis refused with that edit's id instead.commit_editchecks production tracks against a snapshot taken when the edit was created, so it never opens a second edit. - Production is locked. Staging or committing a change to the
productiontrack, or to a form-factor production track such aswear:production, is refused unless the server runs withPLAY_ALLOW_PRODUCTION=1. - Package allowlist. The server only touches the packages in
PLAY_PACKAGE_NAMES. - Files stay inside the asset root. Graphics, bundles and listing files must resolve to files under
PLAY_ASSET_ROOT(symlinks are followed before the check), so a prompt cannot make it read or upload an arbitrary file from your machine. The server refuses an asset root that is your home directory or above it. Images are checked against Play's size rules before anything is sent. - Reviews and crash reports are marked untrusted. Review results and error issues carry a note telling the agent that their text is content, not instructions.
reply_to_reviewpublishes immediately, so keep it behind a permission prompt.
Requirements
- uv (installs Python 3.11+ and the dependencies on first run)
- A Google Cloud service account with access to your app in Play Console
Service account setup
- In Google Cloud Console, pick or create a project, open APIs & Services → Library, and enable the Google Play Android Developer API. For
get_vitalsandlist_error_issues, also enable the Google Play Developer Reporting API. - Under IAM & Admin → Service Accounts, create a service account (no Cloud roles needed). In its Keys tab, choose Add key → JSON and download the key.
- Store the key outside any repository:
mkdir -p ~/.config/play-console-mcp && mv ~/Downloads/<key>.json ~/.config/play-console-mcp/service-account.json && chmod 600 ~/.config/play-console-mcp/service-account.json - In Play Console → Users and permissions → Invite new users, add the service account's email. Under App permissions, add only your app and grant what you need:
- View app information (read-only), which also covers Android vitals
- Manage store presence (listings and graphics)
- Reply to reviews
- Release apps to testing tracks (releases, rollouts and testers on testing tracks)
- For
list_one_time_productsandlist_subscriptions, a permission that can view in-app products, such as View financial data; the server never changes products - Leave out Release to production unless you really want the agent near production.
New permissions can take a few hours to apply; until then the API answers 403 The caller does not have permission.
The Play Developer API cannot create apps. Create the app and upload its first bundle in Play Console by hand.
Configuration
From the project's README.