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.

📖 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

🚀 Quick Start

Prerequisites

1. Google Cloud Project with the Google Play Developer API enabled
2. Service Account with access to your Play Console
3. Python 3.11+, uvx, or Docker installed

Installation

Using uvx (Recommended)

# Run directly without installation
uvx play-store-mcp

Using pip

pip install play-store-mcp
play-store-mcp

Using 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:latest

From source

git clone https://github.com/lusky3/play-store-mcp.git
cd play-store-mcp
pip install -e .
play-store-mcp

Configuration

Set the path to your service account key:

export GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json

Running 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 8000

The 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.json

Per-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 8000

Read-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=1

Code 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=0

Under 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

Store Listings Tools

Review Tools

Subscription Tools

In-App Products Tools

Testers Management Tools

Orders Tools

Expansion Files Tools

Validation Tools

Batch Operations Tools

📋 Google Cloud Setup

1. Create a Service Account

1. Go to Google Cloud Console
2. Create a new project or select an existing one
3. Enable the Google Play Developer API
4. Go to IAM & Admin > Service Accounts
5. Create a new service account
6. Download the JSON key file

2. Grant Play Console Access

1. Go to Google Play Console
2. Navigate to Users and permissions
3. Click Invite new users
4. Enter the service account email (from the JSON file)
5. 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

🧪 Development

Setup

git clone https://github.com/lusky3/play-store-mcp.git
cd play-store-mcp
uv sync --dev

Running Tests

uv run pytest -v --cov=src/play_store_mcp

Linting

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_CREDENTIALS

Error: “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

• 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.