App Store & Google Play

What App Store & Google Play does

The App Store & Google Play MCP server gives an MCP client a common read-only interface for App Store Connect and Google Play. It is intended for developers managing applications on both platforms and needing one place to inspect app availability, release progress, and recent reviews.

The server does not submit builds, edit metadata, publish releases, or reply to reviews. Its tools are marked as read-only. Results retain store-specific details while also providing normalized fields where the two platforms describe similar states differently.

How it works

The server connects to App Store Connect with an Apple API key and to Google Play with a service account. Either store can be configured independently. Calls can target one application or sweep the configured portfolio when no application identifier is supplied.

Release data is mapped to shared states such as live, in_review, rolling_out, halted, draft, and rejected. The original platform state remains available as rawState. For reviews, the server combines results from both stores and sorts them together, but preserves fields only supplied by each platform. For example, App Store reviews may include territory, while Google Play reviews may include language, device, and app version.

Failures from one store or application are collected rather than necessarily preventing other results from returning. Responses identify unavailable sources so an incomplete result is distinguishable from an empty result.

Setup and configuration

The App Store & Google Play MCP server runs through npx and uses a standard MCP stdio configuration. Apple access requires ASC_KEY_ID, ASC_ISSUER_ID, and either ASC_KEY_PATH or ASC_PRIVATE_KEY. The key is created in App Store Connect under Users and Access, Integrations, and App Store Connect API.

Google Play access requires either PLAY_SERVICE_ACCOUNT_PATH or PLAY_SERVICE_ACCOUNT_JSON, plus PLAY_PACKAGES. The service account needs access in Play Console, and its Google Cloud project must have the Android Publisher API enabled. PLAY_PACKAGES is necessary because Google Play does not provide an endpoint for listing all applications owned by a developer.

Run npx -y appstore-play-mcp --demo to use fixture data without store credentials. The package is also listed in the MCP Registry, and the README provides configuration examples for MCP clients and Claude Code.

Tools and capabilities

• stores_health reports which stores are configured and whether authentication works.
• list_apps returns reachable applications from both stores in one list.
• get_app retrieves an application by App Store identifier, Google Play package name, or bundle identifier.
• get_releases shows live, review, draft, halted, rejected, and rollout-related states for one app or the full portfolio.
• get_reviews merges recent reviews from both stores. Use maxRating: 2 to focus on low-rated feedback.

Limitations and notes

Google Play review history generally covers about a week and is available only for applications that have reviews. App Store reviews are fetched per territory and may lag the public store page. Google Play track reads use a temporary edit that is deleted after the request; no edit is committed to the application.

The server cannot discover Google Play applications automatically, so package names must be declared. Authentication tokens are cached and refreshed before expiration. If one configured store is unavailable, the response can still include data from the other store along with an explanation of the partial result.