toolfare

Ask your AI for last week’s DAU and retention, straight from TA.

The metrics your team already defined in ThinkingData — DAU, retention, ARPU — over any window and grouped by up to three properties, plus the events and properties tracked in each project, answered inside ChatGPT, Claude, Codex or Cursor. Add your project key to toolfare once; 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

TD

ThinkingData

Game and app metrics from your own TA/TE cluster

ST

Sensor Tower

App downloads, revenue and ad intelligence

AppLovin MAX

Estimated ad revenue by app, country and 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 ThinkingData sign-in: add your ThinkingData 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
5 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.

  • Your own metrics, over any window

    thinkingdata_query_metric

    Fetches up to ten of the metrics your team defined in ThinkingData over a recent or absolute window, grouped by up to three properties — the same numbers, with the same definitions, as in TA.

    • “What was DAU by country for the last 14 days?”
    • “Show day-1 retention by channel for last month.”

  • The metrics your team defined

    thinkingdata_list_metrics

    The business metrics defined in a project, with the time granularities each one supports.

    • “Which metrics are defined in our ThinkingData project?”
    • “Is there an ARPU metric we can query weekly?”

  • The events a project tracks

    thinkingdata_list_events

    Physical and virtual events tracked in a project, with their display names.

    • “What events do we track in this game?”
    • “Is there a purchase event, and what is it called?”

  • The properties behind an event

    thinkingdata_list_props

    Event or user properties of a project, optionally for one event — what you can group a metric by.

    • “What properties does the level_complete event have?”
    • “Which user properties can we group retention by?”

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 ThinkingData projects this workspace can readthinkingdata_list_projects
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