toolfare

Ask your AI which AppLovin creatives are worth another brief.

Spend, installs and CPA by campaign, delivery by creative set and by individual asset, and cohort ROAS and retention — answered inside ChatGPT, Claude, Codex or Cursor. Connect your AppLovin Ads Manager account to toolfare once; your AI reads it with your own key, and every read costs 0 credits.

Start Asking For FreeConnect in 1 Click

Set it up in

Claude CodeCodexCursorVS CodeChatGPTClaude (web & desktop)Your own agent
toolfare

Sign in, add the account’s API credentials once, paste the setup prompt to your agent, ask something.

Your accounts, one connection

ads, analytics, commerce and revenue

AppLovin

App campaign spend, creatives and cohort ROAS

AppLovin MAX

Estimated ad revenue by app, country and network

Adjust

Adjust

Attribution, cohorts and retention by network

200+

APIs

40+

apps

30+

skills

Ask once and your AI reads the accounts you connected — no paid data call involved.

Your own account0 credits per readRead-only
About five minutes

Set it up once, in the app you already use.

There is no AppLovin sign-in: add your AppLovin API credentials in toolfare once. After that, every AI app you approve reads it through the same connection.

Claude Code

Use the MCP connection in your AI app, or run the toolfare CLI in its terminal. Both use browser approval, discover capabilities and quote paid calls before they run.

  1. 1

    Create your toolfare workspace

    The connection is public and identical for everyone — your toolfare sign-in is what points it at your data. Connect one account in that workspace too: that is what your AI reads. The first time your AI uses the connection, toolfare asks you to approve the access and names the workspace it will read through. No workspace yet? toolfare has you create one right there, then brings you back to approve.

    Create your workspace

    Already have one? Nothing to do here — sign in when the connection asks for it.

  2. 2

    Copy the toolfare MCP connection

    https://api.toolfare.ai/mcp
  3. 3

    Add it to Claude Code

    claude mcp add --transport http toolfare https://api.toolfare.ai/mcp
    1. Run the command in any project. It writes the configuration and prints an `Added …` line.
    2. Authorize separately — adding a server does not open a browser.
    3. Run `claude mcp list` to confirm the server reads `✔ Connected`.
  4. 4

    Approve the access, then ask it something

    1. Inside Claude Code, run `/mcp` and follow the browser flow — or, from your shell, `claude mcp login toolfare`.
    2. The toolfare consent page names the host, the workspace the grant will read through, and what the connection will be able to do.
    3. Approving creates the grant listed above on this page. Cancelling creates nothing.
    4. On a machine with no browser (SSH, headless Linux), `claude mcp login toolfare --no-browser` prints the URL and takes the pasted callback.

    Paste this first

    Using toolfare, search for what capabilities I can reach.

    A list of capabilities with names, what each reads and what each costs. An empty list means the search matched nothing — try broader words. An error naming authorization means the host never completed the browser step.

Checked 2026-08-25 against Claude Code documentation. Menu names change between releases — look for connectors, apps, tools or integrations.

Open the console to connect your accounts
6 things you can ask it

Ask in plain English. These are the tools behind the answer.

Each one is a tool your AI is offered by name once you connect. You never have to type the name — it is here so you can tell what actually ran.

  • Which campaigns are spending and converting

    applovin_campaign_performance

    Impressions, clicks, CTR, installs, cost, CPC and CPA per campaign per day — the last seven complete UTC days unless you name a window.

    • “Which AppLovin campaigns spent the most last week?”
    • “What was CPA by campaign over the last 14 days?”

  • Winning and fatiguing creatives

    applovin_creative_performance

    Delivery, installs and cost by creative set and ad per day — what to cut and what to brief more of.

    • “Which creative sets are fatiguing?”
    • “Rank our AppLovin creatives by installs this week.”

  • The numbers behind one image, video or playable

    applovin_asset_performance

    Impressions, clicks, CTR and cost per asset, joined to its creative set and campaign — the report that ties a specific file to its results.

    • “Which playable has the best CTR?”
    • “How did each video asset perform yesterday?”

  • Cohort ROAS and retention, by campaign

    applovin_roas_retention

    ROAS at day 1, 7 and 30 and retention at day 1, 7 and 28, per campaign, in cohort attribution — value credited back to the install date, and labelled as such.

    • “What is day-7 ROAS by campaign for installs from last month?”
    • “Which campaign retains users best at day 28?”

  • Any slice the ready-made reports do not cover

    applovin_run_report

    An advertiser report over the columns you choose from AppLovin’s documented set — ROAS by country, delivery by placement type, and the like. An unknown column is rejected rather than silently dropped.

    • “Break down ROAS by country for our main campaign.”
    • “Show delivery by placement type for the last week.”

And 1 more, same connection

Named rather than worked through — your AI discovers all of them through the connection itself, so you never have to pick one.

  • The AppLovin accounts this workspace can readapplovin_list_accounts
Pricing

Buy toolfare credits for your research and agent workflow.

Pay as you go. Buy credits when you need them, with no subscription.

Pay as you go

10,000 credits from $30

Buy credits when you need them. No subscription. Every paid call is quoted before it runs.

Buy credits