
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 分