Does LLM Pulse have a Google Search Console MCP server?

Yes. LLM Pulse runs a hosted MCP server that exposes your connected Search Console property through tools such as get_search_console_queries and get_search_console_pages, alongside your AI visibility data. Any MCP client can read it over OAuth.

What Search Console data can an AI assistant read?

Clicks, impressions, CTR and average position as headline totals or a daily time series, plus your top queries and pages, with optional country and device breakdowns.

Do I need an API key?

No. Connections use OAuth 2.1, so you add one URL, sign in once, and tokens refresh automatically. API keys are only for headless setups on Scale and above.

Which plan do I need?

The MCP server is on every plan. The Search Console tools need a connected property and are available on Growth and above.

Which AI clients work?

Any MCP-compatible client, including ChatGPT, Claude, Gemini, Cursor, Windsurf, Zed and custom agents.

Can I combine Search Console with AI visibility?

Yes, that is the point. Because both live behind the same MCP endpoint, one assistant can compare your Google search performance with how AI models mention and cite you.

Google Search Console over MCP

Bring Google Search Console into any AI assistant with MCP

Follow new features, improvements, and fixes across LLM Pulse.

Start Free Trial

14-day free trial

Cancel anytime

Connect your AI client

Paste this URL into your AI client's MCP or connectors settings, then sign in to LLM Pulse. Your Search Console tools appear once a property is connected.

ChatGPT / Claude / Gemini Add this URL as a custom connector in your AI client

https://api.llmpulse.ai/api/v1/mcp

Cursor / Windsurf / Zed Add to your IDE's MCP server settings

https://api.llmpulse.ai/api/v1/mcp

Connect to

MCP Endpoint

Features

Your Search Console data, answerable in plain language

Your Search Console property becomes answerable in plain language, and it lives next to the AI visibility data that classic analytics cannot see.

Top queries and pages

Ask for your best and worst performing queries or pages over any range, ranked by clicks, impressions, CTR or average position.

Clicks and impressions over time

Pull the daily time series for a property and spot the days search traffic moved, without opening the Search Console UI.

Country and device breakdowns

Slice your headline totals by country or device to see where your search demand really comes from.

Search next to AI visibility

Search Console sits beside your mentions, citations and share of voice, so one assistant compares classic search with AI answers in the same thread.

OAuth, no API key

Connect once with OAuth 2.1. Your assistant stays linked, tokens refresh on their own, and you can revoke access anytime.

Works in every client

ChatGPT, Claude, Gemini, Cursor, Windsurf and custom agents all read the same endpoint.

Search Console tools

What an agent can read from Search Console

These read tools map to your connected Search Console property. They need a Search Console connection on Growth and above.

Headline performance

get_search_console_summary
Impressions, clicks, CTR and average position for a property over any range, with optional country or device breakdown.
get_search_console_timeseries
The same metrics day by day, ready to chart or summarize.

Queries and pages

get_search_console_queries
Top search queries with clicks, impressions, CTR and position.
get_search_console_pages
Top landing pages with the same metrics, to see which URLs earn your search clicks.

Cross with AI visibility

Compare classic search with AI answers in one conversation.

get_timeseries
Mentions, visibility, citations and sentiment over time, for you and competitors.
get_sov
Share of Voice against your competitors in AI answers.
get_top_sources
The domains AI models cite most, to compare with the pages that rank in Search.

Connect Search Console in a few clicks

Connect your property to LLM Pulse, then point any AI client at the MCP endpoint.

1

Connect your Search Console property

In LLM Pulse, connect Google Search Console to your project. This powers both the dashboard and the MCP tools.
2

Add the MCP URL to your AI client

Paste https://api.llmpulse.ai/api/v1/mcp into the connector or MCP settings of ChatGPT, Claude, Gemini or Cursor.
3

Sign in once with OAuth

Approve access in the browser window your client opens. No API key to copy, tokens refresh automatically.
4

Ask about your search data

Request top queries, losing pages or the clicks time series, and compare them with your AI visibility in the same thread.

What you can do with Search Console over MCP

From a quick question to a fully automated workflow, Search Console over MCP turns your search data into something any assistant can read and act on.

Search vs AI answers

Ask which queries you rank for in Google but are missing from AI answers, so you know where GEO work pays off.

Automated search reports

Have an agent assemble a weekly Search Console summary, top movers and a visibility readout in one brief.

Spot traffic drops

Let an assistant watch clicks and average position and flag the queries and pages that slipped.

Content opportunities

Find pages with high impressions but low CTR, then brief or draft an improvement with GEO Writer in the same conversation.

"After noticing rising visits from various LLMs in GA4, we needed visibility into those black boxes: which models were mentioning us, in which answers, and how that was changing over time. LLM Pulse gave us the clarity to understand our brand's evolution across AI models and to shape new strategies to boost our exposure."

Victor Hernández

Casa Batlló

Frequently Asked Questions

Everything you need to know about connecting Google Search Console to AI agents over MCP.

: Yes. LLM Pulse runs a hosted MCP server that exposes your connected Search Console property through tools such as get_search_console_queries and get_search_console_pages, alongside your AI visibility data. Any MCP client can read it over OAuth.
: Clicks, impressions, CTR and average position as headline totals or a daily time series, plus your top queries and pages, with optional country and device breakdowns.
: No. Connections use OAuth 2.1, so you add one URL, sign in once, and tokens refresh automatically. API keys are only for headless setups on Scale and above.
: The MCP server is on every plan. The Search Console tools need a connected property and are available on Growth and above.
: Any MCP-compatible client, including ChatGPT, Claude, Gemini, Cursor, Windsurf, Zed and custom agents.
: Yes, that is the point. Because both live behind the same MCP endpoint, one assistant can compare your Google search performance with how AI models mention and cite you.

More ways to integrate LLM Pulse

MCP Server

The full MCP server with read and write tools for AI visibility.

Google Analytics over MCP

Measure AI traffic with GA4 and read it next to your visibility.

Web Analytics Integration

Blend AI visibility with GA4, Plausible, PostHog and more.

API Access

The same data and actions exposed as a documented REST API.

GEO Optimization

Turn search and AI gaps into a prioritized action plan.

From the blog

Developers

API and MCP reference

Full documentation for the REST API and Model Context Protocol server.

Integrations

Web analytics integration

Connect GA4, Adobe, PostHog, Plausible and Piano to measure AI traffic.

Pricing

See pricing and plans

Search Console connections are available on Growth and above.

Ready to query Search Console with AI?

Connect your property and point any AI assistant at LLM Pulse over MCP. Free on every plan, Search Console tools on Growth and above.