# Apptiller MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.apptiller%2Fapptiller
Registry id: `mcp-registry/com.apptiller/apptiller`
Status: live (checked 2026-11-22T16:31:59.412Z)

## Measurements (30 days)

- Uptime: 99.87%
- Checks: 1012
- Outages (90 days): 1

## Install

```json
{
  "mcpServers": {
    "apptiller-mcp-server": {
      "type": "http",
      "url": "https://mcp.apptiller.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http apptiller-mcp-server https://mcp.apptiller.com/mcp
```

## Tools (59)

- `ai_referrals`: Use this when the user asks how many visitors AI assistants sent to their website. Whether the app's website script is installed (status), and what it counted f
- `ai_referrals_setup`: Use this when the user wants to count visitors that AI assistants send to their website. Turns on counting of the people ChatGPT, Perplexity, Gemini, Copilot, C
- `ai_visibility_collect`: Use this after asking the questions again, to fetch the answers that are ready. Fetches every queued answer that is ready and scores it. Runs by itself every ho
- `ai_visibility_plan`: Use this when the user asks how many apps, questions or runs their AI-answer tracking covers. The organization's AI-visibility allowance: how many products and 
- `ai_visibility_report`: Use this when the user asks whether ChatGPT or Google's AI answers recommend their app, and who they name instead. How often ChatGPT, Google AI Mode and AI Over
- `ai_visibility_run_now`: Use this when the user asks for fresh AI answers now instead of waiting for the daily run. Queues one extra round of a project's questions on its engines now, i
- `ai_visibility_set_questions`: Use this when the user wants to add or change the questions AI answers are checked for. Adds the questions people would ask an assistant when looking for an app
- `ai_visibility_track`: Use this when the user wants to start tracking whether AI assistants recommend their app. Starts (or updates) tracking whether ChatGPT, Google AI Mode and Googl
- `ai_visibility_tracked`: Use this when the user asks which apps and questions are tracked in AI answers. Lists the apps tracked in AI answers, what Apptiller looks for in each, and thei
- `app_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 for one app: the brief 
- `app_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 (with create) and map
- `app_ownership`: Use this when the user asks whether Apptiller sees an app as theirs, or how to prove it. Whether the app is proven to be this organization's, and by what: a con
- `app_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, installs, trials, revenue
- `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, per storefront: for 
- `app_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 listing and featurin
- `app_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 conversion. Apple's A
- `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, per storefront: the 
- `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, version, genre, price
- `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 reviews for one app from A
- `app_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 App Store numbers from 
- `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 connected user's roles in 
- `apple_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 Store search ads) number
- `apple_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 as keywords or negat
- `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. Makes the change a propos
- `apps`: 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 account with the ad acc
- `attribution_performance`: Use this when the user asks which network, campaign or keyword brought installs, as the attribution tool counted them. Daily installs by attribution source from
- `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 for an app with no MMP 
- `briefing`: 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 in each app's last 14 
- `campaigns`: Use this when the user asks what to do next for growth, how a campaign is going, or what a move brought. One app's growth brief (audiences, each with the posts 
- `check_launch`: Use this after the user connects or proves something that could change a launch's tier. Works out a launch's tier again from what is connected now (after connec
- `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 live, so Apptiller c
- `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 or Google Search Conso
- `data_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 (Apple Ads, Meta, …), ov
- `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 proposal is rejected, and
- `edit_launch`: Use this when the user asks to change how a launch shows on the board. Changes what the board shows of a launch: its name, tagline, category, and whether dollar
- `launch_ai_answers`: Use this when the user asks whether AI answers name their launched product. A claimed launch's free AI answers (tier owner or verified; an unclaimed launch can 
- `launch_product`: Use this when the user asks to launch their app or website on Apptiller Launches. Launches an app (from its App Store link or id) or a website (its domain, plus
- `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 Ads, RevenueCat, App
- `list_domains`: Use this when the user asks which domains are verified. The organization's domains with their state (pending, verified, lapsed, failed) and the TXT record each 
- `list_launches`: Use this when the user asks how their launches on Apptiller Launches are doing. This organization's launches on Apptiller Launches: period, tier, proof, what wo
- `mark_move`: Use this when the user says they did one of a campaign's moves (posted the reply, sent the pitch, put the page live, asked the creator) or want to drop one. don
- `meta_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 status.
- `meta_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 permissions and granted 
- `meta_performance`: Use this when the user asks how their Meta (Facebook, Instagram) ads are doing. Spend, impressions, reach, clicks, CPM, CTR and key results (purchases, trials, 
- `organic_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 shows it: one ranked list
- `reject_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 account; the finding
- `revenuecat_chart`: Use this when the user asks how a subscription metric (trials, conversion, MRR, churn, retention) moved over time. A RevenueCat chart over time: trials, trial c
- `revenuecat_chart_options`: Use this before building a RevenueCat chart, to see what it accepts. The resolutions, segments (country, product, store…), filters and selectors a RevenueCat ch
- `revenuecat_overview`: Use this when the user asks for an app's current subscription numbers, such as MRR, active subscriptions or trials. Current subscription metrics for a RevenueCa
- `revenuecat_projects`: Use this when the user asks which RevenueCat projects Apptiller can read. Lists the RevenueCat projects Apptiller can read, with their ids.
- `revenuecat_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 two dates (inclusive
- `set_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 agent works from for o
- `set_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 may go. Owners and ad
- `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 verified, in a conne
- `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 (connections to add 
- `site_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 on and what's missing
- `to_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: the open items of A
- `undo_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 Apptiller changed it. Onl
- `verify_domain`: Use this when the user wants to prove they own a domain. Starts proving the organization owns a domain, or checks it again: returns the TXT record to add at the

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
