Google Play Developer API MCP Server

A Model Context Protocol (MCP) server for managing Google Play app deployment and in-app products via the Android Publisher API v3.

Features

App Deployment

• deploy_internal: Upload AAB and deploy to internal testing track
• deploy_track: Upload AAB and deploy to any supported track
• promote_track_release: Promote an existing uploaded release between tracks without re-uploading an AAB

In-App Products

• create_inapp_product: Create or update a single in-app product
• batch_create_inapp_products: Create multiple products at once
• activate_inapp_product: Activate a draft product
• batch_activate_inapp_products: Activate multiple products
• deactivate_inapp_product: Deactivate an active product
• list_inapp_products: List all one-time products
• create_subscription_product: Create or update a subscription product
• list_subscriptions: List all subscription products

App Info

• get_app_info: Get app track and version information

Requirements

• Python 3.10+
• Google Cloud service account with Google Play Developer API access
• App registered in Google Play Console

Installation & Usage

You can use this MCP server directly with npx without installing it manually.

Quick Start (npx)

# Configure your API key
npx google-play-mcp init-key

# For Korean instructions (한국어 안내)
npx google-play-mcp init-key --lang ko

# Start the server
npx google-play-mcp start

Installation (Global)

If you prefer to install it globally (from npm):

npm install -g google-play-mcp

Installation (Local Dev)

To install from the cloned repository:

npm install -g .

Then you can run:

google-play-mcp init-key
google-play-mcp start

Configuration (Antigravity & Claude Desktop)

To use this MCP server, add the following configuration to your MCP client (e.g., claude_desktop_config.json or Antigravity settings):

{
  "mcpServers": {
    "google-play": {
      "command": "google-play-mcp",
      "args": ["start"],
      "env": {
        "GOOGLE_PLAY_KEY_FILE": "/absolute/path/to/your-key.json",
        "GOOGLE_PLAY_PACKAGE_NAME": "com.yourcompany.yourapp"
      }
    }
  }
}

Note: If you haven’t run init-key or don’t have a .env file, you can pass environment variables directly in the configuration as shown above. If you have a .env file in the working directory, the server will load it automatically.

Configuration (Codex)

If your workspace layout is:

/Users//Foreign-Language-Battle/
  └─ google-play-mcp/

you can run this MCP server from the cloned repository directory.

1. Create .env inside google-play-mcp:

cd /Users//Foreign-Language-Battle/google-play-mcp
cp .env.example .env
# edit .env and set:
# GOOGLE_PLAY_KEY_FILE=/absolute/path/to/service-account.json
# GOOGLE_PLAY_PACKAGE_NAME=com.yourcompany.yourapp