zaDojoGoogle Analytics MCP: free GA4 data for AI agents
Connect Google Analytics 4 to Claude, ChatGPT, Cursor or Codex without a Google Cloud project. Thirteen read-only tools, and GA4 reads use no credits.
zaDojo's MCP server lets your AI agent read your Google Analytics 4 property: visitors, sessions, page views, bounce rate, key events and revenue, split by channel, page, country, city, device or browser, plus who is on the site right now. You connect GA4 inside zaDojo with a normal Google sign-in, so there is no Google Cloud project, API to enable or credentials file. Reading Google Analytics uses no credits, and the same data shows up as a dashboard in the zaDojo app. For what an agent can do once it has data like this, see SEO agents.
Connect it in three steps
- Create a zaDojo account and a project for your site. Signing up needs no card.
- In the project, open My Site > Analytics and connect Google Analytics. Sign in with a Google account that can see the GA4 property, approve read-only access and pick the property.
- Add the server URL below to your AI client and approve the zaDojo login the first time it connects.
https://app.zadojo.com/mcpClaude Code
claude mcp add --transport http --scope user zadojo https://app.zadojo.com/mcpCodex CLI
codex mcp add zadojo --url https://app.zadojo.com/mcpCursor: add this to mcp.json under Settings > Tools & Integrations > MCP Tools.
{
"mcpServers": {
"zadojo": {
"url": "https://app.zadojo.com/mcp"
}
}
}Claude Desktop: open Customize > Connectors, choose Add custom connector and paste the URL.
ChatGPT needs a custom connection; the ChatGPT guide lists the steps and the plans that support it. Other clients that support remote MCP servers take the same URL, and the MCP setup guide covers each client.
What your agent can read
Each tool answers one kind of question, so your agent picks the right report from your question instead of building a GA4 query from scratch.
| Your question | Tool |
|---|---|
| How is the whole site doing compared with the previous period? | get_google_analytics_traffic_overview |
| Which countries, regions, cities, browsers or sources lead? | get_google_analytics_breakdown |
| How many people are on the site right now? | get_google_analytics_realtime_users |
| Is organic search traffic growing? | get_google_analytics_organic_overview |
| Which pages bring in organic visitors? | get_google_analytics_organic_landing_pages |
| Which pages get read, and for how long? | get_google_analytics_page_performance |
| Which channels, sources or campaigns send sessions? | get_google_analytics_traffic_acquisition |
| Which key events happen, and after which landing pages? | get_google_analytics_key_events |
| Which products and landing pages earn revenue? | get_google_analytics_ecommerce_performance |
| What do visitors search for on the site? | get_google_analytics_site_search |
| Which devices and countries, and how many returning visitors? | get_google_analytics_audience_breakdown |
| Is tracking set up correctly? | get_google_analytics_measurement_health |
| Which pages near page one are worth improving? | get_search_opportunities |
Traffic overview and breakdowns
The traffic overview covers every channel. It returns visitors (GA4's active users), sessions, page views, bounce rate, average session duration, key events and purchase revenue, each compared with the previous period of the same length, plus a day by day trend.
Both the overview and the breakdown take the same filters: channel, source, campaign, landing page, page, country, region, city, device, browser and operating system. Filters combine, so one question can narrow the numbers to "mobile visitors from Germany who came from Google". The breakdown lists the top 50 values of one of those dimensions, which is how an agent drills from countries to the cities inside one country.
Search Console and GA4 together
If the project also has Search Console connected, get_search_opportunities joins the two. It takes pages ranking in positions 4 to 20 in Search Console, matches them with their GA4 sessions and key events, and scores them by demand, business value and how close page one is. Pages GA4 has no data for stay in the list, unscored. To browse the Search Console side on its own, the Search Console dashboard guide compares three free views.
The same data as a dashboard
You do not need an agent to see the numbers. Once GA4 is connected, My Site > Analytics in the zaDojo app shows:
- seven headline numbers (visitors, sessions, page views, bounce rate, average session, key events and revenue), each with the change against the previous period;
- a daily chart for whichever of those numbers you pick;
- four panels: Sources (channel, source, campaign), Pages (landing page, page), Locations (country, region, city) and Devices (device, browser, operating system);
- a live count of visitors on the site in the last 30 minutes, refreshed every minute.
Click any row, a country or a browser for example, and the whole page narrows to it. Filters stack, and you can pick the last 7, 28 or 90 days, the last 12 months or your own dates. Viewing the dashboard uses no credits.
Example questions for your agent
- "How did mobile traffic from Germany change over the last 7 days compared with the week before?"
- "Which US cities sent the most visitors this month?"
- "Which landing pages bring organic visitors who go on to sign up?"
- "Is anyone on the site right now?"
- "Which pages rank on page two in Search Console and already convert in GA4?"
- "Is site search tracking switched on, and which key events are set up?"
To turn answers like these into a monthly report, give the agent an outline such as this SEO report template.
What it costs
Google Analytics reads use no credits, however many questions you ask, and the dashboard is free to view. You can connect GA4 on a new account without entering a card.
The same MCP connection also serves zaDojo's paid research tools, such as keyword research (about €0.07 a search), backlinks and rank tracking. Those draw on credits: the plan is €10 a month and includes €10 of usage. Each tool's description says whether it uses credits, so your agent can tell the two apart.
Read-only by design
zaDojo asks Google for the analytics.readonly scope. Your agent can read reports. It cannot change settings, edit key events, add users or touch your tracking code. You can disconnect in zaDojo at any time, or remove zaDojo's access from your Google account settings.
How it compares with Google's own MCP server
Google publishes an open-source Google Analytics MCP server, marked experimental. It runs on your own computer with Python, and you set it up yourself:
- Create or pick a Google Cloud project.
- Enable the Google Analytics Admin API and Data API.
- Set up credentials with the
analytics.readonlyscope, through an OAuth client or a service account. - Point the server at the credentials file and your project ID.
| zaDojo MCP | Google's Analytics MCP server | |
|---|---|---|
| Where it runs | Hosted, one URL | On your computer (Python) |
| Google Cloud setup | None, you sign in with Google | Project, two APIs and a credentials file |
| Tools | 13 tools, each for one kind of question | General tools such as run_report |
| Realtime | Visitors in the last 30 minutes | Yes, through run_realtime_report |
| Search Console join | Yes | No |
| Cost | GA4 reads use no credits | Free and open source |
Google's server is the better pick if you want everything on your own machine, or you need reports zaDojo does not offer, such as funnels or custom dimensions. zaDojo suits people who want their GA4 data in the agent today, next to Search Console, keyword and ranking tools, with nothing to install. Other SEO servers are compared in the best SEO MCP servers.
Limits to know
- Reports cover complete days only. Ranges end on yesterday, in your property's time zone.
- Google withholds or samples some data for privacy. When it does, the tools mark the report as limited, and rows that are missing are unknown, not zero.
- Breakdowns return the top 50 values. Custom date ranges can cover up to 366 days.
- Filters match exactly. Countries use two-letter codes such as DE, and the safest values to filter on are the ones a breakdown returned.
- The realtime count covers the whole site and takes no filters.
- There are no demographics, user-level data or custom dimensions.
- GA4 properties only. The Google account you connect needs access to the property.
- Google limits how much reporting each property can run per hour and per day. Reports show the quota left when Google sends it. If the quota runs out, the tools return an error instead of partial numbers, with a retry time when Google gives one.
Questions people ask
Do I need a Google Cloud project?
No. You sign in with Google inside zaDojo and approve read-only access. zaDojo handles the API connection.
Does reading Google Analytics use credits?
No. Google Analytics and Search Console reads use no credits, in the app and through your agent.
Can the agent change anything in Google Analytics?
No. zaDojo requests the analytics.readonly scope, so the agent can read reports but cannot change settings, events or users.
Which AI clients can use it?
Claude Code, Claude Desktop, Cursor, Codex CLI, Codex in the ChatGPT desktop app, ChatGPT with a custom connection, and other clients that support remote MCP servers.
Does it work with Universal Analytics?
No. It reads GA4 properties only.