Google Play CLI
Releases, staged rollouts, listings, reviews, testers, subscriptions, purchases, and orders.
App Store Connect CLI
Versions, App Review, TestFlight, reviews, reports, and every App Store Connect API operation.
Hosted or local
Use hosted when an agent or script should work on stores you already connected in Appeeky, without copying keys around. Use local for CI pipelines, uploads, and when you want the store key to stay with you.
How hosted auth works
- You authenticate with your Appeeky API key, as
Authorization: Bearer <key>orX-API-Key: <key>. - Your service-account key or
.p8key never leaves Appeeky. The hosted server only receives a short-lived Google token or a signed App Store Connect token for the request. - The store connection is the one in Settings → Data sources on appeeky.com. See Google Play Connect and App Store Connect.
Read-only by default
Hosted servers hide every operation that changes your store account until the request carries a write header:
Without it, write tools are not listed over MCP, and REST calls to them return
403 WRITES_DISABLED. Add the header only to clients you trust to publish, and keep a separate read-only config for everyday analysis.
Credits
Each hosted tool call orPOST /v1/ops/{name} is one metered Appeeky API call and draws from your API credits.
These are free:
- MCP
initializeandtools/list - Discovery that never reaches the store:
gps_search_capabilities,appstore_search_operations,appstore_describe_operation,GET /v1/ops - Calls rejected for invalid arguments (they are validated before Appeeky opens a store session)
Quick start
- Google Play (hosted)
- App Store Connect (hosted)
- Local CLIs
Next
Google Play hosted MCP
Connect an agent to Play Console with your Appeeky key.
App Store Connect hosted MCP
Connect an agent to App Store Connect with your Appeeky key.

