App Store and Google Play

App Store and Google Play MCP server

Read and answer your app's App Store and Google Play reviews from your AI assistant, and see what TestFlight testers sent you: screenshot feedback, and crashes with their logs. It works through App Store Connect and the Google Play Developer API. Two tools write: reply_app_store_review and reply_play_review publish a reply in the developer's name, visible to everyone, so send only text you have approved. Nothing here moves money.

You need credentials for each store you use, and one store is enough: for the App Store, an App Store Connect API key (its .p8 file, key id and issuer id); for Google Play, a Google Cloud service account with a JSON key, invited to your app in Play Console. Google's API returns only the last seven days of reviews.

What you can ask

• "What did people say about the last release, and which App Store reviews still have no reply?"
• "Show this week's Google Play reviews of com.example.app, translated into English, worst first."
• "What crashed for TestFlight testers on build 42?"
• "Draft replies to the App Store reviews from Germany that mention signing in." Then, once you have read them: "Send these."

Install

.%22%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22asc_issuer_id%22%2C%22description%22%3A%22Optional.%20For%20the%20App%20Store%3A%20the%20issuer%20id%20App%20Store%20Connect%20shows%20above%20your%20team%20keys.%22%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22asc_private_key_file%22%2C%22description%22%3A%22Optional.%20For%20the%20App%20Store%3A%20path%20of%20the%20.p8%20key%20file%20App%20Store%20Connect%20let%20you%20download.%22%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22play_service_account_file%22%2C%22description%22%3A%22Optional.%20For%20Google%20Play%3A%20path%20of%20the%20service%20account's%20JSON%20key.%22%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22play_packages%22%2C%22description%22%3A%22Optional.%20For%20Google%20Play%3A%20the%20package%20names%20to%20answer%20for%2C%20comma-separated%2C%20e.g.%20com.example.app.%22%7D%5D&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22%40foreverworks%2Fmcp-app-stores%22%5D%2C%22env%22%3A%7B%22ASC_KEY_ID%22%3A%22%24%7Binput%3Aasc_key_id%7D%22%2C%22ASC_ISSUER_ID%22%3A%22%24%7Binput%3Aasc_issuer_id%7D%22%2C%22ASC_PRIVATE_KEY_FILE%22%3A%22%24%7Binput%3Aasc_private_key_file%7D%22%2C%22PLAY_SERVICE_ACCOUNT_FILE%22%3A%22%24%7Binput%3Aplay_service_account_file%7D%22%2C%22PLAY_PACKAGES%22%3A%22%24%7Binput%3Aplay_packages%7D%22%7D%7D)

With Claude Code:

claude mcp add app-stores -- npx -y @foreverworks/mcp-app-stores

Claude Desktop (Settings, Developer, Edit Config) and most other clients read the same command as JSON:

{

"mcpServers": { "app-stores": { "command": "npx", "args": ["-y", "@foreverworks/mcp-app-stores"] } } }

Each runs the published package on Node 22.19 or newer. VS Code and the Claude Desktop bundle ask for each setting as they add the server; leave an optional one empty. Cursor reads each from your environment instead (${env:ASC_KEY_ID} and so on), so set them before you start Cursor. Every setting is optional; Configuration says which ones you need for which tools.

From a clone

git clone https://github.com/foreverworks/mcps.git && cd mcps

npm ci && npm run build claude mcp add app-stores -- node "$PWD/servers/app-stores/dist/index.js"

In a JSON configuration, the command is node and its one argument the full path of servers/app-stores/dist/index.js. To share one running copy between several clients over HTTP, see docs/deploying.md.

The commands above configure no store. Add the variables of each store you use:

claude mcp add app-stores \

-e ASC_KEY_ID=ABCDE12345 -e ASC_ISSUER_ID=" " -e ASC_PRIVATE_KEY_FILE=" " \ -e PLAY_SERVICE_ACCOUNT_FILE=" " -e PLAY_PACKAGES=com.example.app \ -- npx -y @foreverworks/mcp-app-stores

Configuration

A store you leave out shows as configured: false in health, and its tools answer config. Credentials are read on the first call that needs them, so the server starts without any. The variables every server shares (transport, limits, what tools may do) are in docs/configuration.md.

Getting an App Store Connect API key

1. In App Store Connect, open Users and Access, then Integrations, App Store Connect API, Team Keys.
2. Generate a key with the access it needs and no more: Customer Support reads and answers reviews, Developer reads TestFlight feedback.
3. Download the .p8 file. App Store Connect offers it once: save it readable only by you (chmod 600), and point ASC_PRIVATE_KEY_FILE at it.
4. Copy the Key ID from the key's row into ASC_KEY_ID, and the Issuer ID shown above the list into ASC_ISSUER_ID.

A team key does not expire; revoke it on the same page once it is unused.

Getting a Google Play service account

1. In the Google Cloud console, in any project, open IAM and Admin, Service accounts, and Create service account. It needs no roles in the project.
2. On the new account, open Keys, Add key, Create new key, JSON. Save the file readable only by you (chmod 600) and point PLAY_SERVICE_ACCOUNT_FILE at it. If your organisation forbids service account keys (iam.disableServiceAccountKeyCreation), lift that policy for the project while you make the key.
3. In Play Console, open Users and permissions, Invite new users, and enter the service account's e-mail address (client_email in the JSON file). Give it two permissions on the app: View app information (to read reviews) and Reply to reviews.
4. Set PLAY_PACKAGES to the app's package name (several, comma-separated).

First run

1. Ask your assistant to run the app stores' health check. For each store it says whether the credentials work, with the apps the key sees (bundle ids and Apple ids) and each Play package with one review read.
2. Then read before you write: ask for draft replies, and send only those you approved.

Tools

read changes nothing in either store (a crash log is saved to the server's outbox); write publishes a reply under a review.

Troubleshooting

`config`: "App Store Connect is not configured" or "Google Play is not configured". The message names the missing variables. Any other config message names a value the store did not issue: a key id that is not 10 letters and digits, an issuer id that is not a UUID, a .p8 that is not an EC P-256 key, or a JSON file that is not a service account's key.

`auth`. The store refused the credentials: the key was revoked or the service account deleted. Check it in App Store Connect (Users and Access, Integrations) or the service account's Google Cloud project, and replace the file.

`forbidden` from the App Store. The key lacks the role: reviews need Customer Support, TestFlight feedback needs Developer.

`forbidden` from Google Play. The service account cannot act on that app: in Play Console, Users and permissions, give it View app information and Reply to reviews on the app. A newly invited account can take hours to reach the API. If the message says the Google Play Android Developer API is disabled, enable it in the service account's Google Cloud project.

`input`: "... already has a public reply". The review has a different reply, quoted in the message. Call again with replace: true only if you mean yours to take its place. Other input messages name the problem: a reply over the store's limit, or an app or package to name because there are several.

`not_found`. These credentials do not reach that id or app: health lists the apps and packages they do.

`outcome_unknown` after a reply. The connection dropped after the reply left, so it may already be public. List the review again (it shows its reply) before you send it again.

`rate_limited`. The store is throttling these credentials; wait a minute. `api` with status 0 means the store was unreachable; another status, that it failed: retry later. `drift` means the store's