GA4 MCP server for Claude and Cursor (2026 guide)

A GA4 MCP server exposes Google Analytics 4 reporting APIs as MCP tools — run_ga4_report, run_ga4_realtime_report, run_ga4_funnel_report, and property metadata — so Claude or Cursor can answer questions about sessions, conversions, and revenue without you opening the GA4 UI.

What is a GA4 MCP server?

It is an MCP service that calls the Google Analytics Data API on your behalf using OAuth or a service account. Your AI client sees tools with JSON schemas; when you ask "How many organic sessions converted last week?", the model calls run_ga4_report with the right dimensions, metrics, and date range.

Google publishes an official reference implementation: google-analytics-mcp on GitHub. Community repos add convenience wrappers. Most are GA4-only — they do not also expose Search Console.

GenieSeo is different: one hosted MCP URL includes 7 GA4 tools and 21 Search Console tools after a single Google consent screen. That pairing is what lets you cross-reference clicks with conversions inside one chat.

GA4 MCP tools you should expect

Tool	Use case
`list_ga4_properties`	Discover property IDs (always call first)
`run_ga4_report`	Sessions, users, conversions, revenue by dimension
`run_ga4_realtime_report`	Last 30 minutes
`run_ga4_funnel_report`	Step funnels for organic or all traffic
`get_ga4_property_details`	Time zone, currency, industry
`get_ga4_custom_dimensions_and_metrics`	Custom definitions

Official GA4 MCP vs hosted GenieSeo

	Google analytics-mcp (OSS)	GenieSeo (hosted)
Setup	Cloud project + credentials	Google sign-in, paste URL
GA4 tools	Yes	Yes (7)
Search Console	No	Yes (21) on same URL
Clients	Claude Desktop / dev setups	Claude web, Cursor, Codex, Antigravity
Cross-reference SC × GA4	Manual two connectors	One URL, one OAuth

If your search intent is "mcp server google analytics", Google’s repo is the benchmark for developers. If your intent is "answer revenue questions using SEO landing pages", you need GA4 and Search Console in the same session — that is where a combined server wins.

Connect GA4 MCP to Claude (hosted path)

Sign up for GenieSeo with Google (grants GA4 analytics.readonly + GSC webmasters.readonly).
Create your MCP URL on the dashboard.
Paste into Claude → Connectors → Custom MCP.
Ask: "List my GA4 properties, then show organic sessions and conversions by landing page for the last 28 days."

For Cursor: Settings → MCP → Add server with the same URL.

Connect GA4 MCP to Cursor

Cursor uses the same Streamable HTTP URL as Claude:

{
  "mcpServers": {
    "genieseo": {
      "url": "https://seo.geniedial.in/mcp/u/YOUR_TOKEN"
    }
  }
}

Replace YOUR_TOKEN with the token segment from your dashboard. Never commit a real URL to git.

Example prompts once GA4 is connected

"Run a funnel for organic-search visitors: session_start → engagement → purchase."
"Which landing pages had high sessions but conversion rate below 1%?" → see recipe.
"Realtime: how many users are on site from organic search right now?"

Pair GA4 with Search Console (why one URL matters)

Search Console tells you who clicked. GA4 tells you what happened next. Separate MCP connectors force copy-paste between tools. One URL lets Claude join query → landing page → conversion in a single table — the workflow in Map top queries to GA4 conversions.