Play Store MCP Server
Connects to the Google Play Developer API to deploy APK/AAB releases, manage tracks and staged rollouts, update store listings and images, manage testers, respond to reviews, handle subscriptions and in-app products, and retrieve order/transaction details.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Play Store MCP Server
An MCP (Model Context Protocol) server that connects to the Google Play Developer API. Deploy apps, manage releases, respond to reviews, and monitor app health โ all through your AI assistant.
About this fork. This is a fork of lusky3/play-store-mcp that adds high-level workflows, several modeled on Jang-myoung-gyoon/google-play-mcp: one-price regional pricing for in-app products and subscriptions, all-or-nothing image replacement, whole-listing sync from a fastlane-style folder, and automatic handling of draft apps and "changes not sent for review" commits. See Workflow Tools below.
๐ Full Documentation
โจ Features
๐ App Deployment โ Deploy APK/AAB files to any track (internal, alpha, beta, production)
โก Batch Operations โ Deploy to multiple tracks simultaneously
๐ Multi-Language Support โ Deploy with release notes in multiple languages
โ Input Validation โ Validate package names, tracks, and text before API calls
๐ Automatic Retries โ Built-in retry logic with exponential backoff for transient failures
๐ Store Listings โ Update app titles, descriptions, and videos for any language
๐ Release Management โ Promote releases between tracks, manage staged rollouts
๐ฅ Tester Management โ Add and manage testers for testing tracks
โญ Review Management โ Fetch and reply to user reviews
๐ณ Subscription Management โ List subscriptions and check purchase status
๐ In-App Products โ List and manage in-app products
๐ฆ Expansion Files โ Manage APK expansion files for large apps
๐งพ Orders โ Retrieve detailed transaction information
๐ณ Docker Support โ Run as a container with health checks
๐ Per-Request Credentials โ Bring-your-own-credentials for multi-tenant deployments
๐ Secure โ Google Cloud service account authentication
๐ฒ One-Price Regional Pricing โ Give one price, get every region priced with Play's own conversion
๐ผ๏ธ Listing Sync โ Push titles, descriptions, icons and screenshots for every language from one folder
Related MCP server: play-console-mcp
๐ Quick Start
Prerequisites
Google Cloud Project with the Google Play Developer API enabled
Service Account with access to your Play Console
Python 3.11+,
uvx, or Docker installed
Installation
Using uvx (Recommended)
# Run directly without installation
uvx play-store-mcpUsing pip
pip install play-store-mcp
play-store-mcpUsing Docker
docker run -e GOOGLE_APPLICATION_CREDENTIALS=/creds/key.json \
-v /path/to/service-account.json:/creds/key.json:ro \
ghcr.io/lusky3/play-store-mcp:latestFrom source
git clone https://github.com/lusky3/play-store-mcp.git
cd play-store-mcp
pip install -e .
play-store-mcpConfiguration
Set the path to your service account key:
export GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.jsonRunning with HTTP Transport
For remote access or public deployments, run the server with streamable-http transport:
play-store-mcp --transport streamable-http --host 0.0.0.0 --port 8000The server exposes a /health endpoint for monitoring.
Per-Request Credentials (Recommended for Public Instances)
For public deployments where users bring their own credentials, configure your MCP client to pass credentials in headers:
{
"mcpServers": {
"play-store": {
"url": "https://your-server.com/mcp",
"transport": "http",
"headers": {
"X-Google-Credentials-Base64": "YOUR_BASE64_ENCODED_CREDENTIALS"
}
}
}
}To get your base64-encoded credentials:
base64 -w 0 < service-account.jsonPer-request credentials are isolated โ each request uses only the credentials provided in its headers. No credentials are stored server-side or shared between requests.
Server-Side Credentials (For Private/Trusted Deployments)
For private deployments, set credentials via environment variable at server startup:
export GOOGLE_PLAY_STORE_CREDENTIALS='{"type":"service_account",...}'
# or
export GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json
play-store-mcp --transport streamable-http --host 0.0.0.0 --port 8000Read-Only Mode
To point the server at a live Play Console without any risk of mutating it, run in read-only mode. All write tools (deploy, promote, halt, rollout, reply to reviews, listing/tester updates) return an error instead of calling the API; read tools are unaffected.
play-store-mcp --read-only
# or
export PLAY_STORE_MCP_READ_ONLY=1Code Mode (Experimental, enabled by default)
By default the tools are served as three meta-tools (search/get_schema/
execute) instead of the full tool list, cutting per-request tool-list token
overhead. The sandbox execute runs in is a base dependency, so this works
out of the box โ no extra install needed.
To opt out and use the classic tool list instead (CODE_MODE is env-only โ
there is no CLI flag):
export CODE_MODE=0Under code mode one execute call can invoke up to 50 tool calls (including mutations) behind a single approval. Read-only enforcement still applies inside the sandbox, so pair it with --read-only / PLAY_STORE_MCP_READ_ONLY=1 unless you need writes.
๐ง MCP Client Configuration
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"play-store": {
"command": "uvx",
"args": ["play-store-mcp"],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "/path/to/service-account.json"
}
}
}
}Kiro
Add to .kiro/settings/mcp.json:
{
"mcpServers": {
"play-store": {
"command": "uvx",
"args": ["play-store-mcp"],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "/path/to/service-account.json"
}
}
}
}Gemini CLI / Other MCP Clients
{
"mcpServers": {
"play-store": {
"command": "uvx",
"args": ["play-store-mcp"],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "/path/to/service-account.json"
}
}
}
}๐ ๏ธ Available Tools
Publishing Tools
Tool | Description |
| Deploy an APK/AAB to a track with optional staged rollout and single-language release notes |
| Deploy an APK/AAB with multi-language release notes |
| Promote a release from one track to another |
| Get release status for all tracks |
| Halt a staged rollout |
| Update rollout percentage for a staged release |
| Get app metadata (title, description, etc.) |
Workflow Tools (this fork)
Tool | Description |
| Convert one price (e.g. |
| Create a one-time in-app product priced in every region from one price, and activate it |
| Create many priced one-time products; each distinct price is converted once |
| Create an auto-renewing subscription + base plan priced in every region, and activate it. Optional |
| Add a free trial (e.g. 1 month free, then the normal price) to an existing subscription base plan |
| Upload several screenshots/icon/feature graphic for one language in a single all-or-nothing commit |
| Sync listing text and images for every language from a fastlane-style folder (supports |
deploy_app and promote_release also gained:
Draft-app handling โ an app that has never been published only accepts
draftreleases. The release is retried as a draft automatically, so the first upload of a new app works.release_statusondeploy_appโ pass"draft"to stage a release without rolling it out. A status that contradictsrollout_percentage(e.g.completedwith a 5% rollout) is rejected.Review fallback โ for deploys, promotions, image replacement and listing sync, when Play refuses to send changes for review automatically the commit is retried with
changesNotSentForReview=trueand the result tells you to send them for review from the Play Console. Other tools still report the error.
Listing folder layout
sync_listing_from_directory reads the same layout as fastlane supply, so
existing fastlane/metadata/android folders work unchanged:
metadata/
โโโ en-US/
โ โโโ title.txt # max 30 chars
โ โโโ short_description.txt # max 80 chars
โ โโโ full_description.txt # max 4000 chars
โ โโโ video.txt # optional YouTube URL
โ โโโ images/
โ โโโ icon.png # 512x512
โ โโโ featureGraphic.png # 1024x500
โ โโโ phoneScreenshots/ # 1.png, 2.png, ... (up to 8, natural sort order)
โ โโโ sevenInchScreenshots/
โ โโโ tenInchScreenshots/
โโโ de-DE/
โโโ ...Only what exists in the folder is changed. Everything is validated first and
applied in one commit; use dry_run=true to preview.
Example prompts
"Create a consumable
coins_500called '500 Coins' for $1.99 in com.example.app.""Create a monthly subscription
premiumat $4.99 with benefits 'No ads' and 'Cloud sync'.""Create a monthly subscription
premiumat $4.99 with the first month free for new customers.""Add a 7-day free trial to the
monthlyplan ofpremium.""Dry-run a listing sync from ./fastlane/metadata/android, then apply it."
"Replace the en-US phone screenshots with the PNGs in ./shots."
Store Listings Tools
Tool | Description |
| Get store listing for a specific language |
| Update store listing (title, descriptions, video) |
| List all store listings for all languages |
Review Tools
Tool | Description |
| Fetch recent reviews with optional filters |
| Reply to a user review |
Subscription Tools
Tool | Description |
| List subscription products for an app |
| Check subscription purchase status |
| List voided purchases |
In-App Products Tools
Tool | Description |
| List all in-app products for an app |
| Get details of a specific in-app product |
Testers Management Tools
Tool | Description |
| Get testers for a specific testing track |
| Update testers for a testing track |
Orders Tools
Tool | Description |
| Get detailed order/transaction information |
Expansion Files Tools
Tool | Description |
| Get APK expansion file information |
Validation Tools
Tool | Description |
| Validate package name format |
| Validate track name |
| Validate store listing text lengths |
Batch Operations Tools
Tool | Description |
| Deploy to multiple tracks simultaneously |
๐ Google Cloud Setup
1. Create a Service Account
Go to Google Cloud Console
Create a new project or select an existing one
Enable the Google Play Developer API
Go to IAM & Admin > Service Accounts
Create a new service account
Download the JSON key file
2. Grant Play Console Access
Go to Google Play Console
Navigate to Users and permissions
Click Invite new users
Enter the service account email (from the JSON file)
Grant the following permissions:
Release apps to testing tracks (for internal/alpha/beta)
Release apps to production (for production releases)
Reply to reviews (for review management)
View app information and download bulk reports (for app details and orders)
๐ Environment Variables
Variable | Description | Required |
| Path to service account JSON key | Yes (or use per-request credentials) |
| Inline JSON credentials string | Alternative to file path |
| Log level (DEBUG, INFO, WARNING, ERROR) | No (default: INFO) |
| Disable DNS rebinding protection (for cloud/reverse-proxy deployments) | No |
| Require | No |
| Disable all write operations (deploy, promote, rollout, reply, listing/tester updates) | No (default: off) |
| Directory that APK/AAB downloads are confined to (path-traversal / arbitrary-write protection). Downloads are always confined; defaults to the working directory when unset | No (defaults to cwd); recommended for network/hosted deployments โ the server warns if unset |
| Set to | No (default: on) |
| What a commit does when other changes are already in review: | No (default: Google's default, which cancels the in-progress review) |
๐งช Development
Setup
git clone https://github.com/lusky3/play-store-mcp.git
cd play-store-mcp
uv sync --devRunning Tests
uv run pytest -v --cov=src/play_store_mcpLinting
ruff check src/ tests/
ruff format src/ tests/Type Checking
mypy src/๐ Troubleshooting
Error: "Service account key not found"
Ensure GOOGLE_APPLICATION_CREDENTIALS points to a valid JSON file:
ls -la $GOOGLE_APPLICATION_CREDENTIALSError: "The caller does not have permission"
Verify the service account has been granted access in Play Console with the required permissions.
Error: "Package name not found"
Ensure the app exists in Play Console and the service account has access to it.
๐ License
MIT License โ see LICENSE for details.
๐ Acknowledgments
Forked from lusky3/play-store-mcp (MIT)
Workflow ideas (regional price conversion, batch image upload, draft-app commits) from Jang-myoung-gyoon/google-play-mcp, re-implemented here
Inspired by antoniolg/play-store-mcp (Kotlin)
Built with the MCP Python SDK
Uses the Google Play Developer API
๐ค AI Usage Disclaimer
Portions of this codebase were generated with the assistance of Large Language Models (LLMs). All AI-generated code has been reviewed and tested to ensure quality and correctness.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
This server cannot be deployed
Maintenance
Related MCP Connectors
Ship a new Android app from chat. AI runs Google Play Console listings, screenshots, releases, uploโฆ
App Store Connect operator for AI agents: icons, TestFlight builds, listings, IAP, rejection fixes.
AI-agent operations for App Store Connect and Google Play, with approval before live publishing.
AI-agent operations for App Store Connect and Google Play, with approval before live publishing.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to automate Android release workflows via the Google Play Android Publisher API, including deploying builds, managing listings, and replying to reviews.40MIT
- AlicenseAqualityCmaintenanceEnables AI agents to manage Google Play Console reviews and Android app releases, including replying to reviews, promoting releases, managing staged rollouts, and checking crash/ANR vitals.34197 npm2MIT
- AlicenseBqualityCmaintenanceGives AI assistants hands-on control over Google Play Console and Google Cloud Console using an authorized Google identity. Exposes 95 tools for shipping app builds and release tracks, managing store listings, reviews, in-app products, GCP projects and IAM, Firebase projects and App Distribution, and Cloud Storage or Artifact Registry resources.95MIT
- AlicenseNot gradedqualityCmaintenanceEnables autonomous AI agents and developers to programmatically manage Google Play apps via the Play Developer API v3, including uploading Android App Bundles, managing release tracks, updating store listings, and replying to user reviews.3MIT