If you came here looking for the Google Analytics MCP, the short version first: Google has published MCP tooling for Google Analytics, and it does what you would expect — it lets an AI assistant query your GA4 property for sessions, users, events, and conversions without you opening a report.
It is genuinely useful. It also cannot answer a question most SaaS founders care about more: what is a visitor from this channel actually worth after they churn?
This post explains what a Google Analytics MCP covers, where it stops, and how a revenue analytics MCP differs. The goal is to help you pick the right one — or recognise that you need both.
What is a Google Analytics MCP?
A Google Analytics MCP is a Model Context Protocol server that lets an AI assistant query your GA4 data — sessions, users, traffic sources, events, and conversions — in natural language. Instead of building a report in the GA interface, you ask a question and the assistant runs the query.
It inherits GA4's model, which is built around behaviour: what people did on your site, in what order, arriving from where. That model is excellent for the questions it was designed for.
What it answers well
- How many sessions came from organic search last month?
- Which landing pages have the highest engagement?
- What is the conversion rate for a defined GA4 event?
- How did traffic change after a site redesign?
- Which countries and devices dominate my audience?
Where a Google Analytics MCP stops
GA4 knows what happened on your website. It does not know what happened in your billing system afterwards — unless you have built that connection yourself, which is neither simple nor common.
Four things it structurally cannot tell you:
- Revenue per channel, net of churn. GA4 can record a conversion event. It does not know that the customer cancelled in month three.
- MRR by acquisition source. Recurring revenue is a calculated metric over subscription state, not a website event.
- Which customers are at risk. Failed payments and paused subscriptions live in Stripe or Paddle.
- True customer lifetime value by source. This requires joining site data to billing data on a persistent identity.
A common mistake is treating a GA4 conversion event as revenue. A signup event fires whether that account becomes a $200-a-month customer or never pays at all. Optimising a channel on signup volume is how teams end up scaling their worst-retaining traffic.
Google Analytics MCP vs. revenue analytics MCP
| Google Analytics MCP | Revenue analytics MCP | |
|---|---|---|
| Core unit | Sessions, users, events | MRR, churn, subscribers, customers |
| Source of truth | GA4 property | Stripe / Paddle, synced |
| Answers "how many visitors?" | Yes, in depth | Yes, at a simpler level |
| Answers "how much MRR from this channel?" | No | Yes |
| Knows about churn | No | Yes |
| Knows about refunds and failed payments | No | Yes |
| Customer-level revenue | No | Yes, by processor ID |
| Best for | Site behaviour and content performance | Revenue decisions and channel ROI |
They are complements, not competitors
The honest framing is that these answer different questions. GA4 is a behavioural analytics system with far more depth on what people did on your site than any revenue tool will ever have — scroll depth, path analysis, content grouping, audience segments.
A revenue analytics MCP is deliberately narrower on behaviour and far deeper on money. Chartsy's server, for instance, exposes 18 read-only tools covering MRR, MRR by plan and country, churn per period, new subscribers, refund ratios, revenue concentration, at-risk customers, goal progress, and site traffic with signup rate by source — plus whole-business and single-day snapshots with derived warnings about concentration, churn spikes and refund ratios.
If you run a content site funded by ads, GA4's MCP is probably all you need. If you run a subscription business, the revenue side is where your decisions actually get made.
A worked comparison
Ask both systems: "Was our Product Hunt launch worth it?"
Google Analytics MCP returns sessions from the referral, bounce rate, pages per session, and how many fired your signup event. A complete picture of the traffic.
Revenue analytics MCP returns visits and signups for that source with signup rate, then the MRR and churn attached to the customers who came from it. A picture of whether it produced a business.
The first tells you the launch went well. The second tells you whether to do it again — the reasoning behind that join is in marketing attribution for SaaS revenue.
How to choose
Use this rough test:
- Your revenue is indirect (ads, affiliates, content) → a Google Analytics MCP covers most of what you need.
- Your revenue is subscriptions → you need revenue-side tooling; add GA4 for behavioural depth.
- You are making budget decisions between channels → you need the join between traffic and revenue, which only the revenue side provides.
- You are diagnosing on-site UX problems → GA4, every time.
If you would rather ask these questions in plain English than build reports, natural-language SaaS analytics vs. SQL covers the trade-offs.
Conclusion
A Google Analytics MCP is a real and useful tool, and if your questions are about site behaviour it is the right one. But for subscription businesses, the decisive questions are about money — what a channel returns after churn, which plan retains, where revenue concentration is building — and those live in your billing data, not your GA4 property.
If your questions have moved from how many visitors? to which of them are worth acquiring?, a revenue analytics MCP is the layer you are missing.
Compare what a revenue analytics MCP exposes →
Related reading
- What is an analytics MCP?
- Marketing attribution MCP: which channel actually pays you
- Stripe analytics MCP: why raw Stripe data isn't enough
Frequently asked questions
Does Google have an official MCP server for Google Analytics?
Google has published MCP tooling for Google Analytics that lets AI clients query GA4 data — sessions, users, traffic sources, and events — in natural language. Check Google's own developer documentation for current availability, setup steps, and supported properties.
Can a Google Analytics MCP show revenue by channel?
Only if you push revenue into GA4 yourself, and even then it reflects one-time transaction values rather than recurring revenue net of churn. It has no knowledge of subscription state, refunds, or failed payments.
Should I use both a Google Analytics MCP and a revenue analytics MCP?
Often, yes. They answer different questions: GA4 has far more depth on on-site behaviour, while a revenue analytics MCP knows what customers are actually worth. Subscription businesses generally need the revenue side to make budget decisions.
What is the difference between a conversion and a paying customer?
A conversion is a website event, such as a completed signup form. A paying customer is a billing state. Many conversions never pay, and some pay then churn within weeks — which is why optimising on conversions alone is misleading.
Which MCP should a SaaS founder connect first?
Start with the revenue side. Most SaaS decisions — pricing, channel spend, retention work — depend on subscription metrics that GA4 does not hold. Add a Google Analytics MCP afterwards when you need on-site behavioural detail.
Written by
Chartsy TeamThe Chartsy Team writes guides, product updates, and resources to help SaaS and eCommerce founders make sense of their metrics, without SQL or spreadsheets.
Chartsy
