There is no single product uniquely identified as “the Google Play Console MCP server.” This walkthrough covers the community project google-play-developer-mcp, whose maintainers describe it as an MCP server for the Android Publisher API v3 and Play Developer Reporting API v1beta1. It is not a Google-authored server, and its setup instructions should not be assumed to apply to other implementations.
The basic flow is: install the project, configure it in an MCP client, enable the required Google APIs, authorize a service account in Play Console, register that account with the server, and verify app access before using tools. Treat publishing actions as consequential writes: inspect the release details and permissions before committing changes.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Google Play gift code | $200.00 | Buy on Amazon |
| 2 |
|
Google Play gift code | $50.00 | Buy on Amazon |
| 3 |
|
Google Play gift code | $25.00 | Buy on Amazon |
| 4 |
|
Google Play gift code | $100.00 | Buy on Amazon |
| 5 |
|
Google Play gift code | $200.00 | Buy on Amazon |
What this server is—and what it is not
The google-play-developer-mcp project exposes tools that its maintainers say cover the Android Publisher API v3 and Play Developer Reporting API v1beta1. Its README describes workflows involving releases, reviews, subscriptions, and crash reports. Those are maintainer claims about this implementation, not independent verification of every tool or of current compatibility.
The project README reports 150 tools across 30 groups in 2026. That is the project’s own count and can change as the software changes. The repository reports its first public release as 2026-04-20; that date does not establish the project’s current release state or whether the package remains available in the same form.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- No returns and no refunds on gift cards. Good for use on the US Google Play Store only. Terms apply - see below.
- Google Play gift codes can be used on the Google Play Store, the official app store for Android, to purchase apps, games, and more.
- To redeem, enter code in the Play Store app or play.google.com.
- Endless games to explore: Find and play old and new favorites – from mind-bending puzzles to epic quests and more.
- Just the app you’re looking for: Millions of apps means millions of ways to get things done, learn something new, and maybe even meet someone special.
An MCP server makes capabilities available to an AI application through tools. The client can discover tool names and argument schemas using the MCP tools/list method, but the schema you see from the server version you install—not a general example—is the authority for its inputs. Google’s general MCP documentation and the project’s setup instructions address different things: Google’s guidance describes general authentication concepts, while this walkthrough’s commands and account tools are specific to the community project.
What you need before setup
- An MCP-compatible client that can launch a local server process. The project README includes examples for Claude Desktop, Claude Code, Cursor, VS Code, and other MCP-compliant clients; exact configuration fields can differ by client and version.
- Node.js and npm, since the project documents npm installation.
- A Google Cloud project where you can enable the Google Play Android Developer API and Play Developer Reporting API.
- A service account and its JSON key, plus permission to invite that service account in Play Console and grant it the access required for your intended tasks.
- The package’s current README and the current configuration instructions for your MCP client. Client settings and project details can change, so use the instructions matching the versions you actually install.
Google API enablement and Play Console access are separate requirements. Enabling an API in Cloud does not by itself grant the service account permission to manage or read an app in Play Console.
Install and configure the community server
1. Install the npm package
In a terminal, run the installation command documented by the project:
npm install -g google-play-developer-mcp
This installs the command the project says to use as the MCP server process. If npm cannot find the package or the resulting command is unavailable, check the project’s current package instructions and your npm global executable path rather than assuming an unrelated server’s installation steps will work.
2. Add a server entry to your MCP client
In the MCP client’s configuration, add a server entry named google-play-developer with its command set to google-play-developer-mcp. The project README supplies client-specific examples; use the example for your client and preserve its expected configuration format. Do not paste a configuration snippet for one client into another without checking its syntax and configuration location.
Rank #2
- No returns and no refunds on gift cards. Good for use on the US Google Play Store only. Terms apply - see below.
- Google Play gift codes can be used on the Google Play Store, the official app store for Android, to purchase apps, games, and more.
- To redeem, enter code in the Play Store app or play.google.com.
- Endless games to explore: Find and play old and new favorites – from mind-bending puzzles to epic quests and more.
- Just the app you’re looking for: Millions of apps means millions of ways to get things done, learn something new, and maybe even meet someone special.
Restart or reload the MCP client if required by that client. Then confirm that the server starts and that its tools appear in the client’s tool list. A server process can be installed successfully yet still fail to start if the client configuration is malformed or the executable cannot be found.
Enable Google APIs and authorize the service account
1. Enable both APIs in Google Cloud
In the Google Cloud project used for the integration, enable the Google Play Android Developer API and the Play Developer Reporting API. The server’s documented coverage includes both; enabling only one may leave workflows that depend on the other unavailable.
2. Create a service account and key
Create a service account in that Cloud project and create a JSON key following the repository’s current instructions. The key is a credential, not an ordinary configuration file. Store it outside your code repository, restrict who can read it, and follow your organization’s key rotation and handling requirements. Never commit it to Git or put its contents in a prompt, issue, or log.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall3. Invite the service account in Play Console
In Play Console, invite the service account’s email address and grant the permissions needed for the tasks you intend to perform. Choose narrower permissions when they are sufficient; a workflow that only reads reports does not inherently justify broad release-management access. Check both the identity you invited and the app-level or account-level scope of the granted permissions.
The project README says Play Console authorization may take up to 24 hours to propagate. If access fails immediately after granting permissions, propagation could be a factor, but it is not the only possible cause. Verify the service-account email, API enablement, key file, and actual permissions before concluding that waiting will fix a denial.
Rank #3
- No returns and no refunds on gift cards. Good for use on the US Google Play Store only. Terms apply - see below.
- Google Play gift codes can be used on the Google Play Store, the official app store for Android, to purchase apps, games, and more.
- To redeem, enter code in the Play Store app or play.google.com.
- Endless games to explore: Find and play old and new favorites – from mind-bending puzzles to epic quests and more.
- Just the app you’re looking for: Millions of apps means millions of ways to get things done, learn something new, and maybe even meet someone special.
Register the account and verify access
The project documents an account-registration tool named accounts_add. Use the MCP client’s tool interface to call it with the arguments required by the installed version’s schema. The README describes the server as storing a key-file path in its local account registry; verify that behavior against the version you use and protect the registry accordingly.
- Call
accounts_addto register the service account using the installed server’s displayed argument schema. - Call
auth_statusand confirm the server reports an authenticated account. - Call
apps_listand confirm that the apps you expect are visible to that account. - Only after those checks succeed, proceed to the read or write workflow you need.
These checks distinguish credential recognition from useful Play Console access: authentication can succeed while the account still lacks permission to see a particular app or perform a particular action.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsUse tools safely for common Play Console tasks
Inspect the tool schema before calling a tool
Tool names follow a resource-and-action pattern in the project examples, but names alone do not tell you all required arguments or the effect of a call. In your MCP client, inspect the available tools and their argument schemas. Google’s Developer Knowledge MCP reference explains the general MCP distinction between tools and tool discovery; it documents Google’s Developer Knowledge server, not this Play Console project. For actual arguments, use the schema exposed by the Play Console server you installed.
Read reviews and reports
The README includes examples for listing and replying to reviews and querying crash-rate and error reports. Start with read operations to confirm the app, date range, and returned data are the ones you intend. For a reply, verify the review identity and the exact response text before making the write.
Create or activate subscriptions and offers
The project documentation includes subscription and offer creation and activation examples. These operations can affect products visible to customers. Confirm the target app, product identifiers, offer details, and desired activation state against the tool schema and your Play Console plan before submitting a write.
Rank #4
- No returns and no refunds on gift cards. Good for use on the US Google Play Store only. Terms apply - see below.
- Google Play gift codes can be used on the Google Play Store, the official app store for Android, to purchase apps, games, and more.
- To redeem, enter code in the Play Store app or play.google.com.
- Endless games to explore: Find and play old and new favorites – from mind-bending puzzles to epic quests and more.
- Just the app you’re looking for: Millions of apps means millions of ways to get things done, learn something new, and maybe even meet someone special.
Upload and publish a release
The README demonstrates opening an edit, uploading an Android App Bundle, updating a track, and committing the edit. It also demonstrates promoting a beta version to a staged production rollout. These are not merely informational calls: committing an edit can publish or change release state.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →- Confirm the target package name and app before opening or changing an edit.
- Verify the uploaded bundle and version code, and check that the intended track is selected.
- Review release status and rollout fraction. For a staged rollout, ensure the fraction is the one you intend rather than assuming a default is safe.
- Check the exact pending changes before committing the edit, and confirm that the acting account has the required write permissions.
The README’s sample workflow illustrates the project’s documented capabilities; it is not evidence that a particular release was executed or that a write is safe without review.
Permissions, authentication, and security boundaries
The community project’s documented approach uses a service-account JSON key and Play Console authorization. Google’s general guidance says Google and Google Cloud MCP servers may use Application Default Credentials (ADC), OAuth 2.0 client credentials, or an authorization header depending on the client and server; support varies. That general guidance does not change this project’s stated service-account setup.
Google’s roles/mcp.toolUser role, described in Google’s general MCP documentation, grants permission to make calls to Google or Google Cloud MCP tools. Do not treat it as a replacement for the Play Console and Android Publisher API permissions this community implementation requires. Grant only the resources and actions needed for your workflow, and reassess access when the workflow or personnel change.
Troubleshooting
The MCP client does not show the server’s tools
- Check that the client configuration entry uses the command
google-play-developer-mcpand follows that client’s own syntax. - Confirm npm installed the package and that the client process can resolve the global executable.
- Reload or restart the client if its configuration changes require it, then inspect its server startup diagnostics.
- Check the tool list after startup; a running client does not prove the MCP server started correctly.
PERMISSION_DENIED or an app is missing
- Confirm the invited service-account email exactly matches the identity associated with the JSON key.
- Check that the relevant APIs are enabled in the intended Google Cloud project.
- Verify the account was granted the permissions required for that app and action in Play Console.
- If permissions were just granted, allow for the propagation delay the project documents, which may be up to 24 hours; do not use delay as a substitute for checking the other causes.
- Run
auth_statusandapps_listagain to identify whether authentication or app visibility is the failing step.
Authentication fails after account registration
- Check that the JSON key file exists at the path registered with the server and is readable by the user running the MCP client.
- Confirm you registered the intended account with
accounts_addand inspect the installed tool schema for the exact expected arguments. - Make sure the key belongs to the service-account identity invited to Play Console; a valid key for a different account will not inherit the intended access.
- Keep credentials out of source control and avoid sharing diagnostic output that contains secrets.
A write call fails or changes the wrong target
- Inspect the tool schema and request arguments from the running server instead of relying on a remembered example.
- Recheck the app, package name, track, release status, product identifier, and other target values before retrying.
- Confirm the account has the necessary write permission. A successful read or
auth_statusresult does not establish write access. - For release changes, verify the edit and rollout details before committing; do not repeat a commit blindly after an ambiguous client error.
Maintenance and operational considerations
Tool coverage, npm availability, supported clients, authentication behavior, and API compatibility are implementation details that can change. Before a production workflow, check the current repository release and package instructions, inspect the tools exposed by the installed version, and review whether the APIs and permissions still match your organization’s requirements. The project’s published count of 150 tools across 30 groups is a dated maintainer figure, not a guarantee that those tools are present in every version.
Best Value
- No returns and no refunds on gift cards. Good for use on the US Google Play Store only. Terms apply - see below.
- Google Play gift codes can be used on the Google Play Store, the official app store for Android, to purchase apps, games, and more.
- New finds, old favorites, one card. Choose a unique gift card design featuring your favorite games or apps. This card can also be used for anything else on Google Play. There’s something for everyone, so find what’s yours. Go Play.
- Easy to use: With a Google Play gift code, you never have to worry about expiration dates or fees.
- Endless games to explore: Find and play old and new favorites – from mind-bending puzzles to epic quests and more.
Use a dedicated service account and a credential storage approach appropriate to your environment. Restrict access to the key and to the local account registry, monitor which users can invoke write-capable tools, and test new workflows on low-risk or non-production targets where practical. No independent performance, reliability, adoption, or productivity measurements are established for this server, so evaluate it against your own operational requirements rather than inferring service guarantees from the tool count.
Or skip the browser setup
ScreenshotNeo is a separate website screenshot API and MCP server, not a way to manage Play Console. If the task alongside Play Console work is capturing a web page, its API can return a screenshot in one GET request. The API accepts cookie banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; those steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and responses identify the page verdict and billing status in headers. ScreenshotNeo also has an MCP server with take_screenshot, get_page_info, and capture_pdf tools for AI agents.
Example using cURL, with the API key supplied by you and the target URL set to Stripe:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →See the ScreenshotNeo API documentation for parameters and response details. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
Frequently Asked Questions
Is the Google Play Console MCP server an official Google product?
The implementation covered here is a community project, not a Google-authored server. The name does not identify one unique implementation.
Can I use the same setup instructions with every MCP client?
No. The project provides client-specific configuration examples, and MCP client configuration formats and authentication support can differ. Follow the current instructions for your client and installed server.
Does an authenticated service account automatically have release access?
No. Authentication confirms an account can be recognized; Play Console permissions determine which apps and actions it can access.
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.
