Google Play Developer MCP

google-play-developer-mcp

The complete Model Context Protocol (MCP) server for Google Play.

157 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

157 tools across 33 groups. Every non-deprecated endpoint in both APIs.

Android Publisher API v3

Play Developer Reporting API v1beta1

---

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

1. IAM & Admin → Service Accounts → Create service account.
2. Once created, open the account → Keys → Add key → JSON. Download the JSON file.
3. 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.

1. 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 \ --