Ask your AI which keywords an app wins, and what its users hate.
App Store and Google Play keyword rankings, search volume, and review sentiment — answered inside ChatGPT or Claude. You need no AppTweak subscription and no API key of your own: Soku buys each call, tells your AI the price before it runs, and charges the credits the call actually reported.
Claude CodeCodexCursorVS CodeChatGPTClaude (web & desktop)Your own agent
Soku Connect
Sign in, grab the setup prompt from your console, paste it to your agent, ask something. That’s the whole setup.
Soku research stack
traffic, SEO, app-store and ads intelligence
AppTweak
App-store keywords, rankings and reviews
A
AppMagic
Mobile-game downloads, revenue, SDKs and ads
TikHub
Public posts and profiles across social platforms
200+
APIs
40+
apps
30+
skills
Ask once, let the agent choose the right source, and see the price before a paid data call runs.
No vendor keyQuoted per callOne research stack
The ask
New chatsoku · connected
Which keywords does this competitor app win in the App Store, and what are their users complaining about?
apptweak_app_keywordsAppTweak · Soku-suppliedcharged $0.0438 tracked terms; top 3 positions on 6 of them
apptweak_keyword_appsAppTweak · Soku-suppliedcharged $0.03You rank 14th on their strongest term; they are 2nd
apptweak_app_reviewsAppTweak · Soku-suppliedcharged $0.071-star reviews cluster on one thing: the export flow
They own the category term — you are 14th where they are 2nd — but their reviews say the same word over and over: export. The opening is not the keyword, it is the listing copy: their own users are describing the gap your app already closes.One store front and one country per call · store search volume is modelled, the stores publish none of it
Where this came from
Built-in — Soku buys itquoted first
AppTweak$0.14
3 calls$0.14
Illustrative figures. Every source, mark and price rule comes from the live Connect catalogue.
About five minutes
Set it up once, in the app you already use.
There is nothing to install for AppTweak specifically. One connection reaches every source in the catalogue, and this is one of them.
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.