play-console-mcp

MCP server for the Google Play Console that exposes the official Google Play Developer API and Play Developer Reporting API as tools for AI agents.

Its focus is managing user feedback and Android app releases — reading and replying to Play Store reviews, inspecting release tracks, promoting a build from beta to production, steering a staged rollout, and checking crash/ANR vitals before and after a release.

What it deliberately does not do: no app bundle (AAB/APK) uploads, no store listing or metadata edits, no in-app product or subscription management, and no Android device management (that is the unrelated Android Management API). Writes are limited to review replies and release track updates.

Install

claude mcp add play-console -- npx -y @orellbuehler/play-console-mcp \
  --env GOOGLE_SERVICE_ACCOUNT_KEY_PATH=/path/to/service-account.json \
  --env GOOGLE_PLAY_PACKAGE_NAME=com.example.app

Related MCP server: Google Play Console

Getting a service account key

1. In the Google Play Console, go to Setup → API access.

2. Create a new Google Cloud project or link an existing one.

3. Under Service accounts, click Create new service account and follow the link to the Google Cloud console.

4. Create the service account, then create a JSON key for it and download the file.

5. Back in the Play Console, click Manage Play Console permissions for that service account and grant it access to your app(s) with at least:

   • View app information and download bulk reports (required by every tool)

   • Reply to reviews (for reply_to_review)

   • Release apps to testing tracks and/or Release to production (for promote_release, update_rollout, halt_rollout)

6. Point GOOGLE_SERVICE_ACCOUNT_KEY_PATH at the downloaded JSON file.

Permission changes can take a few minutes to propagate. Until they do, calls fail with The caller does not have permission.

Configuration

Usage with Claude Code

{
  "mcpServers": {
    "play-console": {
      "command": "npx",
      "args": ["-y", "@orellbuehler/play-console-mcp"],
      "env": {
        "GOOGLE_SERVICE_ACCOUNT_KEY_PATH": "/path/to/service-account.json",
        "GOOGLE_PLAY_PACKAGE_NAME": "com.example.app"
      }
    }
  }
}

Example prompts

• "What are people complaining about in this week's Play Store reviews?"

• "Reply to the 1-star review from Ada apologising for the crash and saying a fix ships this week."

• "Which tracks have releases right now, and what version code is in production?"

• "Promote the current beta release to production as a 10% staged rollout."

• "The crash rate spiked — halt the production rollout."

• "Compare the crash rate for version code 415 against 414 over the last two weeks."

• "Show me the top crash issues by affected users and the stack trace for the worst one."

Tools

Reviews

Releases

Every write tool accepts validate_only: true for a dry run — the change is validated against the API and then discarded instead of being committed.

Vitals

Notes & caveats

• Reviews are limited by Google, not by this server. The API only returns reviews created or modified in the last 7 days, only reviews that contain written text, and only for production releases. Replies are capped at 350 characters and the user is only notified about the first reply to a review.

• Quotas: review reads are limited to roughly 200 requests/hour and replies to 2,000/day per developer account.

• Release writes use the Play edits workflow. Each write tool opens an edit, applies the change, and commits it in a single call; failed calls delete the edit again. Promoting replaces the destination track's release list, which is what the Play Console does too.

• Vitals data lags. Android vitals metrics are aggregated daily in America/Los_Angeles and are typically about a day behind. Slices with too few users are omitted by Google.

• Ratings over time are not available through the Reporting API; per-review star ratings come from list_reviews.

Development

npm install
npm run build         # tsc -p tsconfig.build.json -> dist/
npm test              # vitest run
npm run lint          # eslint src
npm run typecheck     # tsc --noEmit
npm run format        # prettier --write .

Smoke-test the built server against a real app:

GOOGLE_SERVICE_ACCOUNT_KEY_PATH=/path/to/service-account.json \
GOOGLE_PLAY_PACKAGE_NAME=com.example.app \
npx @modelcontextprotocol/inspector node dist/index.js

CI / Releasing

CI runs format:check, lint, typecheck, test and build on Node 20 and 22. Publishing happens on GitHub release via npm trusted publishing (OIDC, no tokens):

npm version patch
git push --follow-tags
gh release create "v$(node -p "require('./package.json').version")" --generate-notes

License

MIT © Orell Bühler