Google Play MCP connector
The Google Play connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent read your Google Play apps, anomalies, ANR rates, memory metrics and app recoveries, with every call running as the signed-in person and logged.
- Connects over OAuth
- Free 14-day trial
- No credit card
Show me any Google Play anomalies flagged this week.
Working in Google Play with Elaichi
-
List all Google Play anomalies
-
Create anon rss and swap memory usage metric set query
-
List all anon rss and swap memory usage metric set queries
How to connect Google Play to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Google Play MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Google Play MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Google Play MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Google Play MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Google Play MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Google Play to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Google Play through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Google Play is logged.
-
Mobile engineering
Catch an ANR or memory spike early
Ask for the ANR rate and memory usage metrics for a build straight after it ships, and get the numbers in plain language before the reviews start coming in.
-
Release management
See what changed in the last release
Pull the recent update events and release filter options for an app so the release notes and the handover are written from what actually went out.
-
Product
Get a plain read on Google Play anomalies
List the anomalies Google Play has flagged across your apps and ask which ones are new since the last check-in, without opening the console.
-
QA
Pull memory numbers for the build under test
Run a memory usage query for the version in testing and compare it with the previous one, so a regression shows up in the test report instead of in production.
-
Support
Roll out a recovery to affected users
When a bad build hits a group of users, set up an app recovery, target it, deploy it, and cancel it if it turns out to be the wrong call.
-
Security
Keep app signing on schedule
Enroll an app in Play app signing and start a signing key rotation when policy says it is due, with the request logged under the person who made it.
Try asking
- “Show me any Google Play anomalies flagged this week.”
- “What is the ANR rate for our app since the latest release?”
- “List our Google Play apps and their most recent update events.”
What connecting Google Play gets you
6 screens from Elaichi, each doing one job for your Google Play account.
Ask Elaichi to work across your apps.
Show me any Google Play anomalies flagged this week.
What is the ANR rate for our app since the latest release?
List our Google Play apps and their most recent update events.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Google Play in plain language.
Anomalies, ANR rates and memory metrics answered from live Google Play records.
Copy the endpoint
AI apps
Google Play in every client, one endpoint.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Tool catalog
175 Google Play tools, with no custom code.
Apps, anomalies, metric sets, app recoveries and app signing, ready the moment you connect.
Toolboxes
Each team gets its own Google Play toolbox.
Release gets updates and recoveries, QA gets metrics, Security gets signing, scoped per team.
Shared connections
Share Google Play without sharing a credential.
One person connects, teams work through it, and nobody else ever sees the secret.
Audit log
Know who did what in Google Play.
Every recovery, rotation and update is logged with who, when and which app.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Google Play digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch apps
Google Play
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Google Play
Queued
Workflows
A schedule runs the Google Play digest.
Anomalies are fetched, grouped and drafted into a digest a person approves before it posts.
Google Play health
Refreshed 4 minutes ago · every 15 minutes · from the apps collection
Apps
1,284 ↓ 12%
Anomalies
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Apps created
Last 14 days
By team
Share of activity
Mobile engineering 34%
Release 27%
QA 21%
Support 18%
Collections and dashboards
Google Play health, computed without a model.
Four metrics, a 14 day chart of anomalies, and a breakdown by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Google Play
All three can connect Google Play to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Google Play tools | Allow or restrict single Google Play tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Google Play call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Google Play tools for your AI agents
175 tools are ready to call through Elaichi's MCP endpoint the moment you connect Google Play, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Google Play to Claude?
First connect Google Play in Elaichi. Google Play needs an OAuth application you register inside Google Play yourself, so somebody brings its client ID and secret once, then signs in with their own Google account and approves access. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Google Play apps are available.
Does Google Play work with ChatGPT and Cursor as well as Claude?
Yes. Once Google Play is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Google Play once and every client picks it up.
What can an AI agent actually do with my Google Play data?
With Google Play connected, an agent can list your apps, show the anomalies Google Play has flagged, run ANR rate and memory usage queries for a version, read recent update events, and set up or cancel an app recovery. It can also start an app signing enrollment or key rotation and prepare an app store update. Short, concrete asks such as "ANR rate for the latest release" work better than long paragraphs.
Does connecting Google Play give the AI everything in my developer account?
No. Access to Google Play follows the person who signed in, so an agent only sees the apps and metrics that person's Google Play account can see. Elaichi can narrow that further with restrictions and roles, and it never widens it beyond what the person already has.
Can I stop an agent from deleting or changing things in Google Play?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Google Play anomalies and metrics while restricting app recovery deployments, signing key rotations, or publishing an app update. A restriction is set on a role or on one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Google Play connection when someone leaves?
Offboarding a person in Elaichi ends their access to Google Play through every client at once. If they connected a shared Google Play account, the connection keeps working for everyone else it was shared with. Disconnecting Google Play once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Google Play MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Google Play is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Google Play?
Yes. Both let Claude, ChatGPT or Cursor use Google Play. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Google Play call.
How is Elaichi different from Composio for Google Play?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Google Play: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Google Play in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot