google-play-developer-mcp

The complete Model Context Protocol (MCP) server for Google Play. 150 tools. Full Android Publisher API v3 + Play Developer Reporting API v1beta1. No deprecated endpoints. Works with Claude, Cursor, VS Code Copilot, Gemini CLI, or any MCP client.

See also: app-store-connect-mcp — the same philosophy for Apple's App Store Connect.

Table of Contents

• Why this exists

• Feature matrix

• Quick start

• Step-by-step setup

• Register with your MCP client

• Usage examples

• Tool reference

• Security

• Design notes

• Contributing

• Version history

• References

Why this exists

Google Play Console has an API, but its surface is wide and moves fast. Existing community MCPs each cover a slice — one does store listings, another does releases, a third does reviews — and all lag behind Google's deprecations.

google-play-developer-mcp is the one that covers everything.

If you drive Google Play Console with an AI assistant — release automation, review triage, subscription catalog management, crash triage — this gives the assistant a full toolbox in one install.

Feature matrix

150 tools across 30 groups. Every non-deprecated endpoint in both APIs.

Quick start

npm install -g google-play-developer-mcp

Then in your MCP client config (e.g. ~/.config/claude/config.json, Cursor MCP config, or VS Code mcp.json):

{
  "mcpServers": {
    "google-play-developer": {
      "command": "google-play-developer-mcp"
    }
  }
}

Next, tell the server which Play Console account to use — see the setup guide below.

Step-by-step setup

1. Create a Google Cloud service account

1. Open the Google Cloud Console.

2. Select or create a project (any project — this is just where the service account lives).

3. APIs & Services → Library — enable both of these:

   • Google Play Android Developer API

   • Google Play Developer Reporting API

4. IAM & Admin → Service Accounts → Create service account.

5. Once created, open the account → Keys → Add key → JSON. Download the JSON file.

6. Move the JSON file somewhere safe and outside any git repo. A good location: ~/.config/google-play-developer-mcp/service-account.json.

2. Authorize the service account in Play Console

1. Open Play Console.

2. Users and permissions → Invite new user. Paste the service account email (it looks like name@project-id.iam.gserviceaccount.com).

3. Assign permissions:

   • Admin (all permissions) for full access.

   • Or narrower combinations (View app information, Manage store presence, Manage orders and subscriptions, etc.) if you want to restrict what the MCP can do.

4. Wait up to 24 hours. Play Console takes time to propagate the new authorization — this is a common gotcha. If early API calls return PERMISSION_DENIED, this is usually why.

3. Register the account with the MCP server

Launch any MCP client that has the server configured, then run:

accounts_add --name my-app \
  --keyFile /Users/you/.config/google-play-developer-mcp/service-account.json \
  --description "My company's Play Console"

(Or manually create ~/.google-play-developer-mcp/accounts.json — see the file format below.)

4. Verify

auth_status

Should return { ok: true, email: "..." }.

apps_list

Lists the apps the service account can see.

Register with your MCP client

Claude Desktop

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "google-play-developer": {
      "command": "google-play-developer-mcp"
    }
  }
}

Claude Code

claude mcp add google-play-developer google-play-developer-mcp

Or edit ~/.claude.json:

{
  "mcpServers": {
    "google-play-developer": {
      "command": "google-play-developer-mcp"
    }
  }
}

Cursor

Settings → MCP → Add new MCP server:

{
  "google-play-developer": {
    "command": "google-play-developer-mcp"
  }
}

VS Code (GitHub Copilot agent mode)

.vscode/mcp.json:

{
  "servers": {
    "google-play-developer": {
      "type": "stdio",
      "command": "google-play-developer-mcp"
    }
  }
}

Gemini CLI / Codex CLI / Windsurf / Continue

Any MCP-compliant client accepts the same command entry — point it at the globally installed google-play-developer-mcp binary (or at node /path/to/dist/index.js if running from source).

Running from source (no npm install -g)

git clone https://github.com/devinwang/google-play-developer-mcp.git
cd google-play-developer-mcp
npm install
npm run build

Then in your MCP client config:

{
  "mcpServers": {
    "google-play-developer": {
      "command": "node",
      "args": ["/absolute/path/to/google-play-developer-mcp/dist/index.js"]
    }
  }
}

Usage examples

Release a new build to internal testing

accounts_switch --name my-app

# Open an edit, upload bundle, route it to the internal track, commit.
edits_insert --packageName com.example.app
# → { id: "EDIT_ID", expiryTimeSeconds: "..." }

bundles_upload --packageName com.example.app --editId EDIT_ID \
  --file /path/to/app-release.aab
# → { versionCode: 47, sha256: "..." }

tracks_update --packageName com.example.app --editId EDIT_ID \
  --track internal \
  --releases '[{"versionCodes":["47"],"status":"completed","releaseNotes":[{"language":"en-US","text":"Fixes a crash on startup."}]}]'

edits_commit --packageName com.example.app --editId EDIT_ID

Promote a release from beta to production with staged rollout

edits_insert --packageName com.example.app
# → EDIT_ID

# Promote the beta versionCodes to production with 10% staged rollout.
tracks_update --packageName com.example.app --editId EDIT_ID \
  --track production \
  --releases '[{"versionCodes":["47"],"status":"inProgress","userFraction":0.1}]'

edits_commit --packageName com.example.app --editId EDIT_ID

Reply to reviews

reviews_list --packageName com.example.app --maxResults 50
# → { reviews: [{ reviewId, authorName, comments, ... }] }

reviews_reply --packageName com.example.app --reviewId REVIEW_ID \
  --replyText "Thanks for the feedback! The crash is fixed in v1.2 — please update."

Create a subscription with a free-trial offer

# 1. Create the subscription (product)
subscriptions_create --packageName com.example.app --productId plus_monthly \
  --subscription '{"listings":[{"languageCode":"en-US","title":"Plus","benefits":["All premium features"]}],"taxAndComplianceSettings":{"taxTier":"TAX_TIER_UNSPECIFIED"}}'

# 2. Create a base plan
subscription_base_plans_batch_update --packageName com.example.app --productId plus_monthly \
  --requests '[{"basePlan":{"basePlanId":"monthly","autoRenewingBasePlanType":{"billingPeriodDuration":"P1M","accountHoldDuration":"P30D"},"state":"DRAFT","regionalConfigs":[{"regionCode":"US","price":{"currencyCode":"USD","units":"9","nanos":990000000}}]},"updateMask":"autoRenewingBasePlanType,regionalConfigs"}]'

# 3. Activate the base plan
subscription_base_plans_activate --packageName com.example.app \
  --productId plus_monthly --basePlanId monthly

# 4. Create a 7-day free-trial offer
subscription_offers_create --packageName com.example.app --productId plus_monthly \
  --basePlanId monthly --offerId new-user-trial \
  --offer '{"phases":[{"duration":"P7D","regionalConfigs":[{"regionCode":"US","free":true}]}],"state":"DRAFT"}'

subscription_offers_activate --packageName com.example.app \
  --productId plus_monthly --basePlanId monthly --offerId new-user-trial

Verify a purchase token server-side (backend use case)

# For a one-time product (consumable or non-consumable)
purchases_products_v2_get --packageName com.example.app --token PURCHASE_TOKEN

# For a subscription — includes 2026 OfferPhase, priceChangeState, etc.
purchases_subscriptions_v2_get --packageName com.example.app --token PURCHASE_TOKEN

Triage crashes

reports_crash_rate_query \
  --name "apps/com.example.app/crashRateMetricSet" \
  --dimensions '["versionCode","countryCode"]' \
  --metrics '["crashRate","distinctUsers"]' \
  --timelineSpec '{"aggregationPeriod":"DAILY","startTime":{"year":2026,"month":4,"day":1},"endTime":{"year":2026,"month":4,"day":8}}'

reports_errors_issues_search --parent "apps/com.example.app" \
  --filter "errorIssueType = \"CRASH\""

Tool reference

All tools use snake_case names following the resource_action convention, consistent with the Android Publisher URL structure. See the Feature matrix for the full group breakdown.

Each tool accepts a JSON object of arguments — inspect the schema from your MCP client (Claude Code: /mcp tools, Claude Desktop: show tool list in chat, Cursor: MCP panel) to see the exact shape.

Complex body arguments (e.g. subscription, offer, appRecoveryAction, subscription releases) accept the Google-documented JSON schema directly — see the official reference.

Security

This repo ships with zero credentials. You bring a service-account JSON key; the server records only the path.

What is and isn't on disk:

.gitignore blocks

• *.json.key, *service-account*.json, *service_account*.json, *-sa.json, *-sa-key.json

• gcp-key*.json, google-credentials*.json, play-credentials*.json

• .env, .env.* (but keeps .env.example)

• accounts.json, credentials/, keys/, secrets/

• *.pem, *.p12, *.pfx, *.key, id_rsa*

Recommended hygiene

• Keep your service-account JSON outside any git repo on your machine.

• Grant the service account the narrowest role that your workflow needs. Full admin grants the MCP permission to delete app metadata — give it only what you need.

• Rotate the service-account key yearly: delete the old key in Google Cloud Console, create a new one, run accounts_update --keyFile <newPath>.

• auth_status never returns the actual token; only a boolean and the service-account email.

Audit trail

Every write operation on the Android Publisher API is logged by Google Cloud IAM under the service account's identity. If you ever suspect misuse, IAM → Audit Logs in the Cloud Console will show which endpoints were called.

Design notes

• Edit-session-aware. Every write on the Android Publisher API runs inside an edit. The server exposes edits_insert / edits_commit / edits_delete directly so you can hold an edit open across many tool calls — the most common multi-step flow. If you forget to commit, nothing ships. Safe by default.

• Multi-account. One server process can manage many Play Console accounts. Switch with accounts_switch. State lives in ~/.google-play-developer-mcp/accounts.json.

• No deprecated endpoints. Catalogue endpoints use monetization.onetimeproducts (not the deprecated inappproducts). Purchase verification uses purchasesV2 / subscriptionsV2.

• Forward-compatible types. Where Google ships an API feature faster than the googleapis TypeScript typings, we cast through publisherAny() / reportingAny(). The HTTP calls are identical — only TypeScript's static check is skipped on the known-drifting surfaces.

• Good error messages. Every Google API error is translated — 401 becomes "your token is wrong", 403 becomes "permission not propagated, wait 24h", 429 becomes "quota exhausted", etc.

• Stateless transport. Server is stdio, no network listener, no persistent state beyond the accounts file.

• Zero telemetry. The server never phones home.

Contributing

PRs welcome. Before you submit:

• npm run typecheck passes (CI will also run this)

• Never include a service-account key or token in an issue or PR. If you need to share a reproduction, redact the token (X-Goog-Api-Client: ...REDACTED...).

• New tools follow the resource_action naming convention.

• If you add a tool that hits a new API surface, add it to the Feature matrix so the doc stays in sync.

Version history

0.1.0 — 2026-04-20 (first public release)

• 150 MCP tools covering the full Android Publisher API v3 and Play Developer Reporting API v1beta1.

• Latest-generation endpoints only. Uses monetization.onetimeproducts (replaces deprecated inappproducts), purchases.productsv2 / subscriptionsv2 (replaces v1).

• 2026 features. SubscriptionPurchaseV2.offerPhase, purchases.subscriptionsv2.cancel/defer, orders.batchGet, offerPhaseDetails, price step-up consent, outOfAppPurchaseContext.

• Multi-account support with on-disk registry.

• Zero credentials in the repository. Comprehensive .gitignore.

• Error translation for all common Google API failure modes.

References

• Google Play Android Developer API v3 — REST reference

• Play Developer API release notes

• Play Developer Reporting API v1beta1 — REST reference

• monetization.onetimeproducts reference

• purchases.subscriptionsv2 reference

• Model Context Protocol specification

• Anthropic Claude MCP documentation

License

MIT — see LICENSE.