Categories › Business & Finance › Market data, stocks & crypto
Grow App Store apps: ranks, listing, ads, revenue and AI answers. Sign in to read your own apps.
Remote server: your requests and data go to mcp.apptiller.com. Claude Code: claude mcp add --transport http apptiller https://mcp.apptiller.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
list_connections — Use this when the user asks which services are connected to Apptiller. Shows which services (Meta Ads, App Store Connect, Apple Ads, Google setup_suggestions — Use this when the user asks what to set up next in Apptiller, or why some numbers are missing. What this Apptiller account is still missing connect_account — Use this when the user wants to connect a service to Apptiller: App Store Connect, an ad account, an attribution tool, RevenueCat, Stripe ormeta_ad_accounts — Use this when the user asks which Meta ad accounts Apptiller can read. Lists the Meta ad accounts Apptiller can read, with currency and statmeta_diagnose — Use this when Meta data is missing or a Meta account can't be read. Shows what the connected Meta token is (system user or person), its permmeta_performance — Use this when the user asks how their Meta (Facebook, Instagram) ads are doing. Spend, impressions, reach, clicks, CPM, CTR and key results apple_ads_accounts — Use this when the user asks which Apple Ads accounts Apptiller can read. Lists the Apple Ads ad accounts Apptiller can read, with the connecapple_ads_performance — Use this when the user asks how their Apple Ads campaigns, ad groups or keywords are doing, as Apple reports them. Daily Apple Ads (App Storapple_ads_search_terms — Use this when the user asks what people searched when their Apple Ads showed, which searches Search Match matched, or which searches to add attribution_setup — Use this only when the user asks to set up Apple Ads attribution for an app that has no attribution or revenue SDK. An optional fallback forattribution_performance — Use this when the user asks which network, campaign or keyword brought installs, as the attribution tool counted them. Daily installs by attapp_store_sales — Use this when the user asks about an app's downloads, sales, proceeds or refunds. Not for which ad brought a download. Apple's own daily Appapp_store_funnel — Use this when the user asks where an app's downloads came from (search, browse, websites, other apps) or about impressions, page views and crevenuecat_projects — Use this when the user asks which RevenueCat projects Apptiller can read. Lists the RevenueCat projects Apptiller can read, with their ids.revenuecat_overview — Use this when the user asks for an app's current subscription numbers, such as MRR, active subscriptions or trials. Current subscription metrevenuecat_revenue — Use this when the user asks how much revenue an app made between two dates, from RevenueCat. Total revenue for a RevenueCat project between revenuecat_chart_options — Use this before building a RevenueCat chart, to see what it accepts. The resolutions, segments (country, product, store…), filters and selecrevenuecat_chart — Use this when the user asks how a subscription metric (trials, conversion, MRR, churn, retention) moved over time. A RevenueCat chart over tapps — Use this when the user asks which apps are in their Apptiller account, or which accounts feed each app. Lists the apps in this Apptiller accapp_map_sources — Use this when the user wants to add an app to Apptiller or link an ad account, attribution app or RevenueCat project to it. Creates an app (app_store_listing — Use this when the user asks what an app's App Store listing says or what changed in it. An app's App Store listing (name, icon, developer, vapp_performance — Use this when the user asks about one app's ad spend, installs, revenue, ROAS or cost per install across ad networks. One app's spend, instadata_coverage — Use this before judging ad campaigns by revenue or paying users, or when the user asks what their data can show. Per app and ad channel (Appbriefing — Use this when the user asks what's wrong with their ads, what to change, or what an earlier ad change did. What Apptiller's analyst found inapp_brief — Use this when the user asks what goal, markets, constraints or limits Apptiller works from for an app. What Apptiller's agent works from forset_app_brief — Use this when the user states an app's goal, markets, competitors or constraints for Apptiller to work from. Writes the brief Apptiller's agset_app_limits — Use this only when the user asks to change how far Apptiller may go with an app's ad changes. Sets, for one app, how far Apptiller's agent msite_guides — Use this when the user asks about the guides Apptiller writes for their app's website. Daily guides for one app's website: whether they're oorganic_todo — Use this when the user asks what to do to show up more in Google search or AI answers. One app's organic To do, as Search & AI › To do showsto_do — Use this when the user asks what to do next for an app, or what is waiting for their approval. What to do next for an app, or for every app:app_store_keywords — Use this when the user asks which App Store searches an app ranks for, or how its keyword ranks moved. App Store keyword ranks for one app, app_store_charts — Use this when the user asks where an app sits in the App Store top charts, or why it moved. App Store category chart positions for one app, app_store_reviews — Use this when the user asks what reviewers say about an app, which reviews need an answer, or how its ratings are trending. App Store reviewapp_store_drafts — Use this when the user asks about proposed App Store listing edits, featuring nominations, in-app events or custom product pages. App Store set_site_guides — Use this only when the user asks to turn website guides on or off. Turns daily guides on or off for one app's website. On needs the website close_site_guide — Use this when the user says a guide went live, or wants to drop it. Marks one guide as published, with the full https address where it went apply_proposal — Use this only after the user has seen a specific proposal and said to apply it. Not for changes the user describes without a proposal. Makesundo_change — Use this only when the user asks to undo a change Apptiller made. Puts back, at the user's request, the value an ad account had before Apptireject_proposal — Use this when the user declines one of the analyst's proposals. Marks one of the analyst's proposals as rejected. Nothing changes in the ad dismiss_finding — Use this when the user wants a finding to stop coming up. Dismisses one of the analyst's findings: it leaves the briefing, its pending propoNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.