Google Play Console MCP
Let your coding agent manage Play Console release tracks, tester groups, staged rollouts, and Android Vitals without clicking through the web UI.
Overview
Google Play Console MCP is an MCP server for the Launch phase that automates Google Play release tracks, tester management, rollouts, and Android Vitals via the Play Developer API.
What is this MCP server?
- Stdio MCP package (google-play-mcp on PyPI, v0.5.3) wired for Claude Desktop–style configs
- Covers Google Play release lifecycle: tracks, testers, rollout controls
- Surfaces Android Vitals so agents can reason about crashes and quality regressions
- Authenticates via GOOGLE_APPLICATION_CREDENTIALS service-account JSON
- Built for solo Android devs shipping indie apps through the official Play Developer API
- Package version 0.5.3 on PyPI (registryType pypi)
- Stdio transport with identifier google-play-mcp
- Requires GOOGLE_APPLICATION_CREDENTIALS for service account auth
Community signal: 4 GitHub stars.
What problem does it solve?
Solo Android builders waste hours in Play Console promoting builds, juggling testers, and checking vitals when they could be fixing the app.
Who is it for?
Indie developers who already ship to Google Play and want MCP-driven release and rollout checks alongside their agent workflow.
Skip if: Teams with no Android app, no Play Console API setup, or who only need one-off manual uploads without automation.
What do I get? / Deliverables
After you register the server and service account, your agent can run API-backed Play release and vitals tasks from your IDE instead of manual console work.
- MCP tools callable for Play release lifecycle and vitals workflows
- Repeatable agent-driven Play Console operations without manual UI steps
Recommended MCP Servers
Journey fit
Publishing and iterating on a live Android app on Google Play is a Launch-phase job: store presence, releases, and quality signals—not initial product build. ASO on Skillselion covers app-store operations; this MCP maps directly to Play Console lifecycle and vitals, which is post-build distribution and store health.
How it compares
Play Developer API MCP integration, not a generic Play Store listing or ASO copywriting skill.
Common Questions / FAQ
Who is Google Play Console MCP for?
Solo and small-team Android builders who use Claude Code, Cursor, or similar agents and already publish on Google Play with API credentials.
When should I use Google Play Console MCP?
Use it during Launch when you are managing tracks, testers, staged rollouts, or reviewing Android Vitals after you have a build ready to ship or update.
How do I add Google Play Console MCP to my agent?
Install the PyPI package google-play-mcp (stdio), set GOOGLE_APPLICATION_CREDENTIALS to your service account JSON path, and add the server block to your agent’s MCP config per the repo README.