gplay CLI
A single binary that drives Google Play Console: releases and rollouts, subscriptions, reviews and crashes, every command answering in JSON
- 285 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Ships releases to Google Play production tracks and changes store listings, subscriptions and prices
- Manages Play Console users and permissions and reads financial reports, purchases and refunds
- The service account key grants access to every app it is allowed to touch
Install
- Works in
Manual install
brew install tamtom/tap/gplayRun `brew tap tamtom/tap` first. Standalone binaries exist too: `install.sh` for macOS and Linux, `install.ps1` for Windows.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Ships releases to Google Play production tracks and changes store listings, subscriptions and prices
- Manages Play Console users and permissions and reads financial reports, purchases and refunds
- The service account key grants access to every app it is allowed to touch
This is third-party code. Review the repository files before installing.
What it does
gplay is a Go command-line program that replaces hand work in Google Play Console for an Android developer. It releases apps, creates subscriptions and one-time purchases, verifies purchases server-side and monitors crashes and reviews. It works through documented Google APIs and uses no private endpoints or browser automation. The program has more than 250 commands across nine APIs: Android Publisher, Play Developer Reporting, Checks, two Play Games admin APIs, Managed Google Play, Play Integrity, Android Developer ID Status and Cloud Storage for reports. A release takes one command: `gplay release --package com.example.app --track production --bundle app.aab --rollout 0.1`. There are staged rollouts with pause, promotion between tracks, store listings and screenshots in every locale. Output is always compact JSON and commands never wait for input, so an agent can run them. `gplay install-skills` installs a ready skill pack from a pinned commit after verifying the trees. Initial setup of a public app, the first upload, Play App Signing enrollment and legal declarations are still done by hand in the console.
Who it is for. For Android developers and release engineers who publish to Google Play and want Claude Code, Codex, Cursor or Gemini CLI to handle the routine.
Good fit when
- You need to ship an AAB to an internal track or production with a staged rollout in one command
- Subscriptions with base plans, a trial and regional prices should be created from a JSON file
- You want a weekly summary of crashes, ANRs, installs and reviews from Google Play exports
- Purchases must be verified server-side, and orders and refunds checked from the terminal
- The release goes into CI: GitHub Actions or GitLab, with checks before submission
Not a fit when
- The app does not exist yet: first setup, upload and legal declarations must be done by hand in the console
- You need private Play Console features absent from the official APIs: gplay does not use private endpoints
- The project is iOS: the tool works with Google Play only
- An AAB upload is all you need: Fastlane supply or gradle-play-publisher is enough for one upload
Example request
Release this AAB to internal and show the rollout statusLimitations
Sign-in needs a Google Cloud service account with access in Play Console. Setup: `gplay setup --auto` installs `gcloud`, creates the account and opens the console for the permission step, which is done by hand. Initial publication, Play App Signing and legal declarations stay in the console. Building from source needs Go 1.27.3 or newer. After the first metadata push or release with `gh` installed, the program suggests starring the repository but never does it itself and waits for your consent; set `GPLAY_NO_STAR_PROMPT=1` to silence the hint.
How to disable. Remove the binary with `brew uninstall gplay` or by hand, and delete the skills from the agent's skills folder. Revoke the Google Cloud service account in Play Console if it is no longer needed.
FAQ
How do I install gplay and connect it to Claude Code?
Run `brew tap tamtom/tap` and `brew install tamtom/tap/gplay`, or use the `install.sh` script. Then `gplay install-skills` installs ready skills for agents, and `gplay install-skills --preview` shows the plan without writing.
How do I sign in to Google Play with gplay?
With a service account. The shortest path is `gplay setup --auto`: it creates the account and key, and only granting it rights in Play Console stays manual. If you already have a key, run `gplay auth login --service-account /path/to/key.json`, then `gplay auth doctor`.
How is gplay different from Fastlane supply?
Fastlane supply and gradle-play-publisher upload AABs and manage tracks, rollouts and listings. gplay adds subscriptions with base plans, purchase verification and refunds, vitals, reviews, reports, user management and Managed Google Play private apps, and its output is JSON by default.
What can gplay not do by itself?
Initial public-app setup, the first upload, Play App Signing enrollment and legal declarations must be done in the console. `gplay capabilities` separates official workflows from manual and unsupported ones.
How does an agent find the right command among 250?
`gplay search` ranks commands, examples and flags locally, and `gplay schema` embeds 218 reviewed endpoints with request definitions, needing no network or credentials.
Discussion
No questions or reviews yet.
Related
CLI toolsGoogle Play Developer MCP
google-play-developer-mcp
An MCP server for Google Play Console: releases and tracks, staged rollouts, store listings, reviews and subscriptions from an agent chat
Official set of 30 skills from the Android team: Jetpack Compose, AGP 9 upgrade, R8, Perfetto profiling, Navigation 3, CameraX, Google Play policies
Skills and a CLI that let Claude Code, Codex and OpenCode operate an Android phone: open apps, tap, type and test workflows
Screenshots and preview videos for the App Store and Google Play: the agent walks the app on a simulator, frames the shots and checks store requirements
A headless Android debugger on JDWP: the agent sets breakpoints and reads variables, and every answer comes back as JSON
Artemis
artemis
A Google framework for driving a real Android device or an emulator from natural-language instructions: UI tests and everyday tasks, with an MCP server
README in short
The README starts with what gplay is and the boundary of the official APIs, then gives installation through Homebrew or a script, service-account sign-in, and examples for releases, subscriptions and reviews. It continues with highlights, agent setup and a comparison with Fastlane supply and gradle-play-publisher.