Appfigures pricing, plans, and MCP limits

Appfigures pricing on 31 August 2026 starts with a free Starter plan, then an Analytics & ASO grid from Connect at $9.99/mo ($7.99 billed yearly) through Amplify at $1,399.99/mo ($999.99 yearly). A second Market Intelligence grid on the same URL runs Scout $599.99/mo to Scale $2,499.99/mo, with Explore sold as a quote. MCP is real, but it is a local stdio server: npx -y @appfigures/cli mcp. That is a different install shape from Trends MCP Cursor JSON (url + transport: http + Bearer). Appfigures still wins linked App Store Connect and Google Play revenue. Trends MCP is the cheaper path when the job is live App Store / Google Play boards into an agent, not owned-app P&L.

What do the Analytics cards print today?

The public Appfigures pricing page (accessed 31 August 2026) labels two product families: Analytics & ASO, and Market Intelligence. The Analytics cards all print "5 Apps, then $1.99 each." Keyword caps and premium-competitor slots are the visible upgrade ladder.

The page header says "Save 20%." The printed yearly /mo figures match that math on Connect through Amplify. The page does not print billed-annual totals for those Analytics cards (unlike Trends MCP HTML, which prints $192 / $468 / $1,910). Do not invent $95.88 or $16,799.88 from the /mo yearly rates.

Connect's own feature list includes "Unlimited review replies." The comparison grid under the same fetch prints 150 in the Connect Reply to Reviews cell, then Unlimited from Monitor through Amplify. Cite both. The trial FAQ says the trial is free, needs no card, and grants Optimize features. It does not print a day count. After expiry, accounts move to the free plan.

Monthly Boost copy is longer than yearly Boost copy on the same fetch. Monthly Boost lists unlimited Apple Ads Intelligence, complete App Intelligence for tracked apps (download and revenue estimates, custom product pages, cross-app usage), and "Swap tracked competitors up to 4 times/mo." Yearly Boost lists DPR / download / revenue estimates in Keyword Inspector plus Apple Ads Intelligence. Monthly Amplify lists unlimited App Intelligence on any app and game, market trend reports, and Mobile Market Index. Yearly Amplify lists global download estimates, audience demographics, ratings and reviews tracking, SDK analysis, product page insights, and complimentary apps. The dollar amounts match. The bullet lists do not. Treat the monthly and yearly cards as two documents.

The Analytics FAQ also says "All plans are monthly" and that there is no long-term commitment, with upgrades immediate and downgrades at cycle end. That sits on a page with an Annual billing toggle. The separate Billing 101 article (updated 15 January 2026, accessed 31 August 2026) describes yearly as a 20% prepaid amount for the next 12 months, then deducted at each monthly cycle. Changing plans, apps, or add-ons can burn that prepaid balance faster and renew the account early. New York billing addresses are taxed; other states are not, on that article.

Payment methods split across the same URL. The Analytics FAQ lists Visa, MasterCard, American Express, Discover, Paypal, and invoice on some plans. The Market Intelligence FAQ lists major cards, Paypal, checks, and ACH. Do not flatten those lists.

What do the Market Intelligence cards print?

Below the Analytics FAQ, the same 31 August 2026 fetch prints a second grid. Plan names and dollars:

Explore is the only Market Intelligence card that names API access in the feature list. Scout, Pathfinder, and Scale do not print an API line on those cards. Check current add-ons before assuming REST or MCP rides along on Scout.

The Market Intelligence FAQ (same page, same fetch) says every plan can see every app across the stores and markets the product supports. Seats: up to five users on any of those plans at no extra seat price; more seats are contact-only. Annual buyers are told they are not locked into long-term contracts. That wording is clearer than the Analytics FAQ's "all plans are monthly" line.

Appfigures also prints "Powering growth for 300,000+ apps worldwide" twice on the page. That is a trust line, not a SKU.

What Cursor config does Appfigures MCP actually ship?

Appfigures has an MCP server. It is not a hosted url + transport: http endpoint.

The AI agents help article (updated 29 July 2026, accessed 31 August 2026) and the @appfigures/cli npm README (package version 3.0.0, last npm update 19 August 2026, 630 weekly downloads on this fetch) both give the same Claude Desktop / Cursor-shaped stdio block:

{
  "mcpServers": {
    "appfigures": {
      "command": "npx",
      "args": ["-y", "@appfigures/cli", "mcp"]
    }
  }
}

The README adds a headless variant that passes APPFIGURES_API_KEY through env, and a global-install variant (command: af, args: ["mcp"]). Claude Code is documented as:

claude mcp add appfigures -- npx -y @appfigures/cli mcp

Tokens come from appfigures.com/developers/keys after creating a client, then a personal access token. Interactive login stores the token in the OS credential manager.

Trends MCP Cursor config, from docs.md on 31 August 2026, is remote HTTP:

"trends-mcp": {
  "url": "https://api.trendsmcp.ai/mcp",
  "transport": "http",
  "headers": { "Authorization": "Bearer YOUR_API_KEY" }
}

That is the install difference that survives next month. Appfigures MCP runs a local CLI over stdio and inherits whatever the logged-in plan can already see. Trends MCP is a remote server. Paste-ready Cursor JSON for Appfigures does not include url or transport. Paste-ready Cursor JSON for Trends MCP does not include command or npx.

The same help article still says public estimates and catalog data "require the Grow plan or above, with the Public Data API add-on enabled." The live pricing cards on 31 August 2026 do not name Grow. The top Analytics tier is Amplify. Older roundups still print Grow. Do not treat Grow as a live SKU until the pricing page prints it again.

docs.appfigures.com (accessed 31 August 2026) still describes public competitor data as a "Partner API addon" against https://api.appfigures.com/v2/. The MCP/API limits article names a "Public Data API" add-on. Same company, two product names, one job. Cite both.

What API limits sit under those plan prices?

The API, CLI, and MCP limits article (updated 11 August 2026, accessed 31 August 2026) is the durable meter.

Every account includes 1,000 API requests per day. Higher caps are add-ons from 2,500 to 50,000 requests per day. The article does not print dollar prices for those add-ons. Linked-store data (apps connected through App Store Connect or Google Play) has no extra data cost on API, CLI, or MCP. Public data for apps the account does not own burns Public Data API credits. Credits are bought in packages, do not expire, and are shared across API, CLI, and MCP. Package dollar amounts are behind a logged-in settings page. This run did not verify those package prices.

The public credit table on that article:

Review replies through API/CLI/MCP need a linked store account and a plan that includes replies. Commercial reuse, client processing, resale, or model training needs a separate license. The article tells readers to ask before building a product on this data.

Agent access follows the web plan: ranks through agents only if ranks are on the plan. Anyone with an Appfigures account can connect an agent. That is not the same as "MCP is free of plan gates."

When is Trends MCP the cheaper live-board path?

Appfigures is the right buy when the job is owned-app revenue, subscriptions, ad spend, review replies, or ASO keyword ranks against a linked store account. Trends MCP does not ingest App Store Connect. It does not estimate competitor IAP revenue. It does not reply to reviews.

Trends MCP is the right buy when the job is live store boards and Android bundle-ID history inside Cursor, Claude, or REST. The matching landing page is App Store trends in Cursor. Setup lives on MCP server for Cursor. Keyword history uses app downloads and app rankings with an Android bundle ID such as com.openai.chatgpt (Android app downloads API). Live boards use get_top_trends with App Store Top Free, App Store Top Paid, or Google Play. Default limit is 25, max 200, offset starts at 0.

Public Trends MCP prices on 31 August 2026, from HTML /pricing plus pricing.md and docs.md:

HTML yearly toggle copy: "2 months free." Keyword alerts: Pro 50, Business 250. Free card on HTML: top 10 trends, 12 months of history, 24-hour delayed data, 35+ data sources, MCP + API. Paid cards: all trends, full history, real-time. Fine print on paid yearly cards: charged after day 7. FAQ on the same HTML: card collected at checkout, not charged until day 8. Cite both.

Source-count split on the same day, do not flatten:

• HTML /pricing: 35+ data sources on every plan
• docs.md keyword table: 15 sources (no python row)
• MCP get_growth schema: includes python as a PyPI source
• docs.md live-feed table: 24 names, including all four by Category boards
• data-sources.md live-feed table: 20 names, omits all four by Category boards
• llms.txt intro: "plus 21 live feeds"
• llms.txt live-feed table: 24 names, same four by Category boards as docs.md
• docs.md still says official category names are on /data-sources, while data-sources.md omits those boards

HTML /pricing printed 9,663,156 API calls served on this fetch. The homepage counter on a fetch seconds later printed 9,663,099. Those two pages did not agree.

A 31 August 2026 roundup of the wider ASO set, including quote-only Sensor Tower, lives at Sensor Tower alternatives. That post is the comparison. This post is the Appfigures invoice.

FAQ

Does Appfigures have a free plan and a trial?

Yes. The 31 August 2026 pricing page opens with a free Starter plan. Paid Analytics cards start at Connect $9.99/mo. The trial FAQ grants Optimize features, needs no card, and moves expired trials to the free plan. The FAQ does not print how many days the trial lasts. Do not invent a 7-day or 14-day window from other vendors.

Is Appfigures MCP included, and what does it cost extra?

The AI agents article says anyone with an Appfigures account can connect an agent, and that agent access follows the same plan gates as the web app. Linked-store metrics have no extra data cost. Public estimates need the Public Data API add-on plus, on that article, "Grow or above." Grow is not a live pricing-card name on 31 August 2026. Daily API traffic starts at 1,000 requests. Add-on caps go to 50,000/day with no public dollar grid. Public Data credits are a second meter with a public per-call table and a private package-price page.

How is Appfigures MCP different from Trends MCP in Cursor?

Appfigures MCP is npx -y @appfigures/cli mcp over stdio, with login first. npm listed @appfigures/cli 3.0.0, 630 weekly downloads, last publish 19 August 2026. Trends MCP is remote HTTP at api.trendsmcp.ai with transport: http and a Bearer key in ~/.cursor/mcp.json. Appfigures MCP is for linked-store analytics and (with credits) public app intelligence. Trends MCP is for live multi-source trend boards, including App Store Top Free / Top Paid and Google Play, plus Android bundle-ID app downloads / app rankings.

Can Trends MCP replace Appfigures for ASO?

No. Trends MCP does not track 25 to 2,500 keywords against a listing, does not score Apple Ads, and does not reply to reviews. Connect at $9.99/mo is the Appfigures on-ramp for that job. Trends MCP Starter at $19/mo is cheaper than Monitor ($44.99) only if the job is live boards and growth calls, not ASO. Teams that need both should budget them as two line items.

Why do some Appfigures pages still say Grow?

The 29 July 2026 AI agents article still requires Grow for public estimates. The 31 August 2026 pricing cards use Amplify as the top Analytics tier and never print Grow. REST docs still say Partner API. The MCP limits article says Public Data API. Until Appfigures reprints one name on all three surfaces, quote the URL that was fetched, not a blended SKU.

Sources (accessed 31 August 2026): appfigures.com/pricing; help article 1chf6wf; help article 1seiibo; help article 4au00g; docs.appfigures.com; npm @appfigures/cli. Trends MCP HTML /pricing, docs.md, data-sources.md, and llms.txt on the same day.