Skip to content
Back to search

play-store-mcp

An MCP server that connects to Play Store Console and release new App versions from an MCP Client

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/antoniolg--play-store-mcp/badge.svg)](/listings/antoniolg--play-store-mcp)

HTML

<a href="/listings/antoniolg--play-store-mcp"><img src="/api/listings/antoniolg--play-store-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. Google Cloud and Play Console Setup

Step 1: Create a Google Cloud Console project

1. Go to [Google Cloud Console](https://console.cloud.google.com/) 2. Create a new project or select an existing one 3. Enable the Google Play Android Developer API: - Go to "APIs & Services" → "Library" - Search for "Google Play Android Developer API" - Click "Enable"

Step 2: Create a service account

1. In Google Cloud Console, go to "IAM & Admin" → "Service Accounts" 2. Click "Create Service Account" 3. Fill in the details: - **Name**: `play-store-mcp` - **Description**: `Service account for Play Store MCP operations` 4. Click "Create and Continue" 5. In "Grant this service account access to project", you don't need to assign specific roles 6. Click "Done"

Step 3: Generate the service account key

1. In the service accounts list, find the one you just created 2. Click on the service account email 3. Go to the "Keys" tab 4. Click "Add Key" → "Create new key" 5. Select "JSON" as the key type 6. Click "Create" 7. A JSON file will download - this is your `service-account-key.json`

Step 4: Configure permissions in Google Play Console

1. Go to [Google Play Console](https://play.google.com/console) 2. Select your developer account 3. Go to "Users and Permssions" 4. Click "Invite new users" 5. Add the email of the service account 6. Click "Invite User" 8. Configure the necessary permissions: - **App permissions**: Select the apps it can manage - **Account permissions**: Grant "View app information" and the permissions aunder "Versions"

More permissions may be required when new features are released.

2. MCP Client Configuration

Add the following configuration to your MCP configuration file:

{
  "mcpServers": {
    "play-store-mcp": {
      "command": "java",
      "args": [
        "-jar",
        "/path/to/play-store-mcp-all.jar"
      ],
      "env": {
        "PLAY_STORE_SERVICE_ACCOUNT_KEY_PATH": "/path/to/service-account-key.json",
        "PLAY_STORE_DEFAULT_TRACK": "internal"
      }
    }
  }
}

Environment Variables

- `PLAY_STORE_SERVICE_ACCOUNT_KEY_PATH`: Path to the service account JSON file (required) - `PLAY_STORE_DEFAULT_TRACK`: Default track for deployments (optional, default: "internal")

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 177 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. > [!WARNING]
  2. > **Archivado · Archived.** Este servidor MCP ya no se mantiene y sus dependencias no se actualizan: úsalo bajo tu responsabilidad. This MCP server is no longer maintained and its dependencies are not updated: use it at your own risk.
  3. > Lo que enseño ahora · What I teach now: [devexpert.io](https://devexpert.io)
  4. # Play Store MCP Server
  5. An MCP (Model Context Protocol) server that enables interaction with Google Play Console to deploy and manage Android applications.
  6. ## ⚠️ Development Status
  7. **Although it's currently functional, this MCP server is under development.** Please use with caution and thoroughly test in non-production environments first.
  8. If you encounter any issues or have feature requests, please [open an issue](https://github.com/devexpert-io/play-store-mcp/issues) on GitHub. Your feedback is valuable for improving this project.
  9. ## What is this?
  10. This MCP server provides tools to:
  11. - Deploy new versions of Android applications
  12. - Promote releases between tracks (internal → alpha → beta → production)
  13. - Query the status of existing releases
  14. ## Available Tools
  15. ### 1. `deploy_app`
  16. Deploys a new version of an application to the Play Store.
  17. **Parameters:**
  18. - `packageName` (string): App package name (e.g., com.example.myapp)
  19. - `track` (string): Release track (internal, alpha, beta, production)
  20. - `apkPath` (string): Path to APK or AAB file
  21. - `versionCode` (integer): Version code (must be higher than current)
  22. - `releaseNotes` (string, optional): Release notes
  23. - `rolloutPercentage` (number, optional): Rollout percentage (0.0 to 1.0, default: 1.0 for full rollout)
  24. ### 2. `promote_release`
  25. Promotes an existing version from one track to another.
  26. **Parameters:**
  27. - `packageName` (string): App package name
  28. - `fromTrack` (string): Source track (internal, alpha, beta)
  29. - `toTrack` (string): Target track (alpha, beta, production)
  30. - `versionCode` (integer): Version code to promote
  31. ### 3. `get_releases`
  32. Gets the current status of app releases and deployments for a specific package.
  33. **Parameters:**
  34. - `packageName` (string): App package name (e.g., com.example.myapp)
  35. ## Setup
  36. ### 1. Google Cloud and Play Console Setup
  37. #### Step 1: Create a Google Cloud Console project
  38. 1. Go to [Google Cloud Console](https://console.cloud.google.com/)
  39. 2. Create a new project or select an existing one
  40. 3. Enable the Google Play Android Developer API:
  41. - Go to "APIs & Services" → "Library"
  42. - Search for "Google Play Android Developer API"
  43. - Click "Enable"
  44. #### Step 2: Create a service account
  45. 1. In Google Cloud Console, go to "IAM & Admin" → "Service Accounts"
  46. 2. Click "Create Service Account"
  47. 3. Fill in the details:
  48. - **Name**: `play-store-mcp`
  49. - **Description**: `Service account for Play Store MCP operations`
  50. 4. Click "Create and Continue"
  51. 5. In "Grant this service account access to project", you don't need to assign specific roles
  52. 6. Click "Done"
  53. #### Step 3: Generate the service account key
  54. 1. In the service accounts list, find the one you just created
  55. 2. Click on the service account email
  56. 3. Go to the "Keys" tab
  57. 4. Click "Add Key" → "Create new key"
  58. 5. Select "JSON" as the key type
  59. 6. Click "Create"
  60. 7. A JSON file will download - this is your `service-account-key.json`
  61. #### Step 4: Configure permissions in Google Play Console
  62. 1. Go to [Google Play Console](https://play.google.com/console)
  63. 2. Select your developer account
  64. 3. Go to "Users and Permssions"
  65. 4. Click "Invite new users"
  66. 5. Add the email of the service account
  67. 6. Click "Invite User"
  68. 8. Configure the necessary permissions:
  69. - **App permissions**: Select the apps it can manage
  70. - **Account permissions**: Grant "View app information" and the permissions aunder "Versions"
  71. More permissions may be required when new features are released.
  72. ### 2. MCP Client Configuration
  73. Add the following configuration to your MCP configuration file:
  74. ```json
  75. {
  76. "mcpServers": {
  77. "play-store-mcp": {
  78. "command": "java",
  79. "args": [
  80. "-jar",
  81. "/path/to/play-store-mcp-all.jar"
  82. ],
  83. "env": {
  84. "PLAY_STORE_SERVICE_ACCOUNT_KEY_PATH": "/path/to/service-account-key.json",
  85. "PLAY_STORE_DEFAULT_TRACK": "internal"
  86. }
  87. }
  88. }
  89. }
  90. ```
  91. ### Environment Variables
  92. - `PLAY_STORE_SERVICE_ACCOUNT_KEY_PATH`: Path to the service account JSON file (required)
  93. - `PLAY_STORE_DEFAULT_TRACK`: Default track for deployments (optional, default: "internal")
  94. ## Building
  95. To build the project:
  96. ```bash
  97. ./gradlew clean build -x test
  98. ```
  99. This will generate the JAR file at `build/libs/play-store-mcp-all.jar`.
  100. You can also download the `jar` from the latest [release](https://github.com/devexpert-io/play-store-mcp/releases).
  101. ## Usage
  102. Once configured, you can use the tools from any compatible MCP client.
  103. Some samples of prompts are:
  104. If you want to get the current releases of the App:
  105. > Let me know what versions of com.example.myapp are released in the Play Store.
  106. To release a new version of the App to the alpha channel, you can say:
  107. > Upgrade the version of the App, build the AAB, and upload it to the alpha channel.
  108. To deploy with a gradual rollout (e.g., 50% of users):
  109. > Update the App version, compile the AAB, and publish it to the Play Store on the alpha channel with a 50% rollout, using the @release_notes.txt.
  110. ## Requirements
  111. - Java 8 or higher
  112. - Google Play Console developer account
  113. - Google Cloud project with Play Developer API enabled
  114. - Applications already published in Play Console (at least as drafts)
  115. ## Limitations
  116. - Only supports APK and AAB files
  117. - Requires applications to be already configured in Play Console
  118. - Service account permissions must be configured manually in Play Console
  119. ## Troubleshooting
  120. ### Error: "Service account key not found"
  121. Verify that the path in `PLAY_STORE_SERVICE_ACCOUNT_KEY_PATH` is correct and the file exists.
  122. ### Error: "The caller does not have permission"
  123. Ensure the service account is properly configured in Google Play Console with the necessary permissions.
  124. ### Error: "Package name not found"
  125. Verify that the package name is correct and the application is configured in Play Console.
  126. ## License
  127. This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.