App Store Operator
The App Store Operator server provides iOS App Store competitive intelligence and marketing tools, integrating Apple's public APIs and SensorTower analytics into an AI assistant. All tools are read-only and iOS App Store only (no Google Play).
Search App Store (
search_app_store): Search the App Store by keyword and get ranked results (up to 25) as a markdown table with app name, publisher, rating, and app ID. No SensorTower account required.Research Rivals (
research_rivals): Fetches the top 3 apps for a keyword with full SensorTower analytics — downloads, revenue, ratings, publisher info, top markets, release dates, languages, in-app purchases, and ad network presence. Results are cached for 24 hours. Requires a free SensorTower login on first use.Get App Analytics (
get_app_details): Retrieves fresh SensorTower analytics for specific app IDs you provide. Returns the same metrics asresearch_rivalsfor any apps you choose; never cached, ~10–20 seconds per app.Prepare In-App Event Copy (
prepare_iae): Generates 3 variations of iOS In-App Event metadata (event name ≤30 chars, short description ≤50 chars, long description ≤120 chars) based on your keywords, locale, audience, tone, and context. Runs entirely locally with no network calls.Six pre-built prompt workflows: Competitor snapshots, keyword shortlisting, app teardowns, positioning gap analysis, metadata rewrites, and full in-app event flows — usable as slash commands in supported clients.
Reference resources: Country codes, ASO field limits, IAE field rules, supported locales, and cached research results — accessible as context without tool calls.
Provides tools for searching the App Store, retrieving detailed app analytics (downloads, revenue, ratings, markets, etc.) from SensorTower, and generating In-App Event copy, enabling competitive analysis and ASO research.
App Store Operator
App Store competitive intelligence, inside Claude.
App Store Operator is an MCP server that brings App Store research directly into your AI assistant. Instead of switching to a dashboard, you ask Claude for ranked keyword results, competitor download and revenue estimates, or App Store Connect-ready In-App Event copy — and get the answer in the same conversation where you are making the decision.
Built for indie iOS developers who want research inside their workflow rather than in another browser tab. Free and open source (MIT). A lightweight alternative to SensorTower, AppTweak, and AppFollow for iOS-only competitive research.
claude mcp add --transport stdio app-store-operator -- npx -y app-store-operator@latest→ app-store-operator.com · Setup guide
What it does
Searches the App Store for competing apps on a given keyword and pulls detailed analytics from SensorTower — downloads, revenue, ratings, top markets, publisher info, and more.
search_app_store and prepare_iae work with no account at all. research_rivals and
get_app_details open a browser once for a free SensorTower sign-in, then reuse that
saved session — no paid plan, no API key.
Everything the server exposes — four tools, six prompts, seven resources — is read-only. Nothing writes to your App Store Connect account, to SensorTower, or anywhere but a local cache file.
Related MCP server: meta-ads-mcp-server
Tools
research_rivals
Finds the top 3 apps for a keyword and returns a full metrics report for each.
Parameter | Type | Description |
| string | Search term to look up (e.g. |
| string | Two-letter country code (e.g. |
Returns for each competitor:
App Store & SensorTower URLs
Worldwide and last-month downloads & revenue
Rating score and rating count
Publisher, categories, top markets
Release date, last updated, supported languages
In-app purchases and ad network presence
Cached for 24 hours, so asking again about the same keyword and country costs nothing and opens no browser.
search_app_store
Searches the App Store for a keyword and returns ranked results as a markdown table — instantly, no SensorTower required.
Parameter | Type | Description |
| string | Search term to look up |
| string | Two-letter country code |
| number | Number of results to return (1–25, default 3) |
Use this to discover which apps rank before deciding which to analyse. Follow up with get_app_details for analytics on specific apps.
get_app_details
Fetches SensorTower analytics for one or more app IDs you already have.
Parameter | Type | Description |
| array | Numeric App Store IDs (e.g. from |
| string | Two-letter country code |
Returns for each app:
Downloads and revenue (worldwide + last month)
Rating score and rating count
Publisher, categories, top markets
Release date, last updated, supported languages
In-app purchases and ad network presence
Never cached — every call scrapes fresh, at roughly 10–20 seconds per app ID.
prepare_iae
Generates iOS App Store In-App Event (IAE) copy — 3 variations in the target language, then a final report.
Parameter | Type | Description |
| array | Ordered keywords by priority (index 0–2 = Tier 1, 3–6 = Tier 2, 7–9 = Tier 3) |
| string | Target locale (e.g. |
| string | What the event is about and why users should care |
| string | Target audience (e.g. students, professionals, parents) |
| string | Real-world hook tying the event to a moment (e.g. a holiday, season) |
| string | Primary conversion goal (e.g. attract new users, boost engagement) |
| string | Copy tone: |
Returns: a structured brief used to generate 3 copy variations, each with event name (≤30 chars), short description (≤50 chars), and long description (≤120 chars).
Any field SensorTower does not expose, or keeps behind its paywall, comes back as N/A.
The server reports the gap rather than filling it, and the prompts below tell the assistant
to do the same.
Prompts
Six ready-made workflows that already chain the tools above, so you don't have to describe the sequence yourself. In Claude Code they appear as slash commands; other clients surface them in a prompt picker.
Prompt | Arguments | What it does |
|
| Pulls rival analytics for a keyword, then reads out who owns it and how contested it is |
|
| Expands a seed keyword into candidates, tests each against live search results, and ranks them attack / watch / skip |
|
| Teardown of known apps — scale, standing, monetisation, reach, momentum, acquisition |
|
| Puts your app on the same measuring stick as the incumbents and separates behind from attackable |
|
| Three name / subtitle / keyword-field variations, character-counted against Apple's limits |
|
| Runs the full In-App Event flow, asking for whatever |
Arguments marked ? are optional. Every prompt tells the assistant not to invent figures and, where SensorTower is involved, not to quietly fall back to a weaker tool when login is required.
Resources
Reference data and local state a client can attach as context without spending a tool call on it.
URI | Type | Contents |
| markdown | Which tool to use, what each costs, how the SensorTower login works |
| markdown | Two-letter storefront codes by region |
| JSON | App Store Connect character limits and which fields are indexed for search |
| JSON | In-App Event limits, artwork sizes, copy rules, keyword tiers |
| JSON | Every locale |
| JSON | What has already been researched on this machine, and whether it is still fresh |
| JSON | One cached |
Nothing here leaves your machine: the reference resources are static, and the two cache resources read ~/.app-store-operator/cache.json.
Requirements
Node.js v18+
A desktop session for
research_rivalsandget_app_details. They drive a real, visible Chromium window so you can sign in to SensorTower, so they need a display — they do not work over plain SSH or inside a container. The other two tools have no such requirement.Disk space for Chromium. Installing the package downloads a Playwright Chromium build (a few hundred MB) via a postinstall step. If that step fails, the server installs it on first use instead; you can also run
npx playwright install chromiumyourself.
Usage
As an MCP server (Claude Code / Claude Desktop / OpenAI Codex)
Claude Code — run this command once:
claude mcp add --transport stdio app-store-operator -- npx -y app-store-operator@latestClaude Desktop — add to your MCP config:
{
"mcpServers": {
"app-store-operator": {
"command": "npx",
"args": ["app-store-operator@latest"]
}
}
}OpenAI Codex — run this command once:
codex mcp add app-store-operator -- npx -y app-store-operator@latestCodex stores MCP servers in ~/.codex/config.toml. If you prefer to edit it directly:
[mcp_servers.app-store-operator]
command = "npx"
args = ["-y", "app-store-operator@latest"]
# Optional but useful for SensorTower scraping flows
startup_timeout_sec = 20
tool_timeout_sec = 180Then restart Codex or start a new thread, and ask things like:
Research rivals for "hairstyle" in the GB App StoreSearch the App Store for "beard style" in FrancePrepare an in-app event for a summer hairstyle campaign in en-gb
No installation step needed — npx fetches and runs the package automatically.
The server communicates over stdio and is designed to be invoked by an MCP client. It advertises server-wide instructions during initialize so clients route between the tools correctly, and returns an MCP tool error when SensorTower login is required.
Configuration
Both settings are optional environment variables on the server process.
Variable | Default | What it does |
|
| How long a |
| unset | Set to |
In a container
The repo ships a Dockerfile built on Playwright's official image:
docker build -t app-store-operator .
docker run -i --rm app-store-operatorThe server speaks JSON-RPC over stdio, so no port is exposed — point your MCP client at
the container's stdin/stdout. Note that a container has no display: search_app_store
and prepare_iae work there, but the two SensorTower tools cannot open a login window and
will fail rather than prompting you to sign in.
How it works
Searches the App Store for the keyword and country, and looks up any app IDs you passed directly against Apple's public iTunes Lookup API
For each app, drives a Chromium browser to scrape SensorTower analytics
Extracts the metrics and returns a compiled report
SensorTower data is scraped via Playwright because it is rendered client-side.
A browser window will open. This is deliberate, not a bug: SensorTower requires a login, so the first run opens a visible window for you to sign in. The session is saved to ~/.app-store-operator/profile and reused on every later call, so you only log in once. If a tool reports not_logged_in, finish signing in on that window and run the tool again.
Results from research_rivals are cached for 24 hours in ~/.app-store-operator/cache.json — override the TTL with the ASO_CACHE_TTL_HOURS environment variable.
Limitations
iOS only. Nothing here covers Google Play or Android.
Read-only. No tool changes anything in App Store Connect or on SensorTower.
research_rivalsis fixed at the top 3 results. Usesearch_app_store(up to 25) and thenget_app_detailswhen you need a wider set.Scraping is brittle by nature. SensorTower renders its dashboard client-side and changes its markup without notice; when it does, affected fields return
N/Auntil the selectors are updated. A single app failing never fails the whole call.SensorTower's free tier decides what you see. Paywalled figures come back as
N/A.
Privacy Policy
Full policy: https://app-store-operator.com/privacy
App Store Operator runs entirely on your machine. There is no backend, no telemetry, and no analytics — the author collects, receives, and stores nothing about you or your usage.
What each tool sends, and where:
Tool | Account | What leaves your machine |
| None | Keyword and country code → Apple's public App Store search |
| None | Nothing — pure local computation, contacts no external service |
| Free SensorTower | Keyword and country code → Apple, then SensorTower via your own browser session |
| Free SensorTower | App Store app IDs → Apple's public lookup API and SensorTower |
What is stored locally:
~/.app-store-operator/cache.json— cached results, expiring after 24 hours by default (ASO_CACHE_TTL_HOURS)~/.app-store-operator/profile— the Chromium profile holding your SensorTower session
You type your SensorTower credentials into SensorTower's own page in a browser window on your machine. The server never reads or stores your password, and the author never receives it.
Deleting everything — no request to the author, nothing to wait for:
rm -rf ~/.app-store-operatorApple and SensorTower are independent third parties with their own policies. This project is not affiliated with either.
Project structure
src/
├── index.js # MCP server setup and request handlers
├── shared.js # App Store lookup + SensorTower scraping
├── cache.js # 24h local cache (research_rivals only)
├── prompts.js # the six prompt workflows
├── resources.js # reference data + cache resources
└── tools/
├── research-rivals.js # research_rivals tool
├── search-app-store.js # search_app_store tool
├── get-app-details.js # get_app_details tool
└── prepare-iae.js # prepare_iae tool
scripts/postinstall.js # installs Playwright Chromium on install
scripts/sync-version.js # syncs server.json, manifest.json and CHANGELOG.md on release
test/smoke-test-mcp.js # stdio smoke test
server.json # MCP registry manifest
manifest.json # Claude Desktop / MCPB bundle manifest
Dockerfile # container build (no display: search + IAE tools only)Development
No build step and no linter — clone it, npm install, and run npm start to boot the
server over stdio.
The smoke test verifies the server boots and exposes everything it should. It checks
initialize (including the server instructions and the advertised version), tools/list,
prompts/list, prompts/get, resources/list, resources/templates/list, and reads
every resource, failing if one declared as JSON does not parse. It makes no network calls
and opens no browser:
npm run smokeReleases are tag-driven: write the notes under ## Unreleased in CHANGELOG.md, run
npm version <patch|minor|major> — which syncs the version into server.json and
manifest.json and renames that heading to the new version for you — then push with
--follow-tags. GitHub Actions runs the smoke test, publishes to npm and the MCP
registry, and creates the release from that changelog section. The bump refuses to run
while ## Unreleased is empty.
Contributions are welcome — open an issue or a pull request at github.com/meyusufdemirci/app-store-operator.
License
MIT © Yusuf Demirci
Available Tools
4 toolsget_app_detailsGet App AnalyticsARead-only
Fetch SensorTower analytics for one or more App Store app IDs. Returns downloads, revenue, ratings, publisher info, markets, and more for each app.
Use this when you already have app IDs (e.g. from search_app_store) and want detailed analytics for only a subset of them — avoiding unnecessary scrapes for apps you don't need.
Use research_rivals instead for a single convenience call that searches and fetches analytics together.
Do not use this for Google Play or Android apps — it takes numeric iOS App Store IDs only.
Requires a SensorTower account. The server opens a real Chromium window on the user's machine; the first run needs the user to log in there, and the session is reused from then on. If there is no session the call returns an error result carrying {"error": "not_logged_in"} and leaves the window open — tell the user to log in, then call again. Results are never cached, so every call scrapes fresh and costs roughly 10–20 seconds per app ID.
Returns JSON:
{
"country": "us",
"fetchedAt": "2026-04-21T10:00:00.000Z",
"apps": [
{
"rank": 1,
"name": "App Name",
"appStoreUrl": "...",
"sensorTowerUrl": "...",
"downloads": "<5K",
"revenue": "<$5K",
"rating": { "score": "4.7", "count": "1,234" },
"publisher": "Publisher Name",
"categories": "Health & Fitness",
"topMarkets": "United States, United Kingdom",
"releaseDate": "Jan 1, 2020",
"lastUpdated": "Mar 15, 2026",
"languages": "English, Spanish",
"inAppPurchases": "Monthly · $9.99",
"publisherCountry": "United States",
"advertisingNetworks": "N/A"
}
]
}Fields missing or gated behind a paywall will be "N/A". A single app failing to scrape is not fatal — that app comes back with "N/A" fields rather than failing the whole call.
Inputs: app_ids (required), country (required).
prepare_iaePrepare In-App Event CopyARead-only
Prepare an iOS App Store In-App Event (IAE) — generate copy variations and a final report.
Use this when the user wants to create or draft an in-app event, prepare IAE metadata, or generate App Store event copy. Accepts user-supplied keywords and event parameters, then returns a structured brief. Do not use it for ordinary App Store listing metadata (title, subtitle, description) — it covers In-App Event fields only.
Runs entirely locally: no network calls, no App Store or SensorTower lookup, and no keyword research of its own — the caller supplies the keywords (reach for research_rivals or search_app_store first if you still need to find them). Returns immediately.
After receiving the tool output, you MUST:
Generate 3 distinct copy variations in the target language (from
locale.language), each differing meaningfully in angle, tone, or keyword emphasis. For each variation produce:Event name (hard limit: 30 chars — count every character; trim at word boundary if over)
Short description (hard limit: 50 chars — same rules)
Long description (hard limit: 120 chars — same rules) Display every field with its exact character count and ✓ / ✗ indicator. Fix any ✗ before showing the user. Keyword placement: Tier 1 keywords must appear in short description and long description; embed in event name only if it fits naturally. Prioritize keywords toward the beginning of each field. Copy rules: active voice, present tense, no pricing claims or % discounts, no competitor names, all three fields independently meaningful. If locale is not en-US, add an English translation line under each localized field so the user can verify meaning.
Ask the user to choose one variation.
After the user picks a variation, print the output table and the final summary report using this exact format:
Output table:
CHOSEN VARIATION — <locale.appleCode>
─────────────────────────────────────
Event name : <text> (<N>/30)
Short description : <text> (<N>/50)
Long description : <text> (<N>/120)
─────────────────────────────────────
Next step: upload event artwork in App Store Connect
• Event card image : 2160 × 1080 px
• App icon overlay : 1024 × 1024 pxFinal summary report:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
IN-APP EVENT REPORT
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
IAE locale : <locale.appleCode> (<locale.language> — <locale.country>)
Keyword store : <locale.store> store
Target audience : <audience>
Event context : <event_context>
Goal : <goal>
Tone : <tone>
─────────────────────────────────────
Keywords used : <Tier 1 placed> | <Tier 2 placed>
Event name : <text> (<N>/30 chars)
Short description: <text> (<N>/50 chars)
Long description : <text> (<N>/120 chars)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CHECKLIST
[ ] IAE locale is <locale.appleCode>
[ ] Event name ≤ 30 chars
[ ] Short description ≤ 50 chars
[ ] Long description ≤ 120 chars
[ ] No pricing claims or % discounts
[ ] No competitor names
[ ] Event artwork assets prepared (1024×1024 + 2160×1080)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━Flag any checklist item that is not yet satisfied.
Returns JSON with the structured brief for generating copy.
Inputs: goal (required), tone (required), locale (required), audience (required), +3 more.
research_rivalsResearch App Store RivalsARead-only
Search the App Store for a keyword and fetch SensorTower analytics for the top results — all in one call. Results are cached for 24 hours so repeat queries are instant.
Use this for a quick competitive overview when you want everything in one step.
Use search_app_store + get_app_details separately when you need more than 3 results, a custom limit, or selective fetching of specific apps.
Do not use this for Google Play or Android apps — it covers the iOS App Store only.
Requires a SensorTower account. On a cache miss the server opens a real Chromium window on the user's machine; the first run needs the user to log in there, and the session is reused from then on. If there is no session the call returns an error result carrying {"error": "not_logged_in"} and leaves the window open — tell the user to log in, then call again. A cache miss scrapes three apps and typically takes 30–60 seconds; a cache hit returns immediately and opens no browser.
Trigger phrases: "rival research", "research rivals", "competitor analysis", "find competing apps", "check competitors", "what apps compete with", "App Store competitors", "rivals for keyword".
Returns JSON:
{
"keyword": "meditation",
"country": "us",
"fetchedAt": "2026-04-21T10:00:00.000Z",
"cached": false,
"apps": [
{
"rank": 1,
"name": "App Name",
"appStoreUrl": "https://apps.apple.com/us/app/id123456",
"sensorTowerUrl": "https://app.sensortower.com/overview/123456",
"downloads": "<5K",
"revenue": "<$5K",
"rating": { "score": "4.7", "count": "1,234" },
"publisher": "Publisher Name",
"categories": "Health & Fitness",
"topMarkets": "United States, United Kingdom",
"releaseDate": "Jan 1, 2020",
"lastUpdated": "Mar 15, 2026",
"languages": "English, Spanish",
"inAppPurchases": "Monthly · $9.99",
"publisherCountry": "United States",
"advertisingNetworks": "N/A"
}
]
}Fields missing or gated behind a paywall will be "N/A". A single app failing to scrape is not fatal — that app comes back with "N/A" fields rather than failing the whole call. When cached is true, the data was served from the local cache and no scraping occurred.
Present results as a clean report for each app:
#1 — {name}
App Store: {appStoreUrl}
SensorTower: {sensorTowerUrl}
Downloads: {downloads}
Revenue: {revenue}
Rating: {rating.score} ({rating.count} ratings)
Publisher: {publisher}
Categories: {categories}
Top Markets: {topMarkets}
Worldwide Release Date: {releaseDate}
Last Updated: {lastUpdated}
Languages: {languages}
In-App Purchases: {inAppPurchases}
Publisher Country: {publisherCountry}
Advertised on Any Network: {advertisingNetworks}
Inputs: country (required), keyword (required).
search_app_storeSearch the App StoreARead-only
Search the App Store for a keyword and return ranked results as a detailed table — instantly, no browser required.
Use this when you want to discover which apps rank for a keyword before deciding which ones to analyse in depth.
Follow up with
get_app_detailsto fetch SensorTower analytics for specific app IDs.Use
research_rivalsinstead for a single convenience call that searches and fetches analytics together.Do not use this for Google Play or Android apps — it covers the iOS App Store only.
Unlike research_rivals and get_app_details, this needs no SensorTower account, opens no browser window, and returns in about a second. It also carries no downloads or revenue figures — those only come from the SensorTower tools.
Returns markdown (not JSON): one table per result, ranked, with every App Store field available including the numeric app ID that get_app_details takes. Unavailable fields read "N/A". A keyword with no matches returns just the header line and no tables.
Inputs: country (required), keyword (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
The four tools have clearly distinct purposes: search_app_store for discovery, get_app_details for analytics on specific IDs, research_rivals as a combined convenience wrapper, and prepare_iae for in-app event copy generation. Each description explicitly tells when to use it versus the alternatives, eliminating ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case: research_rivals, search_app_store, get_app_details, prepare_iae. Verbs (research, search, get, prepare) clearly indicate actions, and nouns (rivals, app_store, app_details, iae) identify the target. No mixing of casing or verb styles.
Four tools is well-scoped for an iOS App Store operations server. The primary workflows are covered: discovering apps (search_app_store), retrieving analytics (get_app_details), a combined research shortcut (research_rivals), and creating in-app events (prepare_iae). No bloat or redundancy; each tool earns its place.
The tool surface covers the main research and IAE copy generation workflows thoroughly. Minor gaps exist: no tool for managing App Store listing metadata (title, description), and no explicit handling of Google Play, but the tool descriptions clearly scope the server to iOS App Store research and IAE. The explicit boundary is acceptable, though a listing-management tool would round out the 'Operator' name.
Maintenance
Related MCP Connectors
Market & competitive intelligence for Claude & AI assistants: trends, alerts, keywords & more.
Analyse App Store and Google Play reviews in Claude: counts, trends and real quotes for any app.
Amazon competitor research for Claude, ChatGPT and other MCP clients: complaint topics from Amazon's "Customers say" summary of all reviews, 90-day price/rank/review history, listing audits (0-100), keyword rankings with who's advertising, and daily Competitor Watch emails when a rival's price, stock, rank or complaints change. 12 Amazon marketplaces, plus Shopify store teardowns and tracking. 25 free credits. Sample: zonrival.com/sample
App Store keyword rankings, competitors, markets, reviews and analytics for iOS apps, from your AI.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceOpen-source MCP server for Claude AI that connects Stripe and Supabase to enable natural language SaaS analytics, including churn analysis, subscription tracking, and revenue insights.-
- AlicenseAqualityDmaintenanceMCP Server for the Meta Marketing API. Gives Claude Desktop direct access to your ad account data — campaign performance, creative analysis, audience breakdowns, and budget pacing.10280 npm1MIT
- AlicenseAqualityFmaintenanceAn MCP server that gives AI assistants structured access to App Store Connect data. Built for ASO analysis, download tracking, and performance monitoring.71MIT
- AlicenseAqualityCmaintenanceAn open-source MCP server for live Apple App Store competitor research, enabling AI agents to search apps, fetch metadata, compare competitors, and retrieve reviews and top charts as structured JSON.7MIT