Googleplayconsolemcp MCP Server

A Python [Model Context Protocol](https://modelcontextprotocol.io/) server that lets AI assistants (Claude, etc.) manage the full Google Play Store

Local serverstdioPython

What is the Googleplayconsolemcp MCP server?

Connect Googleplayconsolemcp to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Python Model Context Protocol server that lets AI assistants (Claude, etc.) manage the full Google Play Store release lifecycle directly — from uploading artifacts to managing testers, rollouts, and. The googleplayconsolemcp mcp server is what makes that connection.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • list_tracks — Returns all tracks with their releases, rollout percentages, statuses, and country availability
  • get_track_info — Returns a human-readable summary plus releases with status, rollout %, version codes, and release notes
  • create_release — Creates or replaces a release on the given track. Use status="inProgress" with a rollout_percentage for a staged production rollout, or
  • update_release — Update an existing release. Common use cases: - Increase rollout: update_release(pkg, rollout_percentage=50) - Complete rollout:
  • promote_release — Copies a release from one track to another. Release notes and name are inherited from the source release unless explicitly overridden
  • list_artifacts — Returns all APKs and AABs sorted by version code (newest first) with SHA hashes
  • upload_artifact — Uploads an APK or AAB (auto-detected from extension) and creates a release on the given track in a single atomic operation. Returns the assigned
  • upload_to_internal_sharing — Uploads a build to Internal App Sharing (bypasses track assignment) and returns a shareable downloadUrl. Testers must have Internal App Sharing
  • get_testers — Returns the list of tester email addresses and Google Groups for the track
  • update_testers — The update_testers tool exposed by this server
  • get_crash_rate — Returns daily crashRate, userPerceivedCrashRate, and distinctUsers per version code. Google's bad behavior threshold for user-perceived crash rate is
  • get_anr_rate — Returns daily anrRate, userPerceivedAnrRate, and distinctUsers per version code. Google's bad behavior threshold for user-perceived ANR rate is

Installation

Installation goes through your MCP client rather than a global install: point it at google-play-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Credentials and setup notes

Configuration is passed through the environment: GOOGLE_APPLICATION_CREDENTIALS. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  1. uvinstall guide 2. A Google Cloud service account with the JSON key downloaded. 3. The service account added to Google Play Console with the correct permissions (see below). 4. These APIs enabled in your Google Cloud project: - [Google Play Android Developer

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Googleplayconsolemcp's toolset — list_tracks, get_track_info, create_release and 11 more — is a fair guide to whether it matches your workflow. It is maintained by agimaulana; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Googleplayconsolemcp's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Googleplayconsolemcp.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
list_tracksReturns all tracks with their releases, rollout percentages, statuses, and country availability.
get_track_infoReturns a human-readable summary plus releases with status, rollout %, version codes, and release notes.
create_releaseCreates or replaces a release on the given track. Use status="inProgress" with a rollout_percentage for a staged production rollout, or status="completed" to release to all users immediately.
update_releaseUpdate an existing release. Common use cases: - **Increase rollout:** update_release(pkg, rollout_percentage=50) - **Complete rollout:** update_release(pkg, rollout_percentage=100) - **Halt rollout:** update_release(pkg,
promote_releaseCopies a release from one track to another. Release notes and name are inherited from the source release unless explicitly overridden.
list_artifactsReturns all APKs and AABs sorted by version code (newest first) with SHA hashes.
upload_artifactUploads an APK or AAB (auto-detected from extension) and creates a release on the given track in a single atomic operation. Returns the assigned version code.
upload_to_internal_sharingUploads a build to Internal App Sharing (bypasses track assignment) and returns a shareable downloadUrl. Testers must have Internal App Sharing enabled in their Play Store settings. Ideal for quick one-off testing withou
get_testersReturns the list of tester email addresses and Google Groups for the track.
update_testersThe update_testers tool exposed by this server.
get_crash_rateReturns daily crashRate, userPerceivedCrashRate, and distinctUsers per version code. Google's bad behavior threshold for user-perceived crash rate is **~1.09%**.
get_anr_rateReturns daily anrRate, userPerceivedAnrRate, and distinctUsers per version code. Google's bad behavior threshold for user-perceived ANR rate is **~0.47%**.
get_vitals_summaryReturns a combined crash + ANR summary aggregated per version code, with averages over the period and exceedsCrashThreshold / exceedsAnrThreshold flags. The latest version is highlighted as latestVersionSummary.
get_wakelock_rateReturns daily stuckBackgroundWakelockRate and distinctUsers per version code. Relevant for 2026 Google Play battery health enforcement — apps with an excessive proportion of sessions holding a partial wake lock for more

How to install the Googleplayconsolemcp MCP server

{
  "mcpServers": {
    "google-play": {
      "command": "uvx",
      "args": ["google-play-mcp"],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "/absolute/path/to/service-account.json"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  1. uvinstall guide 2. A Google Cloud service account with the JSON key downloaded. 3. The service account added to Google Play Console with the correct permissions (see below). 4. These APIs enabled in your Google Cloud project: - [Google Play Android Developer
VariableDescriptionRequired
GOOGLE_APPLICATION_CREDENTIALSConfiguration value read at startup.Optional

Example prompts to try

  • Use Googleplayconsolemcp to list tracks.
  • Use Googleplayconsolemcp to get track info.
  • Use Googleplayconsolemcp to create release.

Frequently asked questions

It connects Googleplayconsolemcp to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (list_tracks, get_track_info, create_release, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Googleplayconsolemcp directly.