playmcp GitHub

Independent project. Entirely open source.

Google Play.
In your AI workflow.

Release status, reviews and app reports, right where you work.
Connect your own account. Keep the context. Get a clearer answer.

Get started locally Explore the source

Works with MCP clients, including Codex and Claude Code.
Public hosted access is in development.

YOUR WORKSPACEAI clientCodex · Claude Code · MCP
Play MCPLOCAL · STDIO
YOUR ACCOUNTGoogle PlayYour apps. Your permissions.
A closer look

01 / Useful from the first query

Less switching tabs.
More understanding.

Google Play data becomes useful when the details stay intact. Start with focused, read-only workflows that preserve what the source actually says.

01

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 locally
02

Bring reviews into the conversation.

Read recent written feedback, open a specific review and continue through the next page without losing context.

Available locally
03

Read the report behind the number.

Explore installs, ratings and store-performance exports. Keep metric names, dates and missing rows visible.

Available locally
A SMALL LOOK INSIDE

Is the new release published?

PRODUCTION / 2.4.0In review
releaseLifecycleState
IN_REVIEW
Track
production
Source
Android Publisher API

The release is still in review.
Submitted is not published.

Illustrative responses · Synthetic data · Not a live connection

02 / The boundaries matter

Your tools. Your account.
Your permission to connect.

Useful access starts with a clear boundary between the software you run and the Google account you authorize.

Open all the way through.

Inspect the code, run it yourself and contribute. The project is GPL-3.0 licensed, including the hosting implementation. There is no closed feature tier.

Connected to your account.

Local tools use your configured Google access. Public hosting is being built around individual customer authorization, never a shared maintainer account.

Clear about what it can do.

Current workflows are read-only. The complete API inventory separates implemented methods from coming-soon work. A roadmap entry is not a shipped tool.

03 / Built in the open

The whole map.
An honest starting point.

All 172 methods in the pinned Play API inventory are documented. Working tools and upcoming coverage stay visible in the repository.

Explore the full API catalog

  1. Release states, reviews & reports

    The first useful local workflows.

    Available

  2. Android vitals & error reporting

    25 Reporting reads, available from source.

    Available

  3. Customer OAuth hosting

    Development preview in source; public access is not live.

    In development

  4. Publishing & store operations

    Changes with explicit scope and verification.

    Planned

  5. Broader Play API coverage

    Monetization and remaining account workflows.

    Planned

04 / Start with the source

Make it part
of your workflow.

Run a reviewed checkout locally, configure your own Google access, then connect your MCP client.

Python 3.11+uvmacOS / Linux
Authentication & setup guide
01 / GET THE PROJECT 
git clone https://github.com/roadhero/google-play-mcp.git
cd google-play-mcp
uv sync --frozen

02 / CONNECT YOUR CLIENT

Google data requires your own authorization and an explicit app allowlist. No credentials are needed to explore the API catalog.