# 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.

Source: https://elaichi.ai/connectors/googleplay/

## Facts

| | |
| --- | --- |
| Application | Google Play |
| Category | Analytics |
| AI tools | 175 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Google Play is connected

- 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.

## Connect Google Play in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Google Play.
2. Optionally set Share with, then press Connect.
3. Supply your own Google Play app, then approve. Google Play needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Google Play tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Google Play MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Google Play MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Google Play tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Google Play through Elaichi

### Catch an ANR or memory spike early

Mobile engineering. 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.

### See what changed in the last release

Release management. 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.

### Get a plain read on Google Play anomalies

Product. 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.

### Pull memory numbers for the build under test

QA. 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.

### Roll out a recovery to affected users

Support. 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.

### Keep app signing on schedule

Security. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Google Play connection?

Yes. One person connects Google Play in Elaichi and shares the connection with a team, and nobody else ever handles the client ID, secret, or any Google credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Google Play call.

### 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.

## All 175 Google Play tools

Every tool below is callable through https://api.elaichi.ai/mcp once Google Play is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Google Play anomalies** (List). Lists anomalies in any of the datasets. The connector follows nextPageToken through all pages. Required: package_name.
- **Create anon rss and swap memory usage metric set query** (Search). Queries the metrics in the metric set. Required: package_name.
- **List all anon rss and swap memory usage metric set queries** (List). Queries the metrics in the metric set and returns the rows. The connector follows nextPageToken through all pages: pass the same body (timelineSpec, metrics, dimensions, filter) with next_cursor to get the next page; use limit (max 10000) for the page size. Required: package_name.
- **List all Google Play anon rss and swap memory usage metric sets** (List). Describes the properties of the metric set. Required: package_name.
- **Create a Google Play anr rate metric set query** (Create). Queries the metrics in the metric set. Required: package_name.
- **List all Google Play anr rate metric set queries** (List). Queries the metrics in the metric set and returns the rows. The connector follows nextPageToken through all pages: pass the same body (timelineSpec, metrics, dimensions, filter) with next_cursor to get the next page; use limit (max 10000) for the page size. Required: package_name.
- **List all Google Play anr rate metric sets** (List). Describes the properties of the metric set. Required: package_name.
- **List all Google Play app recoveries** (List). List all app recovery action resources associated with a particular package name and app version. Required: package_name.
- **Create a Google Play app recovery** (Create). Create an app recovery action with recovery status as DRAFT. Note that this action does not execute the recovery action. Required: package_name.
- **Create a Google Play app recovery cancellation** (Create). Cancel an already executing app recovery action. Note that this action changes status of the recovery action to CANCELED. Required: package_name, app_recovery_id.
- **Create a Google Play app recovery deployment** (Create). Deploy an already created app recovery action with recovery status DRAFT. Note that this action activates the recovery action for all targeted users and changes its status to ACTIVE. Required: package_name, app_recovery_id.
- **Create a Google Play app recovery targeting** (Create). Incrementally update targeting for a recovery action. Note that only the criteria selected during the creation of recovery action can be expanded. Required: package_name, app_recovery_id.
- **List all Google Play app release filter options** (List). Describes filtering options for releases. Required: package_name.
- **Create a Google Play app signing enrollment** (Create). Enrolls an app in Play App Signing using a self-hosted Google Cloud KMS key. Warning: Do not use this method for standard Play App Signing enrollment. * Standard enrollment with Google-generated or Google-managed keys cannot be done via API. * This advanced API is strictly for enterprise organizations with mandatory compliance, regulatory, or policy requirements to retain key c Required: package_name.
- **Create a Google Play app signing key rotation** (Create). Rotates an app's signing key to a new self-hosted Google Cloud KMS key. Warning: This method only applies to apps enrolled with self-hosted Cloud KMS keys. For apps using standard Google-managed Play App Signing, key rotation requests must be initiated through the Google Play Console UI. See Help Center: Required: package_name.
- **Create a Google Play app store app apk** (Create). Upload an APK file for the hosted app. Returns an ID to track this APK. The request body is the raw file (sent with uploadType=media). Required: app_store_package_name, package_name.
- **Create a Google Play app store app image** (Create). Upload a screenshot or app icon for the hosted app. Returns an ID to track the image. The request body is the raw PNG file (sent with uploadType=media and Content-Type image/png). Required: app_store_package_name, package_name.
- **Create a Google Play app store app publish status** (Create). Updates the publish status of an app store hosted app. The default state after calling UpdateAppStoreHostedApp is PUBLISHED. It is not necessary to call this RPC explicitly to set an app to PUBLISHED. Required: app_store_package_name, package_name.
- **Create a Google Play app store app update** (Create). Updates details for an app hosted on an app store. Use this to provide details for a new app, or to update details for an existing app. The update will be sent for review immediately after creation. Required: app_store_package_name.
- **Create a Google Play app store app** (Create). Creates an app store hosted app. This must be called before any other RPCs for this hosted app. Required: app_store_package_name.
- **Get single Google Play app store recent app view by ID** (Get). Returns metadata about a recently updated app. Required: app_store_package_name, id.
- **List all Google Play app store recent update events** (List). Lists update events for eligible apps in the given time range. The connector follows nextPageToken through all pages. Required: app_store_package_name.
- **List all Google Play apps** (List). Searches for Apps accessible by the user. The connector follows nextPageToken through all pages.
- **Create a Google Play bitmap memory usage metric set query** (Create). Queries the metrics in the metric set. Required: package_name.
- **List all Google Play bitmap memory usage metric set queries** (List). Queries the metrics in the metric set and returns the rows. The connector follows nextPageToken through all pages: pass the same body (timelineSpec, metrics, dimensions, filter) with next_cursor to get the next page; use limit (max 10000) for the page size. Required: package_name.
- **List all Google Play bitmap memory usage metric sets** (List). Describes the properties of the metric set. Required: package_name.
- **Create a Google Play crash rate metric set query** (Create). Queries the metrics in the metric set. Required: package_name.
- **List all Google Play crash rate metric set queries** (List). Queries the metrics in the metric set and returns the rows. The connector follows nextPageToken through all pages: pass the same body (timelineSpec, metrics, dimensions, filter) with next_cursor to get the next page; use limit (max 10000) for the page size. Required: package_name.
- **List all Google Play crash rate metric sets** (List). Describes the properties of the metric set. Required: package_name.
- **Create a Google Play data safety** (Create). Writes the Safety Labels declaration of an app. Required: package_name.
- **List all Google Play device tier configs** (List). Returns created device tier configs, ordered by descending creation time. The connector follows nextPageToken through all pages. Required: package_name.
- **Create a Google Play device tier config** (Create). Creates a new device tier config for an app. Required: package_name.
- **Get single Google Play device tier config by ID** (Get). Returns a particular device tier config. Required: package_name, id.
- **Create a Google Play edit apk** (Create). Uploads an APK and adds to the current edit. The request body is the raw file (sent with uploadType=media). Required: package_name, edit_id.
- **List all Google Play edit apks** (List). Lists all current APKs of the app and edit. Required: package_name, edit_id.
- **List all Google Play edit bundles** (List). Lists all current Android App Bundles of the app and edit. Required: package_name, edit_id.
- **Create a Google Play edit bundle** (Create). Uploads a new Android App Bundle to this edit. If you are using the Google API client libraries, please increase the timeout of the http request before calling this endpoint (a timeout of 2 minutes is recommended). See [Timeouts and Errors]( for an example in java. The request body is the raw file (sent with uploadType=media). Required: package_name, edit_id.
- **Create a Google Play edit commit** (Create). Commits an app edit. Required: package_name, edit_id.
- **Get single Google Play edit country availability by ID** (Get). Gets country availability. Required: package_name, edit_id, id.
- **Create a Google Play edit deobfuscation file** (Create). Uploads a new deobfuscation file and attaches to the specified APK. The request body is the raw file (sent with uploadType=media). Required: package_name, edit_id, apk_version_code, deobfuscation_file_type.
- **List all Google Play edit details** (List). Gets details of an app. Required: package_name, edit_id.
- **Google Play edit details bulk update** (Update). Patches details of an app. Required: package_name, edit_id.
- **Create a Google Play edit expansion file upload** (Create). Uploads a new expansion file and attaches to the specified APK. The request body is the raw file (sent with uploadType=media). Required: package_name, edit_id, apk_version_code, expansion_file_type.
- **Update a Google Play edit expansion file by ID** (Update). Updates the APK's expansion file configuration to reference another APK's expansion file. To add a new expansion file use the Upload method. Required: package_name, edit_id, apk_version_code, id.
- **Google Play edit expansion files partial update** (Update). Patches the APK's expansion file configuration to reference another APK's expansion file. To add a new expansion file use the Upload method. Required: package_name, edit_id, apk_version_code, expansion_file_type_id.
- **Get single Google Play edit expansion file by ID** (Get). Fetches the expansion file configuration for the specified APK. Required: package_name, edit_id, apk_version_code, id.
- **Create a Google Play edit externally hosted apk** (Create). Creates a new APK without uploading the APK itself to Google Play, instead hosting the APK at a specified URL. This function is only available to organizations using Managed Play whose application is configured to restrict distribution to the organizations. Required: package_name, edit_id.
- **Create a Google Play edit image** (Create). Uploads an image of the specified language and image type, and adds to the edit. The request body is the raw PNG file (sent with uploadType=media and Content-Type image/png). Required: package_name, edit_id, language, image_type.
- **Google Play edit images bulk delete** (Delete). Deletes all images for the specified language and image type. Returns an empty response if no images are found. Required: package_name, edit_id, language, image_type.
- **List all Google Play edit images** (List). Lists all images. The response may be empty. Required: package_name, edit_id, language, image_type.
- ...and 125 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
