# ThinkingData through toolfare

> 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 is free.

Page: https://toolfare.ai/thinkingdata

## Use it from your agent

Paste this into Claude Code, Codex, Cursor or any agent with a shell:

> Set up https://toolfare.ai/skill.md, then use toolfare to answer: What was DAU by country for the last 14 days?

Apps without a terminal connect toolfare as an MCP server: https://toolfare.ai/docs#connect

## Use it from a script

```sh
mkdir -p ~/.local/bin
curl -fsSL 'https://toolfare.ai/toolfare/toolfare.mjs' -o ~/.local/bin/toolfare
chmod +x ~/.local/bin/toolfare
export PATH="$HOME/.local/bin:$PATH"
export TOOLFARE_MCP_URL='https://api.toolfare.ai/mcp'
toolfare login
```

Then connect your ThinkingData account in the toolfare console (https://toolfare.ai/thinkingdata#setup); calls fail until it is connected.

Sign in once per machine; the CLI renews the sign-in itself. On a CI runner or another server, create an API key in the toolfare console and set it as `TOOLFARE_API_KEY` instead of signing in. Paid calls on one sign-in or key run one at a time. `--max-cost` refuses a call quoted above that many credits (1,000 credits = $3).

## Tools

### Your own metrics, over any window

Tool: `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.

Ask:
- What was DAU by country for the last 14 days?
- Show day-1 retention by channel for last month.

### The metrics your team defined

Tool: `thinkingdata_list_metrics`

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

Ask:
- Which metrics are defined in our ThinkingData project?
- Is there an ARPU metric we can query weekly?

### The events a project tracks

Tool: `thinkingdata_list_events`

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

Ask:
- What events do we track in this game?
- Is there a purchase event, and what is it called?

### The properties behind an event

Tool: `thinkingdata_list_props`

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

Ask:
- What properties does the level_complete event have?
- Which user properties can we group retention by?

### Also available

- `thinkingdata_list_projects`: The ThinkingData projects your toolfare account can read

## Price

Free to read: it is your own account, so toolfare pays nobody for the data and charges nothing per read. No per-read charge to observe. Reads need no purchase. Like every toolfare call, they run only while your balance holds at least $0.003, and that is not spent.

Balances and top-ups are in US dollars. Quotes and `--max-cost` count credits: 1,000 credits = $3 ($0.003 each).

## Use it when

- You want a KPI your team already defined in ThinkingData, without opening TA.
- You want a metric broken down by country, channel or another property.
- You want to know which events and properties exist before asking a harder question.

## Look elsewhere when

- You need ad-hoc SQL. SQL runs only after a person reviews it, and that step is not published through the MCP connection.
- You want installs and attribution by media source. That is your attribution account.

## Limits

- The cluster is your own: every call spends its compute and shares a conservative per-connection quota.
- Times follow the project’s time zone, not UTC.
- Metric queries take no global filters in this version; narrow them with grouping instead.
- Older TA 3.x clusters may not expose metric listing.