Google Play MCP server: reviews, vitals and products in Claude, Codex or Cursor
Google Play reaches Claude, Codex or Cursor through the Agent Planners MCP endpoint with 11 reads and 1 write. The one write, a reply to a review, is held for a person on every key mode. No release, price or listing tool exists. Firebase and Google Play are in Google's verification review: today only pilot workspaces can connect them, and every other workspace sees the card marked "In review". Everything described here is built; it opens to every workspace once Google verifies the permissions.
What this setup adds
| Calling Google's APIs yourself | Agent Planners MCP | |
|---|---|---|
| Sign-in | A service account or OAuth client, two APIs | Google sign-in once on the Google Play card |
| Reviews | Reviewer names and text as Google sends them | Names masked, emails and phones removed, text marked as untrusted data |
| Vitals | Metric-set queries, freshness and time zones to handle | Daily values ending at Google's latest finished day, in its Los Angeles calendar days |
| Changes | Whatever you send | Only a review reply, held for a person; releases, prices and listings are not built |
How to configure it
- 1Connect Google Play (pilot workspaces while Google reviews the permissions) on its card on Integrations.
- 2Create a key in API & MCP:
tools:readfor reading, addtools:writefor changes. To keep a key to Google Play, choose Only these platforms → Google Play. - 3Add the server to your client with one of the snippets below, run
describe_permissions, thengoogle_play__list_apps.
# Claude Code
claude mcp add --transport http agent-planners https://www.agentplanners.com/api/mcp \
--header "Authorization: Bearer $AGENTPLANNERS_API_KEY"
# Codex (signs in with OAuth in the browser)
codex mcp add agent-planners --url https://www.agentplanners.com/api/mcp
# Cursor (~/.cursor/mcp.json)
{ "mcpServers": { "agent-planners": { "url": "https://www.agentplanners.com/api/mcp", "headers": { "Authorization": "Bearer ${env:AGENTPLANNERS_API_KEY}" } } } }The Google Play tools
| Tool | Kind | What it does |
|---|---|---|
google_play__list_apps | Read | The Play apps this Google sign-in can see (Play Developer Reporting apps:search, every page): packageName, displayName, connected (each app is its own connection). |
google_play__get_app_details | Read | The selected app: package name, title (as set in Play Console), and how fresh its vitals are (the latest finished day per vitals metric set). |
google_play__list_reviews | Read | Recent user reviews of the selected app (androidpublisher reviews.list, every page — Google returns reviews created or changed in roughly the LAST WEEK only): reviewId, star rating, text, language, app version, Androi… |
google_play__get_review | Read | ONE review (androidpublisher reviews.get) with the developer's reply; same masking. |
google_play__query_crash_rate | Read | Crash rate (Play Developer Reporting crashRateMetricSet:query): crashRate, userPerceivedCrashRate, their 7-day / 28-day user-weighted averages, distinctUsers. |
google_play__query_anr_rate | Read | ANR ("app not responding") rate (anrRateMetricSet:query): anrRate, userPerceivedAnrRate, 7-day / 28-day averages, distinctUsers. |
google_play__query_error_counts | Read | Error report counts (errorCountMetricSet:query): errorReportCount and distinctUsers per day; dimensions? may add reportType (CRASH | ANR), versionCode, apiLevel, deviceModel. |
google_play__list_in_app_products | Read | The app's one-time products (androidpublisher monetization.onetimeproducts.list, every page): productId, listings (title per language), purchase options with their state. |
google_play__list_subscriptions | Read | The app's subscriptions (androidpublisher monetization.subscriptions.list, every page): productId, listings, base plans (id, state, auto-renewing / prepaid). |
google_play__list_voided_purchases | Read | Purchases that were refunded, cancelled or charged back (androidpublisher purchases.voidedpurchases.list) in the last ≤ 30 days (Google's limit): counts by reason (remorse, not received, defective, accidental, fraud …… |
google_play__get_track_status | Read | What is on each release track (androidpublisher applications.tracks.releases.list — a plain read, no edit is opened): per track (production, beta, alpha, internal by default) each release's name, lifecycle state (DRAF… |
google_play__reply_to_review | Write — always a person | Post or replace the developer reply to ONE review (androidpublisher reviews.reply): { accountId?, reviewId, replyText (plain text, ≤ 350 characters — longer is refused, never cut; HTML is refused), dryRun? }. |
What waits for a person, whatever the key allows
- A reply to a review — public on the Play Store. A dry run returns the reply without posting.
- Not reachable at all: releases, tracks, rollouts, prices, products, subscriptions, listings, purchases and uploads.
Frequently asked questions
- Can an MCP client reply to Google Play reviews?
- It can draft and ask; a person approves each reply before it is posted, on every key mode.
- How far back do reviews go?
- Google's reviews API returns reviews created or changed in roughly the last week.