In measured numbers
Every figure on this page is read from a code path, not written by hand — the same discipline the product applies to your own data.
What the tools return
| Tool | What it answers |
|---|---|
| list_apps | Which apps this account measures |
| get_keywords | Current rank per keyword and storefront, with measurement state |
| get_history | The stored series for a keyword, gaps included |
| get_rivals | The apps ranked above you, and their ratings |
| get_store_page | The current listing as the store serves it |
| get_reviews | Recent reviews, including the crash-shaped ones |
| get_charts | Top-chart positions for a category and storefront |
| get_ai_visibility | Whether assistants name the app, per engine |
Two ways to connect
- Remote (recommended). A hosted Streamable HTTP server with OAuth 2.1 — you authorise it once from the assistant, and there is no key to paste or rotate.
- Local (stdio). The
storelift-mcppackage on npm, run next to the assistant with an API key from your account.
The remote server also ships prompts — ready-made questions like "which keywords lost ground this week" — so the assistant does not have to be told how to assemble the query.
What you do with it
Ask in plain language
“Which of my keywords lost ground in Germany this week?” is a question, not a dashboard filter.
Set the server upPut ASO next to your other data
An assistant that already sees your analytics can now see your ranks in the same conversation.
See where the numbers come fromDraft with evidence in context
Metadata written next to the actual ranks is a different draft from metadata written from memory.
Compare the ASO MCP serversWhat this does not do
Every tool is read-only. There is no write path at all.
The measurement states travel with the data, which is the part a model would otherwise paper over:
- It does not write anything. No path from an assistant to your listing, your keywords or your billing.
- It does not measure on demand. The tools read what the nightly run collected; they do not trigger new searches against the stores.
- It does not flatten the states. An unmeasured day says so, rather than returning a zero the model would then reason about.
What each plan includes
| Free | Pro | Studio | |
|---|---|---|---|
| API access (required for the local server) | — | Yes | Yes |
| Remote MCP server | — | Yes | Yes |
| Keywords the tools can read | 25 | 250 | 500 |
| History the tools can read | 30 days | 365 days | 365 days |
Pro is $20/month ($18 billed yearly), Studio $60/month ($54 billed yearly).
Frequently asked
How many tools does the server expose?
8: list_apps, get_keywords, get_history, get_rivals, get_store_page, get_reviews, get_charts and get_ai_visibility.
Can an assistant change my keywords or metadata through it?
No. Every tool is read-only, and there is no write path from MCP to your listing, your tracked keywords or your account.
Do I need to paste an API key?
Not for the remote server — it uses OAuth 2.1, so you authorise it once from inside the assistant. The local stdio package does use an API key from your account.
Which plans include it?
Pro and Studio. The free plan does not include API access.
See this for your own app
Paste your store link, add your keywords. Rank, the apps above you and demand are measured every day.
Start free →