Google Search Console MCP: free for any AI agent

Updated November 7, 2026

A free Sightkick account, no card, lets any AI agent read your Google Search Console data. Connect Search Console once in Sightkick, under Settings → Search Console, and every agent on Sightkick's MCP server reads it, next to how AI answers name your brand. Sightkick isn't a standalone Search Console MCP server.

Disclosure: this page is made by Sightkick, about Sightkick's own Search Console connection. The other tools in the comparison are described from their own pages.

Key takeaways

• You connect Search Console to Sightkick once. Your agent signs in to Sightkick, never to Google, and holds no Google credential.
• A free account reads Search Console at the same limits as a plan: up to 180 days, live queries of up to 1,000 rows, exports of up to 5,000.
• Next to Google's numbers, Sightkick shows how AI answers name your brand, which a plain Search Console server can't.
• Agents without MCP read the same data with an API key, through the CLI or the HTTP API.

How do I connect Search Console to my agent through Sightkick?

Make a free Sightkick account, connect Search Console in Settings → Search Console, then connect your agent to Sightkick's MCP server at https://app.sightkick.so/mcp. The Google sign-in is the one step only you can do. The agent steps for each client are in Sightkick's MCP setup.

1. Have a Sightkick account for the site. The free account is enough: sign up at sightkick.so/free-ai-visibility-report, no card. It also gets you a one-time AI visibility report. To start a plan instead, begin at app.sightkick.so/start with the 7-day trial.
2. Connect Search Console, once. In Sightkick, open Settings → Search Console and click Connect. Signing in to Google is one of the few things an agent can't do for you.
3. Connect your agent to Sightkick's MCP server. One endpoint for every client, streamable HTTP, OAuth 2.1, no API key. In Claude Code:

   claude mcp add --transport http sightkick https://app.sightkick.so/mcp

   Other agents have their own steps: Codex, Hermes Agent, OpenClaw, Claude, ChatGPT, Grok Bot and Muse. Any other agent: add a remote MCP server at https://app.sightkick.so/mcp, transport streamable HTTP, auth OAuth. The sign-in picks the workspace for your site.
4. Check it. Ask your agent to call get_workspace, which returns the workspace's setup and connections and what setup still lacks. Then ask for get_settings search_console, which says whether Search Console is connected, the property and any sign-in error, and get_search_console with view metrics.

Agents without an MCP client, such as a cron job or a CI step, use an API key from Settings → Agents with the CLI or the HTTP API. The same Search Console reads, as JSON or a CSV:

sightkick gsc --days 28
sightkick gsc export --days 28 --csv > rows.csv

Run either with npx -y sightkick in place of sightkick, or install the CLI once with npm install -g sightkick.

What does Sightkick read from Search Console?

Sightkick reads the Search Console property of the workspace's website, syncs it daily and gives your agent clicks, impressions, CTR and position by query and page. The first sync brings the last 28 days. Your agent reaches the data through get_search_console and check_web:

• Performance. Clicks, impressions, CTR and position over up to 180 days, against the period before (get_search_console metrics).
• Any slice. By query or by page, a page's detail or one search's detail (query and detail).
• Live queries. The query view filters by query or page and asks Google live, up to 1,000 rows.
• The export and sitemaps. Up to 5,000 rows a call, and the sitemaps submitted, with when Google read each (export and sitemaps).
• Indexing checks. check_web index says whether a page is in Google's index and why not, plus site checks: whether Google and AI bots can reach you, and which pages fell out.

A free account reads at the same limits as a plan (Sightkick's connect guide). The one exception is the searches view, which runs on keyword research and so needs an active plan.

One workspace is one website, and an agent's sign-in reaches only the workspace picked on the consent screen. Google's Search Analytics API returns the top rows, not every row (Google), so the far end of a long tail is partial in any tool built on it, Sightkick included. Filter by page or query to get closer.

What can my agent do with Search Console data in Sightkick?

Your agent can report the 28-day trend, find pages Google shows and nobody clicks, pull every search behind one page, and match Google demand against AI answers. Each job below has a prompt to paste into any connected agent, and what came back on sightkick.so, Sightkick's own site.

The numbers are our own. Method: the sightkick.so workspace in Sightkick, read on 4 November 2026, with Search Console over the 28 days from 2026-10-07 to 2026-11-03. Jobs 1 to 3 run on a free account. Job 4 needs a plan, for keyword research and daily tracked prompts.

1. What changed in the last 28 days?

Use Sightkick's Search Console data: clicks, impressions and average position for the last 28 days against the 28 days before. Which page grew most?

On sightkick.so: 14 clicks and 5,544 impressions at an average position of 29.0. The 28 days before: 5 clicks, 3,805 impressions, position 53.0. The top page by impressions was /blog/am-i-on-ai, with 1,472 impressions, 8 clicks and position 9.3.

Worked out from those numbers: impressions rose 46%, the average position moved 24 places up, and the click-through rate went from 0.13% to 0.25%. That is still low, because an average of 29.0 is page three. The trend an agent should report is "seen more, still rarely clicked", not "growing".

2. Which pages does Google show that nobody clicks?

From Sightkick's Search Console data, list our pages with impressions but no clicks in the last 28 days, with their positions. For each, say whether the fix is the title, the answer in the first paragraph, or a better page.

On sightkick.so, three pages stood out: /blog/best-llm-optimization-service-ai-products (606 impressions, position 53), /blog/best-ai-search-visibility-tools-2026 (574, position 23.6) and /blog/seo-competitor-analysis (462, position 34.5). Together they held 1,642 impressions, 30% of the site's, with no click. We acted on the first: it answered the same buyer question as the tools list, so we merged it into that page and its address now redirects there. On a plan with the site connected for publishing, your agent can edit any live page at any age. Each edit carries a reason, needs the page's current version, and can be undone.

3. Which searches bring one page its traffic?

Run a live Search Console query in Sightkick for the page /blog/am-i-on-ai: every search it showed for in the last 28 days, with clicks, impressions and position.

The query view filters to that page and asks Google live, up to 1,000 rows. On sightkick.so, that one page carried 1,472 of the site's 5,544 impressions, 27% of the total, and 8 of its 14 clicks. Its click-through rate, 0.54%, is about twice the site's, the pull of a position near 9 against one near 29.

4. Where does Google show demand that AI answers ignore?

Find topics where Google shows demand and AI answers don't name us. Check the keyword's volume in Sightkick, our tracked prompts on the same topic, and whether we already have a page.

On sightkick.so, "google search console mcp" came back at 480 searches a month and rising (110 a year ago, 1,000 last month), difficulty 17. The tracked prompt "Is there an MCP server that connects Google Search Console to Claude?" named Sightkick in 0 of 4 answers over 30 days. That is the combined view a Search Console server alone can't give: Google demand and AI answers for the same topic, side by side. This page is our answer to it.

How does Sightkick compare with other Search Console MCP options?

A plain Search Console MCP server gives your agent Google's numbers, and Sightkick puts them next to AI answers and the work that follows. Pick a self-hosted server for raw data across properties at no cost, Composio if your agent already uses it for other apps, and Sightkick for Search Console next to AI visibility.

Sources, read 4 November 2026: Sightkick's connect guide, mcp-gsc on GitHub, Composio's toolkit page, Advanced GSC's MCP page.

On cost: Sightkick's free account reads Search Console with no card, and plans start at $39 a month. mcp-gsc is free to run yourself. Composio's free Hobby plan covers 100,000 tool calls a month, up to 20,000 of them for Search Console. Advanced GSC charges $15, $40 or $105 a month, by number of properties and seats.

Is it safe?

Yes. Search Console stays connected to Sightkick, not to each agent. Your agent signs in to Sightkick with OAuth, and its grant is bound to one workspace, picked on the consent screen, so it can't read another site's data.

• Every call is attributed. Each one lands in Sightkick's activity feed against the client that made it.
• What stays yours. Signing in to Google, signing in to Sightkick, entering the first card, ending a trial early (Start my plan now) and deciding who gets access.
• Destructive actions are marked. Deleting something, taking a page down and sending an email. Agent edits to live pages are kept and can be undone.
• Keys are scoped. An API key carries only the permissions you tick: read, write, spend, publish, send. A key for reporting only needs read. Revoke it under Settings → Agents.

For a human gate on the work that follows the data, set Sightkick's jobs to Manual and have the agent write drafts only: a page with no day waits in Unscheduled. More in Sightkick's MCP safety notes.

Troubleshooting

Why does get_workspace list Search Console as missing?

Search Console isn't connected yet. The person who owns the Google account opens Settings → Search Console in Sightkick and clicks Connect. An agent can't do the Google sign-in, but it can call get_settings search_console for the owner's link and any sign-in error.

Why does every tool say the connection isn't tied to a Sightkick workspace?

The agent's sign-in finished before the new account's workspace existed. Finish the setup at app.sightkick.so/start, then reconnect: run the sign-in again (in Claude Code, /mcp), or remove the server and add it back.

Why doesn't the agent list Sightkick's tools?

Sightkick lists its tools without a sign-in, so look at the client. Claude Code: restart it if sightkick isn't under /mcp. Codex connects at the start of its next task.

What if the agent runs where nobody can open a browser?

Use an API key from Settings → Agents, kept in SIGHTKICK_API_KEY, out of code and commits, with the CLI or the HTTP API.

Why does a query stop at 1,000 rows?

That's the live query's ceiling. Narrow it with a page or query filter, split the date range, or take the export, which holds up to 5,000 rows a call.

Why does the searches view say it needs a plan?

That view runs on keyword research, which comes with Standard and Pro. Every other Search Console read works on a free account.

FAQ

Is Sightkick a Google Search Console MCP server?

Not a standalone one. Sightkick is the agentic SEO and GEO platform. Search Console is one of its data sources, and its MCP server gives your agent that data next to AI visibility, keywords and publishing.

Which agents can read Search Console through Sightkick?

Any MCP client over streamable HTTP, including Claude Code, Claude, ChatGPT, Codex, Grok Bot, Muse, Hermes and OpenClaw. Agents without MCP use the CLI or the HTTP API with a key.

Is it free?

Yes, to read Search Console. A free account, no card, can connect Search Console, and its agent reads it over MCP or with an API key, at the same limits as a plan. The searches view needs a plan.

What does a plan add, and what does it cost?

Daily AI visibility tracking, keyword research, publishing and outreach. Standard is $39 a month ($31 billed yearly), and Pro is $99 a month ($79 billed yearly) with 30 articles a month by Sightkick. Both start with a 7-day trial: a card, nothing charged for 7 days, and cancelling in time costs nothing.

Does my agent need a Google Cloud project or a service account?

No. The Google sign-in happens once in Sightkick, and your agent signs in to Sightkick with OAuth. There's no Google credential for the agent to hold.

How fresh is the data?

Sightkick syncs Search Console daily, and the first sync brings the last 28 days. The newest days are provisional. The query view asks Google live.

Can I connect several Search Console properties?

A workspace is one website, so it reads one property for that site. Your agent can list the owner's properties that cover the site with get_settings search_console_properties, and switch with update_connections pick_property. Switching drops the old property's data.

Can my agent check whether a page is indexed?

Yes: check_web index, 50 a day, and Sightkick's site checks report which pages fell out.

Next

• Sightkick's MCP server: tools, clients, limits
• Pricing: Standard, Pro and the trial
• Free AI visibility report: how AI search answers your buyers' questions, no card
• Claude Code + Sightkick
• Hermes Agent + Sightkick
• WordPress + Sightkick