Storepilot MCP

StorePilot

One MCP server for a whole app portfolio, across Google Play and the App Store.

Ask your assistant:

"Which of my apps has a crash rate above Google's threshold?"

"How much did the portfolio earn last month, per app?"

"Show me every app on both stores: version, rating, installs, revenue, crashes."

"The German description drifted between the two stores — what's different?"

"Ship 3.2.1 to the Play internal track and TestFlight."

Each question above is one tool call covering every app you own, because the tools are portfolio-shaped rather than endpoint-shaped. The last one is two, on purpose: writes preview first and wait for a human.

You need your own developer accounts — a Google Play service account, an App Store Connect API key, or both. StorePilot reads your accounts; it does not scrape public store listings.

Status: early. The read tools have run against real accounts on both

stores; the money and crash-threshold paths have not returned real data yet,

and no write has ever executed against a store. Read

Status and honest limits before trusting a number.

---

What is actually different

Both stores, one tool set. Google Play via the Android Publisher API, the Play Developer Reporting API and the private Cloud Storage reports bucket; the App Store via App Store Connect. 34 tools total, named consistently.

Installs and earnings, which most tooling cannot reach. Play installs, ratings and earnings have no REST API. They exist only as UTF-16 CSVs in a private Cloud Storage bucket, so most tooling skips them and "how much did this app earn?" simply cannot be answered. StorePilot reads that bucket, resolves CSV columns by name rather than position, and reports earnings per currency without ever summing across currencies. (This path is implemented and fixture-tested but has not yet read a real report — see Status.)

Portfolio-first. portfolio_overview renders every app on both stores in one table. play_portfolio_health scans an entire Play account. Neither takes a package name. Built for indie devs, app factories and agencies.

Cross-store tools. parity_check finds listing and version drift between the two stores. compare_reviews puts both stores' reviews side by side. release_both ships one version to both. metadata_pull / metadata_push use fastlane's own directory layout, so adopting StorePilot never means abandoning fastlane.

Writes are gated. Every write previews first and returns a confirmation token that is HMAC-keyed to the exact operation, single-use, and expires in 10 minutes. Production releases are forced into a staged rollout capped at 20%.

`setup_doctor`. Credential setup here is a multi-step Google Cloud + Play Console + App Store Connect maze with several silent failure modes. One tool checks every step and prints the exact fix.

---

Install

Requires Python 3.11+.

uvx storepilot          # no install; uv fetches it per run

or install it:

pipx install storepilot   # or: pip install storepilot

Either way you get a storepilot binary. Every client config below wants its absolute path — which storepilot prints it.

Claude Code

claude mcp add storepilot -- storepilot

Claude Desktop / any MCP client

claude_desktop_config.json:

{

"mcpServers": { "storepilot": { "command": "/absolute/path/to/storepilot", "env": { "STOREPILOT_GOOGLE_CREDENTIALS": "/path/to/service-account.json", "STOREPILOT_GOOGLE_REPORTS_BUCKET": "pubsite_prod_rev_0123456789", "STOREPILOT_ASC_KEY_PATH": "/path/to/AuthKey_XXXXXXXXXX.p8", "STOREPILOT_ASC_KEY_ID": "XXXXXXXXXX", "STOREPILOT_ASC_ISSUER_ID": "00000000-0000-0000-0000-000000000000", "STOREPILOT_ASC_VENDOR_NUMBER": "80000000" } } } }

Cursor

Settings → MCP → Add new MCP server, or add to ~/.cursor/mcp.json:

{

"mcpServers": { "storepilot": { "command": "/absolute/path/to/storepilot", "env": { "STOREPILOT_ASC_KEY_PATH": "/path/to/AuthKey_XXXXXXXXXX.p8" } } } }

Codex CLI

Add to ~/.codex/config.toml:

[mcp_servers.storepilot]

command = "/absolute/path/to/storepilot" env = { STOREPILOT_ASC_KEY_PATH = "/path/to/AuthKey_XXXXXXXXXX.p8" }

Configure only the store you use. Each adapter registers its tools independently, and the cross-store tools register as soon as either store is configured. See .env.example for every variable the code reads.

A .env file also works, but it is read from the process working directory — which is whatever directory your MCP client happened to launch the server from, not the repo. Use it when you run storepilot yourself from the checkout; use the client's env block otherwise.

Credentials are read from the environment and never written anywhere by StorePilot. Keep the service account JSON and the .p8 outside the repo, and chmod 600 both — they are private keys.

---

Start with setup_doctor

Do not start by calling a data tool and guessing why it returned nothing. Ask your assistant to run setup_doctor first. It checks each credential step independently, so one failure never hides the rest, and every failure carries its own fix.

With nothing configured yet:

StorePilot setup check

============================================================

-- Google Play ---------------------------------------------- [skip] Google Play: not configured Fix: Set STOREPILOT_GOOGLE_CREDENTIALS to the path of a service account JSON key. Full setup: create a Google Cloud project, enable the Android Publisher and Play Developer Reporting APIs, create a service account, download its JSON key, then invite the service account email in Play Console -> Users and permissions. Docs: https://developers.google.com/android-publisher/getting_started

-- App Store Connect ---------------------------------------- [fail] ASC credentials: App Store Connect is not configured: STOREPILOT_ASC_KEY_PATH, STOREPILOT_ASC_KEY_ID, STOREPILOT_ASC_ISSUER_ID unset. Fix: In App Store Connect go to Users and Access -> Integrations -> App Store Connect API, create a team key with the Admin or App Manager role, and download the .p8 file (Apple lets you download it exactly once). Then set STOREPILOT_ASC_KEY_PATH to that file, STOREPILOT_ASC_KEY_ID to the Key ID column, and STOREPILOT_ASC_ISSUER_ID to the Issuer ID shown above the key table. Sales reports additionally need STOREPILOT_ASC_VENDOR_NUMBER from Payments and Financial Reports. Docs: https://developer.apple.com/documentation/appstoreconnectapi/creating-api-keys-for-app-store-connect-api [skip] ASC token: cannot test until the credentials load Fix: Fix the step above, then re-run setup_doctor. [skip] ASC API reachable: cannot test until the credentials load Fix: Fix the step above, then re-run setup_doctor. [skip] ASC sales access: cannot test until the credentials load Fix: Fix the step above, then re-run setup_doctor.

============================================================ Summary: 1 fail, 4 skip Resolve the [fail] items above, then run setup_doctor again.

It also catches the failure that looks like success: without the Reply to reviews permission, Play's reviews API returns HTTP 200 and an empty list rather than an error, so "this app has no reviews" and "you lack a permission" are the same response. setup_doctor reports that ambiguity as its own diagnosis instead of guessing.

Full walkthrough for both stores: [docs/SETUP.md](docs/SETUP.md).

---

Tools

34 tools. Full arguments, return shapes and per-tool limitations in [docs/TOOLS.md](docs/TOOLS.md).

Google Play — read

Google Play — write (all gated)

App Store Connect

Cross-store

Plus setup_doctor.

Nothing in either API says a Play package and an Apple ID are the same product, so the pairing lives in ~/.storepilot/apps.toml. Run suggest_app_pairs, then pair_apps for the proposals you agree with. A proposal is inert until written — a wrong pair would attribute one app's revenue, reviews and crash rate to another, and nothing downstream would look wrong.

---

The safety model

Every write is two calls. The first returns a preview and a token; the second carries that token back.

The preview is the actual safety mechanism: it renders into the chat, where a human can read "that is the wrong app" or "that is the production track". Play previews are not estimates — the operation runs for real inside a throwaway Play edit that is validated and then deleted, so the preview reports the version code Google actually assigned and any error Google would actually raise.

The token exists only to prevent drift between the preview and the confirmation. It is an HMAC over a canonical fingerprint of the operation, keyed with a per-install secret kept out of tool output, single-use, and valid for 10 minutes. A plain content hash would be computable by the model itself, letting it self-confirm without ever rendering the