playstore-release
Provides tools for publishing and managing Android apps on Google Play, including bundle uploads, listing, track releases, promotions, data safety, reviews, and subscriptions via the Google Play Developer API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@playstore-releaserun the readiness check and show the next actions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
playstore-release
Ship an Android app to Google Play end-to-end over the Google Play Developer API — an opinionated, idempotent publishing pipeline with a readiness report, for humans and AI agents. The Android sibling of appstore-release.
No dependencies. Clone it and run it.
git clone https://github.com/beydemirfurkan/playstore-release ~/playstore-release
export PLAY_SERVICE_ACCOUNT_JSON=/abs/service-account.json PLAY_PACKAGE_NAME=com.example.app
node ~/playstore-release/src/cli.mjs doctor
node ~/playstore-release/src/cli.mjs checkWhat it does
command | what |
| credentials present and accepted; can this account open an edit for this app |
| the readiness report: a verdict ( |
| bundle → contact details → listing → graphics → track release → testers, in one edit, committed once; idempotent |
| internal → production, full or staged; |
| apply the Data safety CSV exported from the Console |
| read and answer user reviews |
| create / update / activate subscription products |
| author a config without credentials |
| the same surface as 10 MCP tools + 7 resources over stdio |
What Google keeps Console-only — creating the app, the first bundle upload, content rating, app access, ads / news / government / financial / health declarations, privacy policy, category, countries, pricing — is reported by check with the exact URL and clicks, and spelled out in references/console.md so a browser agent can fill the forms for you.
Related MCP server: play-store-mcp
Design
Everything is an edit. Reads and writes go through one
EditManager; a pipeline holds it and commits once; any error discards it.--dry-runopens and discards an edit to read state and never validates or commits.Idempotent, provably. A second
publishwith nothing changed sends onlyedits.insert+edits.delete— there is a test asserting exactly that.Findings, not logs. Every problem is a
Findingwith an owner (cli·ui·external), a fix, and — for Console-only steps — the clicks. The CLI text,--jsonand the MCP tools render the same objects.Local validation first. Screenshot aspect ratio (long side ≤ 2× short), feature graphic size and alpha, listing lengths, rollout fractions: all checked before a byte is sent.
Layout
src/cli.mjs dispatcher src/ops/ one file per operation (see _contract.md)
src/index.mjs library API src/report/ snapshot → checks → verdict → renderings
src/core/ config, findings, console steps
src/play/ auth (RS256 → OAuth), client, edits, uploads, image headers, error hints
src/mcp/ zero-dep JSON-RPC MCP server
skills/playstore-release/ the Claude Code skill: SKILL.md + references/As a Claude Code skill
node scripts/install-skill.mjs # symlinks ~/.claude/skills/playstore-release → skills/playstore-releaseOr as a plugin: the repo carries .claude-plugin/ and .mcp.json.
Development
npm install # dev tooling only (prettier, tsc, ajv)
npm run verify # typecheck · format · schema · manifests · distribution · testsMIT.
This server cannot be deployed
Maintenance
Related MCP Connectors
7 Google Play endpoints. Pay per call in USDC via x402.
Run App Store Connect from your IDE: pricing, listings, screenshots, releases, AI visibility.
Read products, sales, subscribers and offer codes; verify, enable and disable product licenses.
Provides access to Google's public developer documentation.
Related MCP Servers
- AlicenseAqualityAmaintenanceManage the full Google Play Store release lifecycle directly — from uploading artifacts to managing testers, rollouts, and Android Vitals.166MIT
- FlicenseNot gradedqualityBmaintenanceEnables to interact with Google Play Console, allowing release management, app vitals monitoring, and APK/AAB deployment via a service account.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to automate Android release workflows via the Google Play Android Publisher API, including deploying builds, managing listings, and replying to reviews.13MIT
- AlicenseAqualityAmaintenanceEnables AI agents to manage Google Play Console reviews and Android app releases, including replying to reviews, promoting releases, managing staged rollouts, and checking crash/ANR vitals.4411 npm1MIT