
Google Play Console MCP
io.github.AgiMaulana由 GitHub 帳號 AgiMaulana 發布v0.5.0更新於 Oct 24, 2026
Google Play release lifecycle: tracks, testers, rollout, and Android Vitals.
概覽
一個本機 MCP 伺服器,讓助理透過 Play Console API 管理 Google Play 的發布、測試人員、建置產物與 Android Vitals。
- 可以做什麼
- 列出各軌道,檢視軌道狀態、分段發布比例與版本說明,並建立、更新、暫停、恢復發布或在軌道間提升發布。列出 APK 與 AAB 及其版本代碼與雜湊,一步上傳產物並建立發布,或將建置推送到內部應用程式分享以取得下載連結。讀取並整批取代內部測試與封閉測試軌道的測試人員電子郵件清單與 Google 群組。讀取 Android Vitals:依版本代碼統計每日當機率、ANR 率、背景喚醒鎖與過度喚醒率,以及附門檻標記的綜合摘要。
- 適用情境
- 適合發布 Android 應用程式的團隊,讓助理處理 Play 商店的發布事務:分段發布、軌道提升、測試人員名單調整、產物上傳,以及發布前後檢查當機與 ANR 健康狀況。
- 執行需求
- 以 Python 套件形式在本機執行(uvx 或 pip install)。需要一個 Google Cloud 服務帳戶 JSON 金鑰,透過 GOOGLE_APPLICATION_CREDENTIALS 傳入其絕對路徑,並在 Play Console 中為該帳戶授予帳戶層級與應用程式層級權限。Cloud 專案中需啟用 Google Play Android Developer API 與 Google Play Developer Reporting API。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Google Play Console MCP,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
Google Play Console MCP
[Google Play Console MCP server]
[GooglePlayConsoleMcp MCP server] [MCP Badge] [License: MIT]
A Python Model Context Protocol server that lets AI assistants (Claude, etc.) manage the full Google Play Store release lifecycle directly — from uploading artifacts to managing testers, rollouts, and Android Vitals.
Quick start
Option A — uvx (recommended, no install needed)
Run this once. Claude automatically starts and stops the server for every session — you never have to touch it again.
Requires
uv— install withbrew install uvorcurl -Lsf https://astral.sh/uv/install.sh | sh
Option B — pip install
If you prefer a permanent install:
Option C — HTTP (local server)
Only needed if you want to connect via HTTP transport instead of stdio:
How stdio works: With Options A and B, there is no server to start manually. Claude launches the process in the background when a session opens and shuts it down when the session ends. Zero maintenance.
Features
Tracks & Releases
Artifact Management
Tester Management
Android Vitals
Prerequisites
uv— install guide- A Google Cloud service account with the JSON key downloaded.
- The service account added to Google Play Console with the correct permissions (see below).
- These APIs enabled in your Google Cloud project:
Required Play Console permissions
Important: Release Manager does not grant Reporting API access. You must also enable View app information and download bulk reports (read-only) — both at account level and per-app level — for the Vitals tools to work.
Claude Desktop integration
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
Restart Claude Desktop after saving.
Service account setup
- Go to IAM & Admin → Service Accounts in your GCP project.
- Create a service account (or use an existing one) and download a JSON key.
- In Google Play Console → Setup → API access:
- Link your Google Cloud project.
- Find the service account → Manage Play Console permissions.
- Under Account permissions, enable View app information and download bulk reports (read-only).
- Under App permissions for each app, enable:
- View app information and download bulk reports (read-only)
- Release to production… (if you need write access)
- Click Apply → Invite user.
Permissions must be granted at both account level and per-app level. Account-level alone is not sufficient for the Reporting API.
Tool reference
list_tracks
Returns all tracks with their releases, rollout percentages, statuses, and country availability.
get_track_info
Returns a human-readable summary plus releases with status, rollout %, version codes, and release notes.
create_release
Creates or replaces a release on the given track. Use status="inProgress" with a
rollout_percentage for a staged production rollout, or status="completed" to release
to all users immediately.
update_release
Update an existing release. Common use cases:
- Increase rollout:
update_release(pkg, rollout_percentage=50) - Complete rollout:
update_release(pkg, rollout_percentage=100) - Halt rollout:
update_release(pkg, status="halted") - Resume rollout:
update_release(pkg, status="inProgress")
promote_release
Copies a release from one track to another. Release notes and name are inherited from the source release unless explicitly overridden.
list_artifacts
Returns all APKs and AABs sorted by version code (newest first) with SHA hashes.
upload_artifact
Uploads an APK or AAB (auto-detected from extension) and creates a release on the given track in a single atomic operation. Returns the assigned version code.
upload_to_internal_sharing
Uploads a build to Internal App Sharing (bypasses track assignment) and returns a
shareable downloadUrl. Testers must have Internal App Sharing enabled in their Play
Store settings. Ideal for quick one-off testing without affecting any release track.
get_testers
Returns the list of tester email addresses and Google Groups for the track.
update_testers
Warning: This is a full replacement. Testers not in the new list will lose access. Call
get_testersfirst to retrieve the current list if you only want to add/remove individuals.
get_crash_rate
Returns daily crashRate, userPerceivedCrashRate, and distinctUsers per version code.
Google's bad behavior threshold for user-perceived crash rate is ~1.09%.
get_anr_rate
Returns daily anrRate, userPerceivedAnrRate, and distinctUsers per version code.
Google's bad behavior threshold for user-perceived ANR rate is ~0.47%.
get_vitals_summary
Returns a combined crash + ANR summary aggregated per version code, with averages over
the period and exceedsCrashThreshold / exceedsAnrThreshold flags. The latest version
is highlighted as latestVersionSummary.
get_wakelock_rate
Returns daily stuckBackgroundWakelockRate and distinctUsers per version code.
Relevant for 2026 Google Play battery health enforcement — apps with an excessive
proportion of sessions holding a partial wake lock for more than 1 hour in the background
may be penalized.
get_wakeup_rate
Returns daily excessiveWakeupRate and distinctUsers per version code.
Relevant for 2026 Google Play battery health enforcement — apps that wake the CPU too
frequently (above platform thresholds) may be penalized.
Troubleshooting
403 Forbidden on Vitals tools
This error has two common causes — check both:
1. Google Play Developer Reporting API not enabled
Enable it in your Google Cloud project: console.cloud.google.com/apis/library/playdeveloperreporting.googleapis.com
2. Service account lacks per-app Reporting API access
- Play Console → Setup → API access → find the service account → Manage Play Console permissions.
- Under App permissions, select the app and enable View app information and download bulk reports (read-only).
- Save and wait a few minutes for the change to propagate.
404 Package not found
The service account must be linked to the same Google Play Console account that owns the app. Go to Play Console → Setup → API access and verify the service account is listed and has been invited.
Marketplaces
License
MIT
來源:README.md,提交 9003e63
工具
0版本歷史
1- v0.5.0最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分