Open-source MCP server for Google Play developer workflows

Bring Google Play releases into your AI workspace.

PubShip is an open-source Model Context Protocol (MCP) server for Google Play Console workflows. Inspect releases, reviews and Android vitals from your AI client. Run locally with your own credentials, and explicitly authorize any changes.

Approved for inclusion in the GitHub MCP Registry

Starts the local server your client talks to

uvx pubship

Google data access requires credential setup. Follow the setup guide before your first query.

Workflows

Synthetic data · not a live account

Inspect a release

Show the production and internal-testing releases for com.example.app. Make no changes.

list_releases · productionlist_releases · internal

Production serves 2.4.0. 2.4.1 is in review, so it is not published yet. Internal testing has 2.5.0.

NextPreview a track update. Staging it needs a separate opt-in.

com.example.app

fetched 09:41 UTC · no changes made

production2.4.0240 · PUBLISHED2.4.1241 · IN_REVIEW
internal2.5.0250 · PUBLISHED

Release name, version code and lifecycle state, as Google returns them.

Raw response excerpt
"track": "production","fetched_at": "2026-10-08T09:41:07.482913+00:00","data": { "releases": [{ "releaseName": "2.4.1","releaseLifecycleState": "RELEASE_LIFECYCLE_STATE_IN_REVIEW","activeArtifacts": [{ "versionCode": 241 }] },{ "releaseName": "2.4.0", ... }] },"note": "Preserve releaseLifecycleState. In review is not published; obsolete releases are excluded by Google."

Feedback and quality

What are people saying about 2.4.0, and did the crash rate change after the rollout?

list_reviewsread_reporting · crashrate.get + crashrate.query

Crash rate for 2.4.0 rose from 0.38% to 0.52% by October 5. October 6 has no data yet, which is not the same as zero. Two of three recent reviews mention sign-out or crashes.

NextOpen the tablet review in full, then break the crash rate down by device model.

Daily crash rate, version 240

America/Los_Angeles

Daily vitals.crashrate.query; freshness from crashrate.get. Google reports fresh data through October 5.

  • 2 of 5 stars“Signs me out every time I switch apps since the update.” 2.4.0 · Oct 6
  • 4 of 5 stars“The new release history screen is much clearer.” 2.4.0 · Oct 6
  • 1 of 5 stars“Crashes when I open settings on my tablet.” 2.4.0 · Oct 5

Prepare a change

Change the en-US short description for com.example.app in my open edit. Show me the diff first.

After reviewing the diff: “I reviewed this diff. Apply this prepared change.”

prepare_store_listing_updateapply_store_listing_update

The new short description is staged in the edit. Nothing has been committed or published.

NextReview the whole edit, then commit it through the separately enabled edit lifecycle.

shortDescription · en-US

edits.listings.patch

Before: Plan trips and share itineraries.
After: Plan trips, share itineraries and keep tickets offline.
  1. 1 · Prepare

    Exact request and a single-use operation ID, valid up to 10 minutes.

  2. 2 · Review

    You check app, edit, locale and both values.

  3. 3 · Apply once

    Same ID as confirmation. It cannot be reused.

committed: falsepublication_verified: false

Requires GOOGLE_PLAY_WRITE_PACKAGES for the app, store presence editing permission and an existing edit.

Three workflows shown here. 170 implemented API methods in total.

Browse the method inventory

How it connects

Runs on your computer. Reaches Google with your access.

Local, not offline. PubShip calls Google directly and hands results to your client. No PubShip-run service sits in between.

Where you work

Your MCP client

Claude Code, Codex, Cursor, Gemini CLI or any stdio client

calls a toolgets the result

Local process

PubShip

On your computer, started with uvx pubship

HTTPS, your tokendata as returned

Source of the data

Google APIs

Android Publisher, Play Developer Reporting, bulk reports

Credentials

Your client config points to a key file on your disk. The project never receives it.

Permissions

Play Console permissions for your service account decide access. PubShip allowlists can only narrow them.

Results

Tool results go to your MCP client. Its own data handling applies.

Changes

Off by default. Each one is prepared, reviewed and applied once.

How permissions and data flow work

Clients

Works with the client you already use.

One local server, started with uvx pubship. Pick your client for the documented setup.

Claude Code

Add the server
claude mcp add --transport stdio pubship -- uvx pubship

Documented command

Set GOOGLE_APPLICATION_CREDENTIALS and GOOGLE_PLAY_PACKAGES in the shell that launches Claude Code, then run /mcp to check the connection.

Full instructions on GitHub

Codex

Add the server
codex mcp add pubship -- uvx pubship
codex mcp list

Documented command

Set GOOGLE_APPLICATION_CREDENTIALS and GOOGLE_PLAY_PACKAGES in the shell that launches Codex. Desktop apps can use a different PATH from your terminal.

Full instructions on GitHub

Cursor

Service account key file
/absolute/private/path/service-account.json
Package names
com.example.app

Plugin manifest

Not a Cursor marketplace listing. The plugin starts uvx pubship. Enter the key file path, never the key contents.

Full instructions on GitHub

Gemini CLI

Add the server
gemini extensions install https://github.com/pubship/pubship

Extension manifest

Native installation not verified. Enter your key file path and package names when prompted, then restart Gemini CLI.

Full instructions on GitHub

Any stdio client

MCP configuration (JSON)
{
  "mcpServers": {
    "pubship": {
      "command": "uvx",
      "args": ["pubship"],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "/absolute/private/path/service-account.json",
        "GOOGLE_PLAY_PACKAGES": "com.example.app"
      }
    }
  }
}

Standard stdio configuration

Command uvx, argument pubship. Keep shell syntax out of the command field.

Full instructions on GitHub

Documented means the repository describes the setup, not that every client version has been tested.

Get started

Four steps to your first read.

You need Python 3.11 or later, uv, an MCP client and access to your app in Play Console.

  1. Install uv

    uvx runs the published PubShip package.

    uv installation guide
  2. Set up Google access

    Your own service account, invited in Play Console. Read-only access is enough to start.

    How to set it up
  3. Add it to your client

    Give it your key file path and app package names. Never the key itself.

    Client setup steps
  4. Verify, then ask

    uvx pubship --check

    No credentials needed for the check. Then: “Show the production releases for com.example.app. Make no changes.”

Before you connect.

Start with a concrete workflow: check your Google Play release with MCP, including lifecycle states and data freshness.

What is an MCP server for Google Play?

An MCP server gives a compatible AI client tools for developer tasks. PubShip connects your client to Google's Play Developer APIs so you can inspect release tracks, read reviews, investigate Android vitals and prepare permitted changes for apps you own. It is an independent project, not an official Google product.

Can I use PubShip with Claude Code, Codex, Cursor or Gemini CLI?

Yes. PubShip runs locally over stdio, with setup instructions for those clients and a generic MCP configuration. You need uv, Google Play Console access and your own credentials. Follow the client setup guide; a documented configuration does not mean every client version has been tested.

Can PubShip change releases or store listings?

Reads are the default. Changes require explicit configuration for the app and method, the necessary Play Console permissions, and the operation's review and execution steps. Staging an edit is not publication, and submitting a release does not guarantee Google's approval. Start with the permissions and change controls.

Where do my credentials and app data go?

Your credentials stay on infrastructure you control; the PubShip project does not receive them. The local server calls Google and returns results to your MCP client. If that client uses a cloud AI model, the results may be processed by its provider. Review the data-flow explanation and your client's settings before connecting.