list_appsLABSCO SUMMARY
Store operations, including replying to reviews, from where the work is already happening.
Reviews are the part worth automating: reading them and replying are both calls here, so a support routine can answer users in place instead of someone opening the console every morning — and releases and listing edits sit alongside them.
What it is
A server over the Google Play Developer API: the apps in your Play Console, their releases, their store listings, their reviews and their statistics.
What you get
- Every app in your Play Console listed, and full detail on one of them
- Releases listed for an app, and a new release created
- Store listing information updated
- Reviews retrieved, and a reply posted to a user review
- App statistics and metrics pulled for reporting
Requirements
A Google Cloud service account with Play Console API access, and its JSON key file — given either as a path on the command line or through an environment variable. Installed globally from npm or run through npx.
Setup effort
One command plus credentials — npm install -g @blocktopus/mcp-google-play, then supply credentials
USE CASES
01
Answering the reviews that came in overnight
Pull the recent reviews and reply to the ones that need a response, in the same session that drafts them.
02
Shipping a build you have already tested
Check what releases exist for the app, then create the new one.
03
Updating a store listing before a campaign
Update the listing text so it matches the campaign, rather than editing it in the console mid-launch.
04
Putting together a performance report
Pull the statistics and metrics for the app and write the report from them directly.
05
Getting oriented in an account with several apps
List the apps the service account can see, then read the detail on the one you are working on.
8 tools
Listed in project docs. Your client may show a different list.
get_app_infolist_releasescreate_releaseupdate_listingget_reviewsreply_to_reviewget_statisticsBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
- npx on PATH
- A Google Cloud service-account JSON key with Play Console API access
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g @blocktopus/mcp-google-playMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"google-play": {
"command": "npx",
"args": [
"@blocktopus/mcp-google-play",
"--api-key",
"<YOUR_PATH_TO_SERVICE_ACCOUNT_KEY>"
]
}
}
}<YOUR_PATH_TO_SERVICE_ACCOUNT_KEY> is the path of the service-account JSON key you downloaded. The --api-key argument is how this block supplies it.
