Did the clicks become anything?

Read-only Analytics 4 over MCP: sessions, engagement, key events and revenue — including a bridge that puts them beside Search Console clicks for the same pages.

Search Console tells you what happened in the results. Analytics tells you what happened on the site. No tool that only reads the first can answer "this page gained clicks — did it convert?", which is usually the actual question.

Metrics
17
From activeUsers through totalRevenue and averagePageLoadTime.
Dimensions
17
Including landing page, channel group and campaign, so organic can be isolated.

Tools

2 tools on this source

ga4_get_report

Any GA4 report

Seventeen metrics across seventeen dimensions, with filters for page path and event name, and GA4 thresholding flagged explicitly.

ga4_get_search_conversion_bridge

Clicks to outcomes bridge

Puts Search Console clicks and GA4 sessions, key events and revenue for the same pages side by side, with the join limitation stated.

Before you start

What you need, and what you will not get

Requirements

  • The Analytics Data API enabled in your Google Cloud project.
  • At least one GA4 property the connected account can read.
  • Read-only Analytics scope, granted on the same consent screen as Search Console.

Boundaries

The limits worth knowing before you trust an answer.

  • Search Console and Analytics 4 cannot be joined at the user or session level without further identifiers. The bridge shows two columns side by side; it is not a conversion rate.
  • GA4 withholds or combines metrics when too few users were active. Those values are flagged and should not be trended.
  • Revenue is returned in the property currency, which the response names.

Endpoint

remote MCP endpoint
${env.appUrl}/mcp

Discovery metadata is served at /.well-known/mcp.json, so a client that supports it finds the endpoint from the domain alone.