Play-console-mcp Server

Manage Google Play Console: releases, listings, monetization, reviews, and Android Vitals.

Local serverstdio

What is the Play-console-mcp Server?

Play-console-mcp is an MCP integration. Manage Google Play Console: releases, listings, monetization, reviews, and Android Vitals.

Packages and local setup

The published npm package is @wiseappsai/play-console-mcp, version 0.3.0. Its declared MCP transport is stdio.

The package declares PLAY_SERVICE_ACCOUNT_JSON: Inline Google service-account key JSON (recommended). Alternatively set GOOGLE_APPLICATION_CREDENTIALS to a key file path.; GOOGLE_APPLICATION_CREDENTIALS: Path to a Google service-account key file (alternative to PLAY_SERVICE_ACCOUNT_JSON).; PLAY_DEVELOPER_ACCOUNT_ID: Numeric Play developer account id. Required only for the users (permissions) toolset.; PLAY_REPORTS_BUCKET: Cloud Storage report-export bucket for the play_reviews_export and play_stats_export tools — the value from Play Console > Download reports > 'Copy Cloud Storage URI' (pubsite_prod_rev_...). Not the developer account id.; PLAY_STORAGE_CREDENTIALS: Path to a credentials JSON used only for the storage/reviews-export client. The report buckets usually can't be granted to a service account; locally gcloud auth application-default login is auto-detected instead.; PLAY_TOOLSETS: Comma-separated toolsets to enable, or 'all'. Toolsets: releases, store_listing, monetization, commerce, reviews, users, devices, advanced, vitals, reports, workflows.; PLAY_READ_ONLY: Set to 'true' to expose only read-only actions..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.3.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
PLAY_SERVICE_ACCOUNT_JSONInline Google service-account key JSON (recommended). Alternatively set GOOGLE_APPLICATION_CREDENTIALS to a key file path.Optional
GOOGLE_APPLICATION_CREDENTIALSPath to a Google service-account key file (alternative to PLAY_SERVICE_ACCOUNT_JSON).Optional
PLAY_DEVELOPER_ACCOUNT_IDNumeric Play developer account id. Required only for the users (permissions) toolset.Optional
PLAY_REPORTS_BUCKETCloud Storage report-export bucket for the play_reviews_export and play_stats_export tools — the value from Play Console > Download reports > 'Copy Cloud Storage URI' (pubsite_prod_rev_...). Not the developer account id.Optional
PLAY_STORAGE_CREDENTIALSPath to a credentials JSON used only for the storage/reviews-export client. The report buckets usually can't be granted to a service account; locally gcloud auth application-default login is auto-detected instead.Optional
PLAY_TOOLSETSComma-separated toolsets to enable, or 'all'. Toolsets: releases, store_listing, monetization, commerce, reviews, users, devices, advanced, vitals, reports, workflows.Optional
PLAY_READ_ONLYSet to 'true' to expose only read-only actions.Optional