Google Analytics MCP server: GA4 beside store and revenue

Google Analytics 4 answers one question well: who came to the site and what they did there. The question people bring to an AI assistant is usually the next one: did those visits turn into orders, subscribers or better rankings? That answer sits in other accounts, your store, Stripe or RevenueCat, Search Console. An MCP server lets the assistant read GA4 directly; which server you pick decides whether it can read the rest too.

Two ways to connect Google Analytics to an AI assistant

	HeyMetra	Google’s official server
Where it runs	Hosted: one web address	On your own computer
Setup	Paste one address, sign in with Google	Python, a Google Cloud project, two APIs, credentials, a config entry
Assistants	Claude, ChatGPT, Grok, Perplexity, Claude Code, Codex, Cursor, Antigravity	Assistants that start local servers, such as Claude Code
Accounts in one answer	GA4 with your store, Search Console, subscriptions, CRM	Google Analytics only
Team	Shared with your workspace	Each person installs their own
Status	GA4 on the way; other connectors live	Experimental

What you can ask when GA4 sits beside your other accounts

Google Analytics on its own can answer the first half of each of these. The second half needs the account next to it:

• GA4 with your store: which landing pages bring visitors who go on to order, and what those orders were worth.
• GA4 with Search Console: which searches bring sessions that actually engage, not just clicks.
• GA4 with RevenueCat or Adapty: whether the campaigns that brought the most sign-ups also brought paying subscribers.
• GA4 on its own: which channels brought the most key events this month, and where people leave the sign-up funnel.

Each answer comes back in the assistant you already use.

How HeyMetra connects

1. Connect the accounts once in HeyMetra. Google accounts connect with a Google sign-in; your store or subscription platform with its own key.
2. Add HeyMetra to your assistant. One address, https://mcp.heymetra.com/mcp, in Claude’s or ChatGPT’s settings, or one command in Claude Code.
3. Ask. Your assistant reads what the question needs from each account and answers in the chat.

GA4 is the connector still on the way. Until it opens, the same connection already reads Search Console, WooCommerce, Amazon, Stripe, RevenueCat, Adapty and more, and the Google Analytics 4 page has a button to be told the day it opens.

If you want Google’s official server today

Google publishes an experimental Google Analytics MCP server, analytics-mcp. It reads accounts and properties, runs standard, funnel and realtime reports, lists custom dimensions, and with a write flag can add an annotation. It needs:

• Python’s pipx;
• a Google Cloud project with the Google Analytics Admin API and Data API switched on;
• Application Default Credentials with the scope https://www.googleapis.com/auth/analytics.readonly.

Then, in Claude Code:

claude mcp add analytics-mcp \
  --scope user \
  -e "GOOGLE_APPLICATION_CREDENTIALS=PATH_TO_CREDENTIALS_JSON" \
  -e "GOOGLE_PROJECT_ID=YOUR_PROJECT_ID" \
  -- pipx run analytics-mcp

It is a good fit for one person in a terminal asking about Google Analytics alone. For a team, for ChatGPT or Claude on the web, or for questions that reach past Google Analytics into orders and revenue, a hosted server that holds the other accounts too is the shorter path.