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 Soku once; every read costs 0 credits.
Claude CodeCodexCursorVS CodeChatGPTClaude (web & desktop)Your own agent
Soku Connect
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
ThinkingData
Game and app metrics from your own TA/TE cluster
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 Soku once. After that, every AI app you approve reads it through the same connection.
Claude Code
One sign-in covers every project, and headless runs (`claude -p`, CI, the Agent SDK) work without a browser — `claude mcp add` only writes config, so a non-interactive run can never finish the MCP authorization. Both surfaces can act on your accounts once you approve each change.
1
Create your Soku workspace
The connection is public and identical for everyone — your Soku 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, Soku asks you to approve the access and names the workspace it will read through — so the workspace has to exist by then.
Already have one? Nothing to do here — sign in when the connection asks for it.
2
Copy the Soku MCP connection
https://api.soku.ai/mcp
3
Add it to Claude Code
claude mcp add --transport http soku https://api.soku.ai/mcp
Run the command in any project. It writes the configuration and prints an `Added …` line.
Authorize separately — adding a server does not open a browser.
Run `claude mcp list` to confirm the server reads `✔ Connected`.
4
Approve the access, then ask it something
Inside Claude Code, run `/mcp` and follow the browser flow — or, from your shell, `claude mcp login soku`.
The Soku consent page names the host, the workspace the grant will read through, and what the connection will be able to do.
Approving creates the grant listed above on this page. Cancelling creates nothing.
On a machine with no browser (SSH, headless Linux), `claude mcp login soku --no-browser` prints the URL and takes the pasted callback.
Paste this first
Using Soku, 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.
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
Choose the Soku plan for your research and agent workflow.
Start free, upgrade when your team needs more credits, more brands, or deeper workflow execution.