playstore-release-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLAY_PACKAGE_NAME | Yes | The package name of your app in Play Console (e.g., com.example.myapp). | |
| GOOGLE_SERVICE_ACCOUNT_KEY_PATH | No | Path to the Google service account JSON key file. | |
| GOOGLE_SERVICE_ACCOUNT_KEY_CONTENT | No | Base64-encoded content of the Google service account JSON key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| play_doctorA | Verify Play release config end-to-end: service-account credentials, PLAY_PACKAGE_NAME, and (if creds are present) that the package can be reached via the Android Publisher API. Run this first in any release session. No local toolchain check is needed — builds arrive pre-signed from EAS/Gradle. |
| play_app_statusA | Snapshot of every release track (internal, closed testing, open testing, production) and their current release: version codes, rollout status, staged-rollout percentage. Use this to answer 'where is the release right now?' |
| play_upload_bundleA | Upload a signed .aab (Android App Bundle) to Play — the bundle must already be built and signed (e.g. by |
| play_release_to_trackA | Assign an uploaded versionCode to a release track and publish it there. Targeting 'production' rolls the release out to all users (subject to Google's automated policy review) — this is the point of no return for a public release; confirm with the human first for production. Testing tracks (internal/alpha/beta, or a custom closed-testing track name) publish immediately with no review gate. |
| play_update_listingA | Update Play Store listing text for a locale: title, short description, full description. Note: only Play Console (web) can fill out the Data Safety form and content rating questionnaire — those have no public API. |
| play_upload_graphicsA | Upload a store listing image: phone/tablet screenshots, the 512x512 hi-res icon, or the 1024x500 feature graphic. Unlike App Store Connect, Play's API supports uploading these directly — no Console click-through needed. |
| play_list_reviewsA | List recent user reviews with star ratings and text. No App Store Connect equivalent — Play exposes reviews directly via the API. |
| play_reply_reviewA | Post a public developer reply to a user review. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct action or resource: config verification, track status, bundle upload, releasing, listing text update, graphics upload, review listing, and reply. There is no overlap or ambiguity between them.
All tools share the 'play_' prefix and most follow a verb_noun pattern (upload_bundle, release_to_track, update_listing, list_reviews, reply_review). 'play_app_status' is a noun phrase rather than a verb action, which is a minor deviation, but the overall pattern is consistent and predictable.
8 tools is well-scoped for a Play Store release management server. Each tool covers an essential operation without redundancy, and the count fits comfortably within the typical 3-15 range.
The surface covers the core release lifecycle (upload, release, status) and store presence (listing text, graphics, reviews). Gaps include inability to read current listing text or images, adjust staged rollout percentages, or manage closed testers, but the primary workflows are sufficiently covered.