Short answer: install the community google-play-developer-mcp package, connect it to an MCP client, enable the Google Play Android Developer API and Play Developer Reporting API in Google Cloud, authorize a service account in Play Console, then register that account with the server’s accounts_add tool. Confirm access with auth_status and apps_list before attempting releases or other write operations.
“Google Play Console MCP server” is not a unique Google product name. This guide covers the community project documented as google-play-developer-mcp. Its maintainers describe support for Android Publisher API v3 and Play Developer Reporting API v1beta1, with examples for releases, reviews, subscriptions and crash reports. Tool names, package availability and permissions can change, so check the version you install and inspect its schemas in your MCP client.
What this MCP server does
Model Context Protocol (MCP) lets an AI application discover callable tools from a server. The client asks for the server’s tool specifications through the protocol’s tools/list method, then presents those tools to you or an agent. The Play project uses that pattern to expose Google Play publishing and reporting operations.
The project’s 2026 README claims 150 tools in 30 groups. That is a maintainer-reported figure, not an independent audit, and it may be stale. The same README identifies a first public release of 2026-04-20; verify the current npm package and repository release before relying on that date.
Recommended Free Tools
#1 Best Overall
Operations documented by the project
- Android Publisher API v3 tasks such as edits, app bundles, tracks and staged rollouts.
- Play Developer Reporting API v1beta1 queries, including crash-rate and error reports.
- Review listing and replies.
- Subscriptions and offers, including creation and activation.
- Multiple Play Console accounts, subject to the account registry and permissions of the installed version.
These are claims in the project documentation, not a guarantee that every endpoint or current Play Console feature is implemented. Read each tool’s argument schema before sending a request.
Prerequisites and access model
- A computer with Node.js and npm able to install a global package.
- An MCP-compatible client, such as Claude Desktop, Claude Code, Cursor or VS Code. The project README also lists other MCP-compliant clients; configuration keys differ by client.
- A Google Cloud project where both the Google Play Android Developer API and Play Developer Reporting API are enabled.
- A Google Cloud service account and a JSON key, unless your organization’s chosen client/server version documents another method.
- Play Console administrator access sufficient to invite the service-account email and grant the permissions your workflow needs.
Google’s general MCP guidance describes several possible authentication patterns, including Application Default Credentials, OAuth 2.0 client credentials and authorization headers. This community server’s documented setup uses a service-account key file and Play Console authorization instead. Do not assume the generic roles/mcp.toolUser role replaces Android Publisher or Play Console permissions; it does not.
Install the community server
- Install the package globally:
npm install -g google-play-developer-mcp - Confirm that your shell can find the executable:
google-play-developer-mcp --helpIf the command is not found, check npm’s global bin directory and your
PATH, then reopen the terminal. - Create an MCP server entry in your client. The command value documented by the project is
google-play-developer-mcp. A common JSON shape is:
{
"mcpServers": {
"google-play-developer": {
"command": "google-play-developer-mcp"
}
}
}Use the exact settings file and restart procedure for your client. Claude Desktop, Claude Code, Cursor and VS Code each expose configuration in different locations. Do not copy a Claude-specific path into another client and expect it to work.
Free tools Windows power users keep installed
One-click scans. No signup required.
Create Google Cloud credentials
- Open the Google Cloud project you intend to use.
- Enable the Google Play Android Developer API.
- Enable the Play Developer Reporting API if you need crash, error or other reporting tools.
- Create a service account for the integration.
- Create a JSON key and download it once. Store it outside your source repository, with file permissions and secret-management controls appropriate to your organization.
- Copy the service account’s email address; you will invite this identity in Play Console.
Keep the key path stable if the server’s local account registry records that path. Never commit the JSON file, paste it into prompts, or place it in a public issue. Follow your organization’s rotation and revocation policy.
Authorize the service account in Play Console
- In Play Console, open the users and permissions area for the developer account.
- Invite the service-account email address.
- Grant only the permissions required by your workflow. A read-only reporting job should not receive release-management rights; a release bot needs the specific publishing permissions required for edits, uploads, tracks and commits.
- Save the invitation and wait for access to propagate.
The project documentation warns that propagation can take up to 24 hours. An immediate PERMISSION_DENIED may therefore be temporary, but first verify the service-account identity, enabled APIs and exact Play Console permissions. Do not treat every denial as a propagation delay.
Register and verify an account
After the client loads the server, use its documented account-management tool. The project calls it accounts_add. The exact argument names are discoverable from the tool schema, so inspect that schema rather than guessing. Supply the path to the service-account JSON and the account details requested by your installed version.
- Run
accounts_addonce for the service-account key you want to use. - Run
auth_status. It should report whether the server can authenticate. - Run
apps_list. Confirm that the expected package names are visible. - Only after those checks succeed, try a read operation such as listing reviews or obtaining reporting data.
If several developer accounts are registered, select the intended account explicitly in the tool arguments when the schema provides an account identifier. This avoids publishing from the wrong organization.
Discover tools instead of guessing names
Use the MCP client’s tool panel or its generated schema view to inspect available operations. The project uses a resource/action naming style, but names and arguments can change. Look for:
- Required versus optional fields, especially package name, edit ID, track and version code.
- Whether an operation is read-only or mutates Play Console state.
- Pagination, date ranges and rate-limit fields for reports and reviews.
- Account-selection arguments when more than one service account is configured.
Google’s Developer Knowledge MCP reference explains the general role of tools/list; use the actual list returned by this Play server, not the reference server’s tool names.
Common workflows
Inspect apps and reviews
Start with apps_list to obtain package names visible to the authenticated account. Then use the review-listing tool’s schema to provide the package name, pagination token and any language or date filters it supports. A reply is a write operation: verify the review identifier and proposed text before invoking the reply tool.
Upload and release an Android App Bundle
The README’s release example follows this sequence:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute- Open an edit.
- Upload an Android App Bundle.
- Update a track.
- Commit the edit.
Before committing, check the package name, version code, target track, release status and rollout fraction. A commit can make a release available to users; treat it like a production deployment. If you are promoting beta to staged production, verify the source version and the exact percentage rather than relying on an agent’s summary.
Manage subscriptions and offers
The documented examples include creating and activating a subscription and an offer. Confirm product identifiers, base-plan or offer details, regional pricing and activation state in the tool schema. Use a read-back operation after a write so you can verify the resulting resource.
Query crashes and errors
Use the reporting tools for crash-rate and error data. Set an explicit time window and application package, record the query parameters used, and account for report latency. Reporting availability and field names can differ from publishing resources, so rely on the schema returned by your installed server.
Safe operating practices
- Separate read and write clients. Give investigation agents read permissions and reserve release credentials for a controlled workflow.
- Use narrow permissions. Grant the smallest Play Console role combination that completes the task.
- Require human review for commits. Have a person verify package, version, track, status and rollout fraction immediately before a release commit.
- Log intent, not secrets. Record account, package, operation and result, but never service-account JSON or access tokens.
- Pin and review updates. Tool coverage and deprecated endpoint handling are implementation details that can change with a new npm release.
Troubleshooting
“Command not found” after installation
The global npm executable directory is not on your PATH. Find npm’s global bin location, add it to the shell path, reopen the client and run google-play-developer-mcp --help.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The MCP client shows no tools
Check that the configuration key is named command, the value is exactly google-play-developer-mcp, and the client was fully restarted. Run the executable directly to expose startup errors. Also confirm that your client supports stdio MCP servers.
Authentication fails
Verify the JSON path, file readability, service-account email and active Google Cloud project. Ensure the required APIs are enabled. Re-register the account with accounts_add if the key was moved.
PERMISSION_DENIED from Play Console
Confirm that the invited identity is the same service account in the JSON file and that the required Play Console permissions were granted. Allow up to 24 hours for propagation, then retry. A valid Google Cloud role alone cannot grant Play Console publishing access.
The app is missing from apps_list
The service account may be invited to a different developer account, the invitation may not have propagated, or the app may not be visible under the granted permissions. Correct the invitation and rerun auth_status and apps_list.
Best Value
A release operation is rejected
Inspect required fields and current state: package name, edit, version code, track, release status and rollout fraction. An edit may have expired or another process may have changed the track. Re-read the resource, create a fresh edit when required, and do not retry a commit blindly.
How to evaluate another Play MCP server
If this package does not fit your environment, compare alternatives on the dimensions that affect operational risk:
| Question | Why it matters |
|---|---|
| API coverage | Does it cover Android Publisher and Play Developer Reporting APIs, and are deprecated endpoints handled? |
| Read versus write scope | Can you keep reporting agents read-only while limiting publishing actions? |
| Authentication and storage | How are OAuth credentials or service-account keys stored, rotated and selected? |
| Client compatibility | Does it work with your MCP client’s transport and configuration format? |
| Multi-account support | Can operators select the correct developer account safely? |
| Maintenance evidence | Are releases current, schemas documented and breaking changes communicated? |
No independent performance, uptime, adoption or productivity figures establish one server as superior. Treat maintainer-reported tool counts and release dates as changeable documentation.
Or skip the browser setup
If your project also needs clean website screenshots for release notes, QA evidence or agent context, ScreenshotNeo provides a separate screenshot API and MCP server. A single request returns PNG, JPEG, WebP or PDF; it is not a replacement for Play Console publishing, but it can remove browser automation from screenshot tasks.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the parameter reference in the ScreenshotNeo documentation. It accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups and chat widgets; bot checks, blank pages, timeouts, failed loads and cache hits are not billed, with the result identified by X-Page-Verdict and X-Billed headers. Its MCP server exposes take_screenshot, get_page_info and capture_pdf to Claude, Cursor and other MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.
Frequently Asked Questions
Is google-play-developer-mcp an official Google server?
No. The documented implementation is a community project. Google’s general MCP documentation is separate and does not establish that this repository is Google-authored.
Can I use OAuth instead of a service-account key?
Google MCP guidance describes several authentication methods, but this project’s documented setup uses a service-account JSON key and Play Console authorization. Confirm whether your installed version supports another method before changing the design.
How long should I wait after inviting the service account?
The project README says Play Console authorization can take up to 24 hours to propagate. During that period, verify the identity, enabled APIs and permissions rather than retrying a failing write indefinitely.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Does registering an account publish anything?
No. accounts_add, auth_status and apps_list are setup and verification actions. Publishing begins only when you invoke write tools such as edit, upload, track or commit operations.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
