toolfare

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 toolfare once; your AI reads it with your own login, and 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, 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

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 chattoolfare · connected

Which landing pages lost the most traffic in the last 7 days — and who outranks them now?

Google Search Consolegsc_list_top_pagesSearch Console · your account0 credits/pricing −38%, /blog/attribution −22%
Google Search Consolegsc_query_search_analyticsSearch Console · your account0 creditsPosition 3.1 → 7.4 on “marketing attribution tool”
serpapi_requestLive search results · toolfare-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

  • Google Search ConsoleSearch Consolefree

Built-in — toolfare buys itquoted first

  • Live search results$0.03
3 calls$0.03

Illustrative figures. Every source, mark and price rule comes from the live toolfare catalogue.

About five minutes

Set it up once, in the app you already use.

Sign in to Google Search Console once from toolfare 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

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

  • 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

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