Know where a release stands.
Read production and testing track states. See the difference between a release that is in review and one that is published.
Available locallyIndependent project. Entirely open source.
Release status, reviews and app reports, right where you work.
Connect your own account. Keep the context. Get a clearer answer.
Works with MCP clients, including Codex and Claude Code.
Run locally with your own credentials. No project-run Google service.
01 / Useful from the first query
Google Play data becomes useful when the details stay intact. Start with focused, read-only workflows that preserve what the source actually says.
Read production and testing track states. See the difference between a release that is in review and one that is published.
Available locallyRead recent written feedback, open a specific review and continue through the next page without losing context.
Available locallyExplore installs, ratings and store-performance exports. Keep metric names, dates and missing rows visible.
Available locallyIs the new release published?
The release is still in review.
Submitted is not published.
What are people saying?
“The new update makes it much easier to find what I need.”
Read the feedback in context.
Recent reviews are not all-time ratings.
Do we have data for every day?
One day has no reported data.
A missing row does not mean zero installs.
Illustrative responses · Synthetic data · Not a live connection
02 / The boundaries matter
Useful access starts with a clear boundary between the software you run and the Google account you authorize.
Inspect the code, run it yourself and share feedback. The project is AGPL-3.0-only licensed. There is no closed feature tier.
Local tools use your own Google credentials. The project never receives them and does not operate a Google-connected service.
Tools start read-only. Optional local writes require explicit app access and a reviewed preparation. The API inventory records supported methods and the operation Google explicitly does not support. Review each tool's scope and limitations.
03 / Built in the open
PubShip 0.24.0 implements 170 enabled methods from a pinned inventory of 172 definitions. Voided-purchase access is deliberately disabled. Google does not support subscription archiving. Implementation is not a claim of live verification.
Explore the API catalog ↗Read the source data, with its limitations intact.
Prepare, review and apply within your own permissions.
AGPL-3.0-only. No closed feature tier.
04 / Get started locally
Install the published package with uvx pubship and
connect your own service account. Follow the setup guide for
authentication and client configuration. The project does not
receive your credentials.
uvx pubship
Google data requires your own authorization and an explicit app allowlist. No credentials are needed to explore the API catalog.