Persyst connector
Google Play MCP connector: your app reviews, readable by the whole team
Support, product or leadership know what Android users are saying, with no Play Console access and no CSV export.
Updated on November 1, 2026
Your tools
- By the admin or by each member
- Rights per person, team or client
- Who read what, and when
Everyone’s AI
In short
- Persyst works without an MCP server to install: it is a remote MCP server shared by the team, with no developer tooling on anyone’s computer.
- Read-only: Persyst reads reviews and published replies. It replies to no review and changes nothing in the Play Console.
- Search by meaning: “login problems” also finds “can’t sign in” or “the app keeps logging me out”.
- Statistics computed over all imported reviews, by day, week, month, app, version, language or rating: not over a sample.
EXAMPLES
What your team can ask
Since version 4.2, what are Android users complaining about?
Two topics dominate the 61 one- and two-star reviews on 4.2: sync failing after the update (24 reviews, for example “my notes have been gone since yesterday”) and the new navigation bar (11 reviews). The version’s average rating drops from 4.3 to 3.6.
Sources consulted
- Google Play reviews · statistics by version
- Google Play reviews · search
How many negative reviews went unanswered this month?
38 one- and two-star reviews in October, 29 of them unanswered. The average reply delay is 52 hours, against 20 hours in September. The oldest unanswered ones date from October 3.
Sources consulted
- Google Play reviews · statistics
- Google Play reviews · filtered list
HOW IT WORKS
Google Play in your AI, in three steps
Connect Google Play
In Data sources, an administrator connects a Google account with access to the apps in the Play Console. Persyst only asks for read access. The Google Play guide covers each step.
Choose the apps and their history
In Apps, the administrator adds the relevant apps. Reviews from the last 7 days arrive right away. For the full history, they paste each app’s review reports address, copied from the Play Console.
Ask from the assistant
In Access management, the administrator opens the apps to support, product or leadership. Everyone asks in ChatGPT, Claude or Copilot: “what have users complained about since the last release?”, “which negative reviews are waiting for a reply?”. The history keeps track of who looked at which app, and when.
TOOLS
What your assistant can do
Google Play· 4 tools
Opened team by teamLists the Google Play apps open to the member, with their identifier and name.
list_play_appsLists reviews, newest first: rating, text, language, version, device and developer reply. Filters by period, rating, language, version or reply; 100 reviews per call.
list_play_reviewsFinds reviews about a topic, by meaning and by keywords, up to 50 results, most relevant first.
search_play_reviewsComputes review count, average rating, star distribution, reply rate and delay, grouped by day, week, month, app, version, language or rating.
get_play_review_stats
Rights and audit trail
Rights per person, team or client.
Then, inside the tool, only the items you open. The rest does not exist for the AI.
One-click revocation.
Removing a member cuts their access in every AI at once.
A history.
Who used which tool, and when.
Credentials that stay put.
They remain encrypted in Persyst, never in the assistants.
COMPARISON
Persyst or a Google Play MCP server?
| Criterion | Persyst | Community Google Play MCP server |
|---|---|---|
| Who authenticates | The company once, or each member with their own account. | Each member, with their own API key. |
| Installation | None: a remote MCP server, authorized from the assistant. | A server to install and maintain on every machine, or a third-party service you hand the key to. |
| Where credentials live | Encrypted in Persyst, never in the assistant. | In each member’s assistant configuration. |
| Scope | Per person, team or client, then per opened item. | Everything the key allows. |
| History | Who used which tool, and when, for the whole team. | None, or machine by machine. |
| When a member leaves | One-click revocation, in every AI. | A key to revoke at the vendor, machine by machine. |
What this connector does not do
- No writes: Persyst publishes no reply to reviews. The assistant can draft one, to publish in the Play Console.
- Reviews only: no installs, crashes, revenue or store listing.
- Google’s API only returns the last 7 days of reviews. The full history requires the Play Console review reports address, set per app.
- The latest hours of reviews may be missing: they are refreshed every 6 hours. The computed average can differ from the Play Store rating, which Google weights differently.
Questions
Frequently asked questions
Is there an official Google Play MCP server?
No. Community MCP servers exist, mostly to publish releases from a developer’s computer, with each user’s credentials. Persyst serves the teams that read reviews: an administrator connects the Play Console once and opens specific apps to each team.
Does each member need Play Console access?
No. A Google account with access to the apps in the Play Console is connected once. Members ask about the reviews of the apps open to them, with no Play Console invitation.
How do I get the full review history?
For each app, paste the Play Console review reports address (gs://pubsite_prod_…) into Persyst. The connected account needs the “Download bulk reports” permission. The full history is then imported, and read again every week.
Can the assistant reply to reviews for me?
It can draft a reply from the review and your guidelines, but not publish it. Publishing happens in the Play Console, by someone with access.
Does the data stay with Persyst?
Reviews are imported to Persyst’s servers, hosted in the European Union. The reviews read to answer are passed to the assistant of the person asking, like anything else they share with it.
