Google Play Server

Node.js TypeScript MCP License: MIT

An MCP (Model Context Protocol) server that connects AI assistants to the Google Play Developer API v3 — enabling automated app publishing, subscription management, review monitoring, and tester management.

✨ Features

• 📦 Publishing — List release tracks, upload AAB bundles, get store listings
• 💰 Subscriptions & IAP — Query subscription products, base plans, pricing, and in-app products
• ⭐ Reviews — List user reviews with ratings/device info, reply to reviews directly
• 👥 Testers — Manage tester groups per release track
• 🔒 Secure — Service account auth (server-to-server, no OAuth flow needed)
• 🤖 LLM-Optimized — Markdown responses, clear error messages, proper isError flags

📋 Tools Reference

Publishing

Subscriptions & IAP

Reviews

Testers

🚀 Quick Start

1. Prerequisites

• Node.js ≥ 18
• A Google Cloud project with the Google Play Android Developer API enabled
• A Service Account with permissions granted in Play Console

2. Google Cloud Setup

3. Installation

# Clone the repository
git clone https://github.com/quan7794/google-play-mcp-server.git
cd google-play-mcp-server

# Install dependencies
npm install

# Build
npm run build

Or install globally via npm (once published):

npm install -g google-play-mcp-server

4. Configuration

The server requires two environment variables:

[!NOTE] The package_name parameter can be overridden per tool call, so you can manage multiple apps with a single server instance.

5. Add to Your MCP Client

{
  "mcpServers": {
    "google-play": {
      "command": "node",
      "args": ["/absolute/path/to/google-play-mcp-server/dist/index.js"],
      "env": {
        "GOOGLE_SERVICE_ACCOUNT_KEY": "/path/to/service-account-key.json",
        "GOOGLE_PLAY_PACKAGE_NAME": "com.example.myapp"
      }
    }
  }
}

{
  "servers": {
    "google-play": {
      "command": "node",
      "args": ["/absolute/path/to/google-play-mcp-server/dist/index.js"],
      "env": {
        "GOOGLE_SERVICE_ACCOUNT_KEY": "/path/to/service-account-key.json",
        "GOOGLE_PLAY_PACKAGE_NAME": "com.example.myapp"
      }
    }
  }
}

{
  "mcpServers": {
    "google-play": {
      "command": "node",
      "args": ["/absolute/path/to/google-play-mcp-server/dist/index.js"],
      "env": {
        "GOOGLE_SERVICE_ACCOUNT_KEY": "/path/to/service-account-key.json",
        "GOOGLE_PLAY_PACKAGE_NAME": "com.example.myapp"
      }
    }
  }
}

{
  "mcpServers": {
    "google-play": {
      "command": "node",
      "args": ["/absolute/path/to/google-play-mcp-server/dist/index.js"],
      "env": {
        "GOOGLE_SERVICE_ACCOUNT_KEY": "/path/to/service-account-key.json",
        "GOOGLE_PLAY_PACKAGE_NAME": "com.example.myapp"
      }
    }
  }
}

💬 Usage Examples

Once connected, you can ask your AI assistant things like:

"Show me all release tracks and their current versions"
"Upload the bundle at ~/build/app-release.aab to internal testing"
"What subscriptions are configured for my app?"
"Show me recent 1-star reviews"
"Reply to review abc123 thanking them for the feedback"
"What testers are on the beta track?"

🔧 Development

npm run dev    # Watch mode with hot reload (tsx)
npm run build  # Compile TypeScript to dist/
npm run clean  # Remove dist/
npm start      # Run compiled server

Project Structure

src/
├── index.ts              # Entry point — registers tools, connects stdio
├── auth.ts               # Google Auth (service account, cached client)
├── constants.ts          # Shared constants (CHARACTER_LIMIT, tracks)
├── schemas.ts            # Shared Zod schemas (PackageNameSchema)
├── tools/
│   ├── publishing.ts     # list_tracks, upload_bundle, get_app_details
│   ├── subscriptions.ts  # list/get subscriptions, list IAP
│   ├── reviews.ts        # list/reply reviews
│   └── testers.ts        # get/update testers
└── utils/
    ├── errors.ts         # GaxiosError → LLM-friendly error messages
    └── formatter.ts      # Truncation, text content helpers

❓ Troubleshooting

🔒 Security

• Service account keys should never be committed to version control
• Use minimal permissions — only grant what you need
• The server runs locally via stdio — no network ports are opened
• All API calls use OAuth 2.0 with the androidpublisher scope

🤝 Contributing

Contributions are welcome! Please:

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-tool)
3. Make your changes, ensuring npm run build passes
4. Submit a Pull Request

Adding a New Tool

1. Add the tool registration in the appropriate file under src/tools/
2. Use withErrorHandling() wrapper for consistent error handling
3. Use textContent() and truncateIfNeeded() for responses
4. Add proper Zod schemas with .describe() for all parameters
5. Set correct annotations (readOnlyHint, destructiveHint, etc.)
6. Update this README

📄 License

MIT © Waclabs

Built with ❤️ using Model Context Protocol and the Google Play Developer API v3.