PubShip logo - MCP Servers AI tool

PubShip

MCP ServerFree

PubShip connects an AI assistant to Google Play Developer API resources through an MCP server. It can read release states, reviews, Android vitals, scoped reports, and selected catalog and account data, subject to configured access.

Last updated:

  • Official. Built and maintained by the company or project behind the service, so usually kept in step with it. Not audited by us.

  • Community. Built and maintained by an independent developer or group, not by the company behind the service. The company has not reviewed it, and updates depend on its author.

About PubShip

PubShip is an MCP server that connects an AI assistant to Google Play Developer API resources. With the operator’s Google credentials and appropriate Play Console access, an assistant can inspect release lifecycle states, recent written reviews, Android vitals, and scoped bulk reports. PubShip also provides tools for selected catalog and account resources, with sensitive data and write workflows kept behind separate configuration.

The project is designed to run under the operator’s control: locally as a stdio server, or as a self-hosted HTTP implementation. It does not provide a hosted service connected to Google Play. What an assistant can see or change depends on the credentials, permissions, and scopes configured for that PubShip instance.

What can PubShip do?

PubShip exposes Google Play data and operations through MCP tools. Developers can use it to review release status, examine recent written reviews, inspect Android vitals, and request reports scoped to the configured access. It also includes tools for catalog, subscription, product, and account resources.

For method-level work, the project includes API method discovery and schema inspection. Its access controls distinguish ordinary inspection from sensitive reads and optional writes. The specific available actions therefore depend on the configured app and method scopes, rather than simply on whether PubShip is installed.

  • Inspect release lifecycle states, recent written reviews, and Android vitals.
  • Read scoped bulk reports and inspect catalog, subscription, product, and account resources.
  • Discover API methods and inspect their schemas.
  • Prepare, review, and apply explicitly authorized changes through separate steps.

How PubShip connects and authenticates

PubShip runs locally as an MCP stdio server, using Google credentials supplied by the operator. The project also offers an HTTP implementation for operators to host on infrastructure they control; it is not a project-run Google-connected service. Documented Google authentication options include Application Default Credentials, gcloud impersonation, or a local service-account JSON key. The Google identity must also have appropriate Play Console access. Documented client support includes Claude Code, Codex, Cursor, Gemini CLI, and generic stdio MCP clients; native Gemini CLI installation is noted as unverified.

Who is PubShip best for?

PubShip is intended for developers and organizations managing their own apps and developer accounts who want an AI assistant to inspect Google Play resources through MCP. It suits workflows such as reviewing release states, written feedback, vitals, or scoped reports, as well as carefully configured administrative tasks. Users need their own Google credentials and suitable Play Console permissions. The project is free software, but that does not establish the cost of Google services or accounts; those costs were not verified.

What PubShip can access and change

Read access is limited by the Google service account’s permissions and PubShip’s configured app and method scopes. An app allowlist narrows requests but does not grant Google permissions. Sensitive purchase, order, transaction, and tester reads are off unless separately configured, and some require distinct app or method allowlists. Voided-purchase access is disabled by project policy, and the project reports that Google does not support one subscription-archive method. Optional writes require separate opt-in; preparation and application are distinct steps, with an operation ID used for the application step. These controls do not make unauthorized Google permissions available.

Alternatives to PubShip

For other MCP server options listed in this directory, compare Google Drive MCP, named for Google Drive, and GitHub Official MCP Server, named for GitHub. These links identify other directory listings, not verified substitutes for Google Play access. Check each listing’s documentation and access requirements to determine whether it fits your workflow; the verified PubShip facts do not establish the capabilities of those alternatives.

Key Features

Read Google Play release lifecycle states, recent written reviews, Android vitals, and scoped bulk reports.

Inspect catalog, subscription, product, and account resources.

Use API method discovery and schema inspection for supported Google Play methods.

Run locally as an MCP stdio server with your own Google credentials.

Self-host the HTTP implementation on infrastructure you control.

Optionally prepare, review, and apply authorized changes in separate steps.

Configure access with Google credentials and appropriate Play Console permissions.

Before you installSecurity checklist for MCP servers

An MCP server runs code and gives your AI assistant access to files, accounts or data. A few minutes of checking is worth it.

  1. Check the source. Make sure the repository belongs to the vendor or author you expect, that the vendor's own documentation links to it, and that it is actively maintained. Beware of lookalike names.
  2. Read what it can do. Look at the tools the server exposes and the permissions or scopes it asks for. Start with read-only access where the server allows it.
  3. Use the least access that works. Give it a dedicated API key or a narrowly scoped token, ideally on a test project or sandbox, not your production credentials.
  4. Pin versions and review updates. Install a specific version, read changes before upgrading, and do not run copied commands you do not understand.
  5. Treat what it returns as untrusted. Documents, web pages and tool results can contain text that tries to steer your AI assistant. Keep confirmation switched on for actions that write, delete, send or spend.
  6. Know where your data goes. Find out whether the server runs on your machine or is hosted, and what it sends to the vendor or to third parties.
  7. Keep a way back. Know how to revoke the key and remove the server from your client's configuration.

This page is general information, not security or legal advice, and listing a server is not an endorsement or a security review. We do not create, host or control MCP servers, and listing details such as commands, permissions or pricing can be out of date, so check the official source. You install and use MCP servers at your own risk. See the section on third-party products in our Terms of Service.

Pricing Plans

Free (open source)

Free

  • Free software under the AGPL-3.0-only license.
  • Use Google Play data with your own Google credentials and appropriate Play Console permissions.
  • Run locally over stdio, or self-host the HTTP implementation on infrastructure you control.
  • Google service pricing and account costs are not established by the project’s free-software status.

Pricing information last updated: October 27, 2026

FAQs

What Google Play information can PubShip access?

It can read release lifecycle states, recent written reviews, Android vitals, and scoped bulk reports. It also provides tools for catalog, subscription, product, and account resources. Access depends on configured scopes and Google permissions.

Does PubShip provide a hosted service connected to Google Play?

No. The documented primary option runs locally as an MCP stdio server using your Google credentials. An HTTP implementation is available for self-hosting on infrastructure you control.

What credentials and permissions do I need?

PubShip authenticates to Google with configured credentials. Documented options include Application Default Credentials, gcloud impersonation, or a local service-account JSON key. The account also needs appropriate Play Console access.

Can PubShip change Google Play data?

Optional write workflows can prepare, review, and apply explicitly authorized changes as separate steps. Write operations are off unless separately enabled; some require distinct app or method allowlists.

Are sensitive purchase records available by default?

No. Sensitive purchase, order, transaction, and tester reads require separate configuration. Voided-purchase access is disabled by project policy.