Google Play MCP tools

Every gps operation is registered as an MCP tool with the same name and argument schema. The same name works with gps call, the local gps-mcp server, the hosted MCP, and POST /v1/ops/{name}.

Discovery tools

Tool	Description
`gps_search_capabilities`	Search operations by `query` (matches name, group, and summary)
`gps_list_capabilities`	List every operation with its group, summary, and `write` flag
`gps_list_apps`	Hosted: apps the connected service account can use. Local: apps in the local registry
`gps_whoami`	Service-account email and read-only mode

On the CLI: gps search rollout, gps capabilities --json, and gps ops [query].

Operation groups

Group	Ops	Covers	Hosted
`reviews`	3	List, get, reply	All
`tracks`	8	Tracks, releases, lifecycle, promote, rollout, halt	All
`testers`	2	Track testers	All
`listings`	9	Localized listings and images	All but `gps_upload_image`
`monetization`	50	Subscriptions, base plans, offers, one-time products, purchase options, legacy IAPs, price conversion	All
`purchases`	10	Product and subscription purchases, voided purchases	All
`orders`	6	Orders, refunds, external transactions	All
`users`	7	Play Console users and app-level grants	All
`artifacts`	18	APKs, bundles, app details, country availability, generated APKs, system APK variants	Reads and non-file writes
`compliance`	9	Data safety, app recovery, device tier configs	All
`deploy`	1	`gps_deploy_app`	CLI only
`accounts`	6	Local multi-key config	CLI only
`meta`	1	`gps_whoami`	All

Full catalog with arguments: operations reference.

CLI-only operations

These read or write local files or local config, so the hosted server does not offer them:

Operation	Reason
`gps_deploy_app`, `gps_upload_bundle`, `gps_upload_apk`	Local build file
`gps_upload_image`	Local image
`gps_upload_deobfuscation_file`, `gps_upload_expansion_file`	Local file
`gps_upload_internal_sharing`	Local build file
`gps_download_generated_apk`, `gps_download_system_apk_variant`	Writes a local file
`gps_list_accounts`, `gps_list_apps` (local), `gps_register_account`, `gps_register_app`, `gps_unregister_app`, `gps_set_default_account`	Local config

Local vs hosted

	Local `gps-mcp`	Hosted
Credentials	`--credentials`, env vars, or config accounts	Your Appeeky connection
`account` argument	Optional on every tool	Not present
`gps_list_apps`	Local app registry	Apps seen on your Appeeky connection
Writes	On unless `--read-only`	Hidden unless `X-GPS-Allow-Writes: true`
File operations	Yes	No

Locally, if a packageName is registered under exactly one account, the account argument can be omitted.

Example calls

{ "name": "gps_list_tracks", "arguments": { "packageName": "com.example.app" } }

{
  "name": "gps_list_reviews",
  "arguments": { "packageName": "com.example.app", "maxResults": 20, "translationLanguage": "en" }
}

{
  "name": "gps_update_rollout",
  "arguments": { "packageName": "com.example.app", "track": "production", "userFraction": 0.2 }
}

CLI equivalent:

gps --confirm call gps_update_rollout '{"packageName":"com.example.app","track":"production","userFraction":0.2}'

Tool results are JSON text. Errors return { "error": "<message>" } with isError: true.

Overview

Google Play CLI

App Store Connect CLI

Discovery tools

Operation groups

CLI-only operations

Local vs hosted

Example calls

​Discovery tools

​Operation groups

​CLI-only operations

​Local vs hosted

​Example calls

Discovery tools

Operation groups

CLI-only operations

Local vs hosted

Example calls