Ask Claude about your GA4 data
GA4 is the tool people most want an assistant for, because it is the tool they most dislike opening. The interface asks you to know the name of the dimension before it will show you the number, and the exploration builder is a small BI product that most people learn twice and forget once. A google analytics mcp server sidesteps the vocabulary problem entirely: you ask which channels sent traffic last month, and something that has read the API documentation picks the dimension for you.
The connector URL
https://api.mevnix.com/mcp
The same URL for every source. Add it once in Claude; it carries whichever accounts you have connected.
Google has an official one, and it might be the right choice
Google publishes a GA4 MCP server. It is free, open source, and it works. If you are comfortable creating a Google Cloud project, enabling the Analytics Data and Admin APIs, installing the server with pipx and keeping a process running on your machine, you should genuinely consider using it — it is first-party and it costs nothing. Two things push people away from it. The first is that every step in that list is a step, and for most marketers the honest answer is that they will not finish. The second is that a local server is local: it runs where you installed it, so it works in the app on your laptop and not on your phone, and it stops working when the machine sleeps. Mevnix is a hosted URL, so setup is a consent screen and the connector follows your account rather than your hardware.
Sessions are only interesting next to something
A number from GA4 on its own is almost never the answer. Traffic went up nine per cent — against what? The month before, the same month last year, the week you increased spend? The six GA4 tools here are built around that: traffic overview, sources, top pages, conversions, realtime, and an explicit period comparison that returns both ranges and the change between them rather than making the assistant subtract two reports and hope. Realtime is the odd one out and worth knowing about — it answers "is anyone on the site right now", which is a different and much shorter question, and it is cached for sixty seconds rather than an hour for the obvious reason.
The question GA4 alone cannot answer
The reason to connect google analytics to claude through Mevnix rather than through a GA4-only server is that most real questions cross a boundary GA4 does not. "Did the ad spend increase actually move sessions" needs Meta Ads and GA4 in the same breath. "Are the pages getting impressions the ones converting" needs Search Console and GA4. Each of those is one question to an assistant holding all three, and three separate servers plus manual reconciliation otherwise. That is the whole design: one connector, one consent, the sources grouped per client so the assistant never blends two businesses together.
Setting it up
- Connect Google
One Google consent covers both Analytics and Search Console, so if you have already connected one you have connected both. Then choose which GA4 properties to expose.
- Add the connector to Claude
Add the Mevnix URL as a custom connector in Claude and approve the request. No Cloud project, no API enablement, no pipx, no local process — the difference from running a server yourself is this step being one step.
- Ask in your own words
You do not need to know that "session source / medium" is the dimension you want. Ask where the traffic came from and let the tool choose.
Free covers one source of each type. $9/month removes the limits, for as many clients as you like — see pricing.
Questions
- How is this different from the official Google Analytics MCP server?
- Google's is free, open source and runs on your own machine after you create a Cloud project and install it. Mevnix is hosted, so setup is a consent screen, it works from any device signed into your assistant, and it carries Search Console and Meta Ads in the same connector. If you only need GA4 and you are happy in a terminal, use Google's.
- Which GA4 metrics and dimensions can it reach?
- The reporting set most questions need: users, sessions, engaged sessions, conversions and revenue, by channel, source, medium, page, country and device, plus realtime active users. It reads the Data API, so it sees what your property has collected — it cannot fix a measurement gap that exists upstream.
- Can it change my GA4 configuration?
- No. Read scopes only, so creating an audience, editing a conversion event or changing a data stream are outside what it can do. That is a property of the permission we ask Google for, not a setting.
- Does it work with Universal Analytics?
- No — GA4 properties only. Universal Analytics stopped processing data in 2023 and its API is closed, so there is nothing left to read.
- Why do the GA4 numbers not match Search Console?
- Because they count different things, and neither is wrong. Search Console counts clicks it recorded on a result page; GA4 counts sessions its tag observed in a browser. Ad blockers, consent banners, immediate bounces and cross-device journeys all sit between the two. Chasing agreement between them wastes afternoons — compare each against its own history instead, which is the comparison that actually tells you whether something changed.
- What if I have several GA4 properties?
- Expose as many as you like on Pro and name the one you mean in the question. When only one is connected the tools resolve it implicitly; when several are, they refuse and list them rather than guessing, because silently answering about the wrong business is worse than asking. Filing each property under a client makes that unambiguous.
- Can Claude see individual users or personal data?
- No. The Data API returns aggregated reporting rows — counts by channel, page, country and so on — not user records, not client IDs and not anything identifying a person. Some rows may be withheld by Google itself when a segment is small enough that reporting it would risk identifying someone, and that thresholding happens upstream of us.