Ask your AI which queries you are losing, and why.
The queries and pages that earn your organic clicks, average position day by day, any breakdown by query, page, country or device, and how Google sees a single URL — answered inside ChatGPT, Claude, Codex or Cursor. Connect your Search Console property to Soku once; your AI reads it with your own login, and every read costs 0 credits.
Claude CodeCodexCursorVS CodeChatGPTClaude (web & desktop)Your own agent
Soku Connect
Sign in, connect the account once, paste the setup prompt to your agent, ask something. That’s the whole setup.
Your accounts, one connection
ads, analytics, commerce and revenue
Google Search Console
Organic queries, rankings and index status
TikTok Ads
Spend, results, Smart+ and GMV Max reporting
Google Ads
Campaigns, keywords and search terms
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
The ask
New chatsoku · connected
Which landing pages lost the most traffic in the last 7 days — and who outranks them now?
gsc_list_top_pagesSearch Console · your account0 credits/pricing −38%, /blog/attribution −22%
gsc_query_search_analyticsSearch Console · your account0 creditsPosition 3.1 → 7.4 on “marketing attribution tool”
serpapi_requestLive search results · Soku-suppliedcharged $0.033 new results above you, all published in the last 10 days
You did not lose traffic — you lost position 3. Three pages published in the last ten days now sit above /pricing, and all three cover the comparison angle yours does not.
Where this came from
Your connected accounts0 credits
Search Consolefree
Built-in — Soku buys itquoted first
Live search results$0.03
3 calls$0.03
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.
Sign in to Google Search Console once from Soku to connect it. After that, every AI app you approve reads it through the same connection, with nothing to install for Google Search Console itself.
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.
The searches that bring people in
gsc_list_top_queries
Top Google queries for a date range with clicks, impressions, click-through rate and average position.
“What did people search to find us last month?”
“Which queries get impressions but almost no clicks?”
The pages that earn organic clicks
gsc_list_top_pages
Every URL with organic impressions and clicks over a date range, sorted by clicks, with its average position.
“Which pages get the most clicks from Google?”
“Which of our pages lost the most clicks this week?”
Any breakdown, with filters
gsc_query_search_analytics
Search performance grouped by any mix of query, page, country, device and date, filtered however you need — only branded queries, only one country, image search instead of web.
“Which queries does our pricing page rank for, by country?”
“Show non-branded query clicks by device for the last 28 days.”
Clicks and position, day by day
gsc_get_daily_trend
A daily series of clicks, impressions, CTR and position for the property — the shape of a drop, with a date on it.
“When did our organic clicks start falling?”
“Chart our average position over the last three months.”
How Google sees one URL
gsc_inspect_url
Whether a page is indexed and why not, the canonical Google chose, the last crawl, mobile usability and rich-result status.
“Is this page indexed, and if not, why?”
“Which canonical did Google pick for this URL?”
Whether your sitemaps are healthy
gsc_list_sitemaps
Submitted sitemaps with their status, warnings, errors, and submitted against indexed counts.
“Do any of our sitemaps have errors?”
“How many submitted URLs are actually indexed?”
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 Search Console properties this workspace can readgsc_list_sites
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.