Play Console Mcp

io.github.wiseappsaiPublished by GitHub account wiseappsaiv0.3.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

A local MCP server that lets an assistant manage Google Play Console: releases, store listings, monetization, reviews, and Android Vitals.

What you can do
Manage releases and track rollouts through the releases toolset, plus advanced and workflow toolsets for multi-step operations. Edit store listings and configure monetization and commerce settings. Read and export user reviews, including via a Cloud Storage report bucket. Inspect Android Vitals and export statistics reports. Look up developer account users and permissions, and device data, when those toolsets are enabled.
When to use it
Useful when you want an assistant to help with day-to-day Google Play Console work — preparing or checking releases, updating listings, reviewing user feedback, or reading vitals and stats — without switching between the console and the chat.
Requirements
Runs locally over stdio, typically via the npm package, so Node.js is needed. Requires Google Play developer access through a service-account key, supplied either inline in PLAY_SERVICE_ACCOUNT_JSON or as a file path in GOOGLE_APPLICATION_CREDENTIALS. The users toolset needs PLAY_DEVELOPER_ACCOUNT_ID; report exports need PLAY_REPORTS_BUCKET and may need PLAY_STORAGE_CREDENTIALS or a local gcloud application-default login. Toolsets are selected with PLAY_TOOLSETS.
Before you install
The service-account key is a powerful Google credential: keep PLAY_SERVICE_ACCOUNT_JSON and any key file private and scope the account narrowly. Many toolsets can change live store data such as releases, listings, and monetization; set PLAY_READ_ONLY to true to expose only read-only actions. Report export buckets often cannot be granted to a service account, so a separate storage credential or gcloud login may be involved. Data is sent to Google APIs.

Installation

In SourceWeft

  1. Open Play Console Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.