By Ira Bodnar, Ryze AI · Updated · Connector tested November 13, 2026
Quick answer
The main way to connect Claude to Google Analytics 4 is the Ryze AI connector. Connect your GA4 property in a Ryze AI workspace with a Google login that has at least the Viewer role, add https://connector.get-ryze.ai/mcp as a custom connector in Claude, click Connect, allow access and start a new chat. Claude then reads GA4 through nine read-only tools, and nothing in the property changes.
- Connect Google Analytics 4 in Ryze AI with a Google login that has Viewer access
- In Claude open Customize, Connectors, Add, Add custom connector
- Paste the URL, click Add, Connect, then Allow connection
- Start a new chat and list your GA4 properties
Claude to Google Analytics 4 at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, added as a custom connector under Customize, Connectors |
| Connector address | https://connector.get-ryze.ai/mcp |
| Sign-ins involved | Two: Google once inside Ryze AI, then Ryze AI from Claude through OAuth with PKCE. No client ID, API key or Google Cloud project |
| GA4 tools | 9, all read: property list, raw, pivot and realtime reports, Admin API reads and 4 AI-referral reports |
| Can Claude change GA4 | No. The Google scope is analytics.readonly and the Admin API tool takes GET requests only |
| GA4 access you need | Viewer role or higher on the property or its account. No Universal Analytics |
| Claude plan | Free, Pro, Max, Ultra, Team or Enterprise. Free allows one custom connector |
| Where it works once added | claude.ai, Claude Desktop, Cowork, the phone apps after your next sign-in there, and Claude Code on the same account |
| Ryze AI price | Paid Ads is $89 per month with a 7-day free trial. Adding the connector is free |
| Google's own option | analytics-mcp, run on your computer. Google names Claude Desktop and Claude Code for it, not claude.ai |
| Last checked | Connector tested November 13, 2026. GA4 calls made November 14, 2026 |
Before you start
- A Claude account. Anthropic lists custom connectors on the Free, Pro, Max, Ultra, Team and Enterprise plans, and Free is limited to one custom connector. On Team an Owner or Primary Owner adds the connector once in Organization settings, Connectors; Enterprise also lets people whose custom role includes Manage access to Libraries do it. Each member then clicks Connect and signs in with their own account. (Anthropic help center)
- A Google login with access to the GA4 property. At least the Viewer role on the property, or on the account above it. Universal Analytics properties are not supported. The access section below shows how to get the role.
- A Ryze AI workspace on a plan or free trial. GA4 is connected here once. Without an active plan, Claude can list your workspaces and connect platforms, but the other tools reply that a subscription is required. Every Ryze AI plan includes the Claude connector; Paid Ads is $89 per month with a 7-day free trial and SEO Starter is $129 per month with a 3-day free trial. See pricing.
How to connect Claude to Google Analytics 4 in claude.ai
Six steps across Ryze AI and Claude. The screenshots show the Claude settings screen and the Ryze AI permission page, which look the same for every platform; the connector URL is the same for every user.
Connect Google Analytics 4 in Ryze AI
Sign up at ryze.ai, open Integrations in the left sidebar and find Google Analytics 4 under Analytics. Click Connect, sign in with the Google login that has access to the property, approve access and keep every requested permission checked. Back in Ryze AI, pick the Property (listed as account, property) and click Save. Until a property is saved the card shows Require setup.
Copy the connector URL
The URL is the same for every user: https://connector.get-ryze.ai/mcp. In Ryze AI it is also on the Connect Claude card on Home and on the Claude MCP card under Integrations, AI.
Open Connectors in Claude
In claude.ai open Customize, then Connectors, or go straight to claude.ai/customize/connectors. In the desktop app Customize sits in the sidebar. If an older guide sends you to Settings, Connectors from your avatar in the bottom-left corner, follow the link there to Customize, Connectors (screenshot below).

Add the custom connector
Click Add, then Add custom connector. Anthropic's pages also print these as + Add, or as Custom, then Web. Name it Ryze AI and paste https://connector.get-ryze.ai/mcp into the MCP server URL field exactly, /mcp included. Some accounts see one screen with extra options under Advanced, others a second step. Keep the options Claude marks Detected and do not pick No sign in, because the Ryze AI server answers only after sign-in. If you set the OAuth client by hand, choose Register automatically: the server supports automatic client registration, not Claude's published identity. Leave Request headers empty if you see them. There is no client ID, client secret or Google Cloud project to enter. Click Add.
Click Connect and allow access
If the new Ryze AI connector shows Connect, click it. On claude.ai the sign-in page opens in the same tab; the desktop app opens it in your browser. On the Ryze AI page Connect your data sources to AI, sign in, keep the workspace that holds your GA4 property ticked (all workspaces are ticked by default, up to 20 per connection) and click Allow connection. When exactly one workspace is ticked, the page also shows Connect your accounts, where you can connect more platforms before you allow access. Claude then lists the connector as Connected.

Start a new chat and list your properties
Chats opened before the connection do not pick it up, so start a new one. Ask: List the Google Analytics accounts and properties I can access, with their property IDs. Claude calls listAccountSummaries and returns each account with its properties.
Connection errors on the Claude side are covered in the Ryze AI Claude connector FAQ, and the steps follow Connect Claude and Connect Google Analytics in the Ryze AI help center.
Sources: Anthropic custom connector docs, Anthropic remote MCP article, Anthropic connectors article, Anthropic getting started page. Checked November 14, 2026.
GA4 role and permission screen
Ryze AI reads the GA4 properties your Google login can already open, so the role is set in Google Analytics, not in Ryze AI. The Ryze AI help center and Google's own MCP setup guide both ask for at least the Viewer role on the property.
| GA4 role or restriction | What Google says it allows | Works with the connector |
|---|---|---|
| Viewer | Sees settings and data and can change which data appears in reports | Yes. This is the minimum. |
| Analyst | Viewer permissions, plus sharing explorations with other users | Yes |
| Marketer | Analyst permissions, plus audiences, events, key events and attribution settings | Yes. The extra rights are not used, because the connector only reads. |
| Editor | Analyst permissions, plus full control of property settings | Yes. The extra rights are not used. |
| Administrator | Editor permissions, plus managing users | Yes. The extra rights are not used. |
| None | No role on that property | No. The property does not appear in the list. |
| No Cost Metrics or No Revenue Metrics restriction | Blocks cost metrics (such as Google Ads cost and ROAS) or revenue metrics | Reads work, but the restricted metrics come back as 0. Google enforces the restriction in the API too. |
If your login has no role yet, a GA4 Administrator adds it: Admin, then under Property select Access Management, click +, choose Add users, enter your Google email, pick the Viewer role and click Add. Only Administrators can add users. Source: Google's access and data-restriction management and add users help pages.
The Google permission screen
When you click Connect on the Google Analytics 4 card in Ryze AI, Google's sign-in and consent screen opens. Ryze AI asks Google for four scopes. The middle column is Google's own wording from its OAuth scope list; the last column says what each scope means for what Claude can see.
| Scope Ryze AI requests | How Google describes it | What it means here |
|---|---|---|
| analytics.readonly | See and download your Google Analytics data | The only Analytics scope requested. Google's runReport method and its account summaries list both accept it, so it covers finding your properties and running reports |
| openid | Associate you with your personal info on Google | Sign-in only, with no Analytics data behind it |
| See your primary Google Account email address | The address of the Google login you used, nothing from GA4 | |
| profile | See your personal info, including any personal info you've made publicly available | Basic profile details for the sign-in; GA4 reports are not part of it |
Ryze AI reaches GA4 through the consent you give on Google's screen, acting as your Google user. It uses no API key and no service account, and you do not create a Google Cloud project or an OAuth client.
Left off the request: analytics.edit, which Google describes as Edit Google Analytics management entities, and analytics.chatbot.read, the scope behind Google's Ask Advisor chat method. A Marketer or Editor role carries rights to create audiences, key events and property settings, and this connection never calls on them. Claude can report on a key event through Ryze AI, but cannot create one.
Pick the login that has the role, keep every requested permission checked, then pick the property in Ryze AI and click Save. If the Google Analytics permission is unticked, Ryze AI cannot read the property. The saved property is only the default: Claude can query any other property on the same Google login by naming it. Sources: Google's OAuth 2.0 scopes for Google APIs, runReport reference and accountSummaries.list reference. Checked November 14, 2026.
The Claude side of the sign-in
The second sign-in, from Claude to Ryze AI, is its own OAuth flow. The connector's sign-in details name two scopes, mcp:read and mcp:write. Anthropic says Claude asks for the scopes in the server's 401 answer, or else those its metadata lists. Which ones Claude requested from Ryze AI was not checked. Source: Anthropic connector authentication. Checked November 14, 2026.
What Claude can read in Google Analytics 4
All nine GA4 tools on the connector read data. runAdminRead accepts GET requests only and rejects create, update and delete paths, so Claude cannot change key events, data streams or property settings through Ryze AI.
| Tool | What it returns |
|---|---|
| listAccountSummaries | Every GA4 account and property the login can reach, with property IDs |
| runRawReport | Any Data API report: dimensions, metrics, named date ranges, filters, ordering |
| runPivotReport | Pivot tables, for example channel by device |
| runRealtimeReport | The last 30 minutes: active users, screen views and events |
| runAdminRead | Admin API reads: key events, custom dimensions, data streams, audiences |
| getAIReferrals | AI referral sources with sessions and conversions |
| getAiLandingPages | Top landing pages that receive AI-referred traffic |
| getAiTrafficByEngine | AI traffic by engine, compared with a prior period |
| getAiTrafficDaily | Daily sessions from AI referrers such as ChatGPT and Perplexity |
Anthropic says the Tool permissions list under Customize, Connectors, Ryze AI shows every tool a server offers, so each of the nine can be set to Always allow, Needs approval or Blocked. Every tool takes the workspace. All except listAccountSummaries and runAdminRead also take a property ID in each call; listAccountSummaries returns the IDs.
Parameters, request examples and API limits for each tool are on the Google Analytics MCP server page.
Limits in numbers
| Limit | Figure |
|---|---|
| Daily report budget | 200,000 core tokens per standard property, 2,000,000 on Analytics 360. Refilled at midnight Pacific time. |
| Hourly report budget | 40,000 tokens per property (400,000 on 360). One Google Cloud project may spend 14,000 of them per property per hour. |
| Reports at the same time | 10 per standard property, 50 on 360. |
| Price of one report | Usually 10 tokens or fewer. More rows, fields, filters, days and detailed dimensions such as pagePath cost more. |
| A budget at 0 | 429 RESOURCE_EXHAUSTED on further requests to that property until it refills. |
| Failed requests | 10,000 per project and property in any 15-minute window, counting every answer other than 200 or 500. |
| Rows | 10,000 by default, 250,000 at most per request, paged with offset. |
| Dimensions, metrics and date ranges per report | 9 dimensions at most, per Google's report guide. In the test on November 14, 2026 the API also refused an 11th metric and a 5th date range. |
| Realtime window | The last 30 minutes, or up to 60 on 360. |
| How fresh the data is | Usually 2 to 6 hours for intraday data and 12 hours for daily data on standard properties. Processing can take 24 to 48 hours. |
| Ryze AI tool inputs | getAiLandingPages returns 200 rows at most. A runAdminRead path is up to 512 characters. |
| Claude's side | About 150,000 characters per tool result and 240 seconds per tool call in claude.ai and Claude Desktop. |
Sources: Data API quotas, Data API changelog, runReport reference, Create a report, Realtime reports, Admin API quotas, GA4 data freshness, Anthropic connector limits. Checked November 14, 2026.
Calls tested through the connector
Claude Code sent these eight calls through the Ryze AI connector on November 14, 2026, over the default read-only connection to a standard GA4 property. Two asked for data and worked; six were wrong on purpose. The property belongs to a real account, so only field names and outcomes are shown.
| Tool and request | Outcome |
|---|---|
| listAccountSummaries, with only the workspace | Worked: accountSummaries, each with propertySummaries (property, displayName, propertyType, parent, canEdit) |
| runRawReport, sessions for the day before the test, returnPropertyQuota on | Worked: one row with metricHeaders, rowCount and metadata (currency code, time zone), plus a propertyQuota block whose totals equal the standard-property limits |
| runRawReport with the made-up dimension trafficSauce | 400 INVALID_ARGUMENT, manualSource suggested |
| runRawReport with the misspelled metric sessionz | 400 INVALID_ARGUMENT, sessions suggested |
| runRawReport on a property ID that does not exist | status not_allowed, as an ordinary tool result |
| runRawReport with 10 dimensions | 400 INVALID_ARGUMENT |
| runRawReport with 11 metrics | 400 INVALID_ARGUMENT |
| runRawReport with 5 date ranges | 400 INVALID_ARGUMENT |
Claude Desktop
Remote connectors belong to your Claude account. Anthropic lists custom connectors for claude.ai, Cowork and Claude Desktop, so a connector added on claude.ai is already in the desktop app, and the phone apps pick it up after your next sign-in there. To add it from the app instead, open Customize in the sidebar, then Connectors, click Add, Add custom connector, paste the URL and click Connect. The app sends the Ryze AI sign-in to your browser.
You do not need claude_desktop_config.json. Anthropic calls servers listed in that file a separate mechanism: they run on your computer, use your local network and are not available in claude.ai or in Cowork sessions that run in the cloud. Google's own Google Analytics MCP server is that kind of server, so in Claude Desktop it goes in that file, as the ways table shows.
Claude and MCP: the facts in one table
| Topic | What Anthropic's pages say |
|---|---|
| Where you add a connector | Customize > Connectors, Add, Add custom connector on Free, Pro, Max and Ultra. On Team and Enterprise an Owner starts in Organization settings > Connectors |
| What the add dialog asks | Name, MCP server URL, Authentication, OAuth client, Request headers (a beta for some organizations) and, under Advanced, Transport |
| Transports | Streamable HTTP for remote servers; the older HTTP+SSE still works while it is phased out. Desktop extensions use stdio |
| Sign-in | OAuth 2.0 with PKCE S256 on every authorization request. Claude never sees the password and returns to https://claude.ai/api/mcp/auth_callback |
| Where the calls come from | Anthropic's cloud, even when you chat in Claude Desktop or on a phone, so the server must answer on public HTTPS port 443 |
| Tool approval | Allow once or Always allow when asked. Standing rules per tool or group: Always allow, Needs approval or Blocked |
| Inside one chat | The + button or /, then Connectors, turns a connector on or off for that conversation |
| Local servers | Claude Desktop only, as a desktop extension (.mcpb) or a command in claude_desktop_config.json. Not in claude.ai |
| Where it is managed | Customize > Connectors, then the connector: Tool permissions, Disconnect, or Remove. Status reads Connected, Connect or Reconnect |
Sources: Anthropic's custom connector docs, remote MCP article, building, authentication, getting started and desktop and web connectors pages. Checked November 14, 2026.
Claude Code
One command registers the connector for every project on your machine:
claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp --scope userThen open Claude Code, type /mcp, pick the Ryze AI server (ryze) and finish the sign-in in the browser tab that opens. If you sign in to Claude Code with the same claude.ai account, the connector you added on claude.ai is already available there and this step is optional. claude mcp list confirms the server is connected.
For scripts and headless runs, create a key in Ryze AI under Workspace Settings, Profile, API keys, and send it as a header instead of signing in in the browser:
claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp --scope user \
--header "Authorization: Bearer YOUR_RYZE_AI_KEY"Sources: the Claude Code MCP docs and the Ryze AI API for agents.
ChatGPT, Cursor and Windsurf
The same URL works outside Claude. The GA4 connection in Ryze AI stays the same; only the client side changes.
ChatGPT
OpenAI's help center offers full custom MCP servers on ChatGPT web for Business and Enterprise/Edu, and read and fetch only on Pro; it does not mention Plus. In Plugins, add a custom MCP server with the connector URL and OAuth, sign in to Ryze AI, then pick Ryze AI with @ in a new conversation. If GA4 is connected in Ryze AI after that, OpenAI's docs say to open the server under Plugins, select Refresh and start a new conversation. The ChatGPT guide for Google Analytics has every step.
Cursor and Windsurf
Cursor reads a url entry in ~/.cursor/mcp.json for every project or .cursor/mcp.json for one, runs the sign-in with PKCE and registers itself; approve it on the Ryze AI page. The Windsurf docs address now leads to the Devin Desktop docs, which take the same url entry under mcpServers in ~/.config/devin/mcp_config.json.
{
"mcpServers": {
"ryze": { "url": "https://connector.get-ryze.ai/mcp" }
}
}7 ways to connect Claude to Google Analytics 4
Claude reaches a hosted server from Anthropic's cloud. Only Claude Desktop, and Claude Code, can also start a server on your computer. So hosted options work in claude.ai, and local ones do not. Seven ways fit. This guide treats the Ryze AI connector as the main way: one Google approval in Ryze AI, one pasted address in Claude, no Python and no Google Cloud project. The other six were read on their own pages on November 14, 2026.
| Way | Runs where | Setup in Claude | What it reaches in GA4 | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted. One address for every user, shared with Google Ads, Meta Ads and Search Console | Add custom connector with https://connector.get-ryze.ai/mcp, or add it from its Connectors Directory listing (Community label). Works in claude.ai, Desktop, Cowork and the phone apps | 9 read tools, 4 of them for AI-referred visits | $89 a month on Paid Ads, with a 7-day free trial; adding the connector costs nothing |
| Google's analytics-mcp 1.1.0 (November 6, 2026), open source | Your computer | Not in claude.ai. Claude Desktop: a pipx run analytics-mcp entry in claude_desktop_config.json with GOOGLE_APPLICATION_CREDENTIALS and GOOGLE_CLOUD_PROJECT; Claude Code: claude mcp add. Needs Python 3.10+, a Google Cloud project with both Analytics APIs on and Application Default Credentials | Read by default: 9 tools on Google's page, 13 in the README, 3 of which write with --allow-write and analytics.edit | No price stated. Apache-2.0 license |
| Composio | Hosted | Composio names Claude on its Google Analytics page and gives the address https://connect.composio.dev/mcp, which Claude takes as a custom connector. You then approve GA4 through Composio's Google app. Its step-by-step pages cover Claude Code and Cowork, not claude.ai | 82 tools that read and write, such as Create Audience | Free up to 10,000 tool calls a month. Standard is $18 per seat per month |
| Zapier MCP | Hosted | Generate a Zapier MCP address, pick the GA4 actions, add it to Claude and sign in. Zapier lists Claude as a popular client | 6 actions, among them Run Report and Create Conversion Event | 2 tasks per successful tool call; Free has 100 tasks a month |
| Windsor.ai | Hosted | Add GA4 as a source in Windsor.ai, then search for Windsor under Customize, Connectors and sign in. In the directory since January 2026 | GA4 read only; 19 tools across all Windsor sources | Free tier after a 30-day trial: 1 source, last 30 days. Basic $23 per month |
| Coupler.io | Hosted, on a synced copy of GA4 | Build a GA4 data flow, then pick its Claude integration. Its Custom MCP route needs a Bearer header, which in Claude depends on the Request headers beta | Read only. 10 metrics and 9 dimensions per data flow, queried as SQL | Free with manual refresh. Starter $32 per month |
| surendranb/google-analytics-mcp, open source (244 GitHub stars) | Your computer. Sends anonymous telemetry unless DO_NOT_TRACK=1 is set | Not in claude.ai. Claude Desktop through claude_desktop_config.json, with GA4_PROPERTY_ID and a service account key; Claude Code through claude mcp add | 8 read tools, such as get_ga4_data | Free, MIT license |
Three more Google options, and why they do not fit
- analytics-mcp in HTTP mode. Since 1.0.0 Google's server can run as a hosted multi-user service with OAuth 2.1, on Docker or Cloud Run. The README names only Google ADK, an agent framework, for it and no chat assistant, so Google does not say Claude works with it. Its built-in sign-in keeps tokens in memory, so a restart signs everyone out.
- Google Analytics agent skills. Instruction packs for coding agents that write Data API code. Google names Antigravity, Claude Code, Codex and Cursor, not claude.ai, and they carry no data connection.
- The Ask Advisor chat method. properties.chat, a v1alpha Data API call with the analytics.chatbot.read scope, is for code. Google names no assistant for it.
Which one to pick
Ryze AI is the best way to connect Claude to Google Analytics 4 when you want answers in claude.ai or the desktop app without running anything yourself, with one caveat: it only reads, so creating an audience, a key event or a custom dimension needs another route. Composio and Zapier write to GA4 and fit teams that already use them. Windsor.ai and Coupler.io fit teams that already route marketing data through them. Choose Google's analytics-mcp if you work in Claude Desktop or Claude Code with a Google Cloud project and want Google's own code. For one question with nothing connected, the CSV route below works everywhere.
Google's docs page, updated November 10, 2026, still calls its server read-only, while the 1.1.0 README adds three write tools behind a flag. For a wider comparison, see the best MCP servers for Google Analytics.
Sources: Google MCP docs, analytics-mcp, agent skills, Ask Advisor, Composio, Composio pricing, Zapier, Zapier pricing, Windsor.ai for Claude, Windsor.ai GA4, Windsor.ai pricing, Windsor.ai listing, Coupler.io, Coupler.io pricing, surendranb repository. Checked November 14, 2026.
Download a GA4 report as CSV instead
- In Google Analytics select Reports in the left menu and open the report you need, for example Traffic acquisition, with your date range set.
- Click the Share this report icon at the top right, choose Download File, then Download CSV. The file holds up to 100,000 rows, and you need the Viewer role on the property.
- In Claude click the + button in the message box, attach the file and ask, for example: Which five landing pages have the most sessions but the lowest key event rate?
The file is a snapshot of one report, frozen at download time, and any Claude surface can take it. Claude cannot pull other dimensions or dates from it, so a new question often means a new download. Source: Google's share and export reports help page.
First 3 prompts to run
Run these three in order in a new chat. Each one lists what comes back. This page shows no figures from any GA4 property.
Prompt 1 · tool:
listAccountSummariesList the Google Analytics accounts and properties I can access, with their property IDs.
What comes back: Each GA4 account with its properties, the property ID and whether your login can edit it. Claude uses the ID in every report after this one.
Prompt 2 · tool:
runRawReportFor the <property name> property, show sessions, engaged sessions and key events by default channel group for the last 28 days against the 28 days before.
What comes back: One row per channel and per date range, labeled with the range names Claude sets, plus the currency and time zone of the property. Claude then writes the comparison as a table.
Prompt 3 · tool:
getAiTrafficByEngineHow many sessions came from AI assistants in the last 28 days compared with the 28 days before, split by engine?
What comes back: Sessions, users, revenue and purchases for the period, sessions and revenue for the prior period, the change in sessions as a percentage and a breakdown by engine (ChatGPT, Gemini, Claude, Perplexity and others, by referrer).
Next prompts
- List the key events on this property and how each one is counted. (
runAdminRead) - Who is on the site right now, by country and device? (
runRealtimeReport) - Which landing pages received the most visits from AI assistants this month? (
getAiLandingPages)
For reusable versions of these prompts, see Claude skills for Google Analytics. For Google Ads, see how to connect Claude to Google Ads.
10 jobs to hand to Claude
Ten requests to give Claude, each with the tool that answers it. listAccountSummaries and runRawReport were called in the test; the other tools were loaded and not called, since they return real business data. The last row is a job this connection cannot do.
| Job | What to type in Claude | Tool | Works on the default connection |
|---|---|---|---|
| Find property IDs | Which GA4 accounts and properties can this Google login open? Give me each property ID. | listAccountSummaries | Yes |
| Month over month by channel | Compare sessions, key events and revenue by default channel group for last month and the month before, with each range named. | runRawReport | Yes. One report takes up to 4 date ranges |
| Landing page health | For the last 28 days, rank landing pages by sessions and show engagement rate and key event rate next to each. | runRawReport | Yes |
| Revenue by source | Show purchase revenue and purchases by session source and medium for this quarter. | runRawReport | Yes, once ecommerce tracking sends purchase events. A No Revenue Metrics restriction hides it |
| Channel by device | Build a pivot of sessions with channels as rows and device categories as columns. | runPivotReport | Yes |
| Live check | Which countries and devices are active on the site right now? | runRealtimeReport | Yes, for the last 30 minutes only |
| Configuration audit | List the key events, custom dimensions and audiences set up in this property. | runAdminRead | Yes. Audiences are read with version v1alpha |
| AI engines against the last period | Which AI assistants sent visits in the last 30 days, and how does each compare with the 30 days before? | getAiTrafficByEngine | Yes |
| AI visits by day and page | List daily sessions from AI assistants this month, then the landing pages and referral sources behind them. | getAiTrafficDaily, getAiLandingPages, getAIReferrals | Yes. Landing pages come back as 200 rows at most |
| Create a key event | Mark the form_submit event as a key event. | None | No. The connection only reads, so make the change in GA4 Admin |
Claude, GA4 and MCP: dates that matter
| Date | What happened |
|---|---|
| May 6, 2024 | The GA4 Data API made conversions a deprecated metric name in favor of keyEvents. |
| November 25, 2024 | Anthropic open-sourced MCP, and Claude Desktop began running local servers on every plan. |
| May 1, 2025 | Claude gained remote MCP servers on web and desktop, in beta on Max, Team and Enterprise. Pro followed on June 3, 2025. |
| July 14, 2025 | Claude's connectors directory opened; remote connectors were then for paid plans only. |
| July 30, 2025 | Google announced its Analytics MCP server in the Google Analytics API Notify group. |
| February 25, 2026 | Claude Desktop gained Customize, which groups skills, plugins and connectors. |
| October 22, 2026 | analytics-mcp 0.8.0 added its first write tool and the --allow-write flag. |
| November 3, 2026 | analytics-mcp 1.0.0 added the multi-user HTTP mode with OAuth 2.1 and left experimental status. |
| November 6, 2026 | analytics-mcp 1.1.0 added opt-in writes for custom dimensions and key events. Still the newest on November 14, 2026. |
Sources: Data API changelog, Anthropic MCP announcement, Integrations post, connectors directory post, Claude release notes, Google Analytics API Notify post, analytics-mcp releases. Checked November 14, 2026.
How this guide was tested
Two checks stand behind this guide: the connector address on November 13, 2026, and GA4 calls through the connector on November 14, 2026.
| What was run | What came back |
|---|---|
| The connector address without signing in (November 13) | HTTP 401 with a WWW-Authenticate header pointing to the sign-in details. Anthropic says a 401 is what starts sign-in in Claude. |
| The connector's two discovery files (November 13) | Both loaded: authorize, token and register endpoints, authorization code and refresh token grants, PKCE with S256, scopes mcp:read and mcp:write. |
| GA4 tool list through the connector, from Claude Code (November 14) | All 9 definitions loaded by exact name. No name contains a write verb. |
| Two GA4 reads (November 14) | listAccountSummaries and a one-day runRawReport worked. The report's quota block totals equal the standard-property limits. |
| Six calls built to fail (November 14) | Five 400 INVALID_ARGUMENT answers and one not_allowed, listed in the errors table. |
Not run: any step inside Claude. No connector was added in claude.ai or Claude Desktop and no tool was called from either, so the setup steps follow Anthropic's pages as read on November 14, 2026. The OAuth option Claude marks Detected and the scopes it asks for were not checked. The GA4 calls came from Claude Code, which reaches the same server and the same 9 tools. runPivotReport, runRealtimeReport, runAdminRead and the four AI-traffic tools were not called, because they return business data from a real account. No call went to Google's analytics-mcp, and nothing was written.
GA4 errors and fixes
Exact error messages from the test
Google sent these six messages back in the test on November 14, 2026, copied from the responses. Five reached the assistant as Error 400 with Google's JSON error inside. The permission message came back as an ordinary tool result with the status not_allowed.
| Message | What it means | What to do in Claude |
|---|---|---|
| Did you mean manualSource? Field trafficSauce is not a valid dimension. For a list of valid dimensions and metrics, see https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema | A dimension name the Data API does not have, sent on purpose. | Ask again with a real one such as sessionSource, or the one Google suggests. |
| Did you mean sessions? Field sessionz is not a valid metric. For a list of valid dimensions and metrics, see https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema | A misspelled metric, also on purpose. | Use the suggested name. For conversions, ask for keyEvents. |
| User does not have sufficient permissions for this property. To learn more about Property ID, see https://developers.google.com/analytics/devguides/reporting/data/v1/property-id. | The ID does not exist, or the connected Google login has no role on it. Google answers both the same way. | Have Claude run listAccountSummaries and use an ID from it, or ask a property admin for the Viewer role. |
| Requests are limited to 9 dimensions within a nested request. This request is for 10 dimensions. | 9 dimensions per report at most. | Drop a breakdown or ask for two reports. |
| Requests are limited to 10 metrics within a nested request. This request is for 11 metrics. | 10 metrics per report at most. | Split the metrics across two reports. |
| Requests are limited to 4 dateRanges. This request contains 5 dateRanges. | 4 periods per report at most. | Compare 4 periods at once, or use a date dimension over one range. |
Not triggered in the test, but on Google's errors page: 429 RESOURCE_EXHAUSTED for an empty quota and 401 UNAUTHENTICATED for bad credentials. Claude's own connection messages, documented by Anthropic and not seen with Ryze AI here, are Couldn't reach the MCP server, Authorization with the MCP server failed, and Unexpected error while invoking tool. Sources: Data API errors, Anthropic connector troubleshooting. Checked November 14, 2026.
Other problems
- No properties to pick in Ryze AI
- The Google login you connected has no role on any GA4 property. Ask a GA4 Administrator to add it with at least the Viewer role, then reconnect Google Analytics 4 in Ryze AI with that login.
- The Google Analytics 4 card shows Require setup
- The login is connected but no property is saved. Click View on the card, pick the Property and click Save. The saved property is only the default; Claude can still query other properties on that login by name.
- Claude does not show any GA4 tools
- This happens when GA4 was connected in Ryze AI after the connector was added to Claude. Per the Ryze AI help center, Claude holds on to the tool list it saw at that moment, and a GA4 reconnect does not update it. Delete the connector under Customize, Connectors, add the same address again and open a fresh chat. Anthropic's own pages do not say when Claude reads a tool list again.
- Revenue or cost comes back as 0
- Either ecommerce tracking is not set up in GA4 and purchase events are not firing, or your GA4 user has the No Revenue Metrics or No Cost Metrics restriction. Google applies restrictions in the API as well, so ask an Administrator to check your access.
- Quota errors (HTTP 429, RESOURCE_EXHAUSTED)
- The Data API gives a standard property 200,000 core tokens per day, 40,000 per hour and 10 concurrent requests, and one app's Cloud project can use at most 14,000 tokens per hour on a property. When a bucket runs out, requests return 429. Ask for fewer rows or a shorter date range, or wait for the hourly quota to refill.
- Numbers differ from the GA4 interface
- Check that the date range and time zone match; reports come back in the property's time zone. GA4 also applies data thresholds to reports and API calls that include demographic data or low counts in a narrow date range, so some rows can be withheld.
- Claude asks for conversions and the column is empty or rejected
- GA4 renamed conversions to key events. Ask for keyEvents and sessionKeyEventRate instead of conversions and sessionConversionRate.
- The card shows Reconnect needed
- Click Reconnect on the Google Analytics 4 card in Ryze AI and sign in to Google again, then start a new chat in Claude. If the Ryze AI connector itself shows Reconnect under Customize, Connectors, click it and sign in to Ryze AI again: Anthropic says Claude shows that status when access is lost.
Sources: Ryze AI GA4 integration help, Data API quotas and GA4 data thresholds.
Terms on this page
- MCP
- The Model Context Protocol, which Anthropic open-sourced in November 2024. Claude uses it to call tools on servers such as the Ryze AI connector.
- Custom connector
- A remote MCP server you add to Claude by its address. Anthropic does not review it, and Claude never suggests it in a chat.
- Property ID
- The number of the GA4 property a report is built for, shown under Admin, Property Settings. Every Data API request names it.
- Key event
- An event that marks an action that matters to the business, formerly called a conversion. The API metric is keyEvents.
- Dimension and metric
- A metric counts activity, such as active users. A dimension splits it, for example by country.
- Token
- Google's unit for what a report request costs against the property's daily and hourly budget.
Sources: Anthropic MCP announcement, Anthropic directory and custom connectors, Google property ID page, Google key events help, runReport reference, Data API quotas. Checked November 14, 2026.
GA4 next to your ad accounts
The same connector URL carries Google Ads, Meta Ads, Search Console, Shopify, TikTok Ads and the other platforms you connect in the workspace, so Claude can read GA4 next to ad spend in one chat.
- Google Analytics MCP server: full tool reference
- Best MCP servers for Google Analytics
- Claude skills for Google Analytics
- How to connect Claude to Google Search Console
- How to connect Claude to Google Ads
- How to connect Claude to Meta Ads
- Connect multiple Google Ads accounts to Claude
- How to measure AI referral traffic in GA4
- Ryze AI MCP for developers
- All Claude integrations
Frequently asked questions
How do I connect Google Analytics to Claude?
Connect your GA4 property in a Ryze AI workspace with a Google login that has at least the Viewer role. Then in claude.ai open Customize, Connectors, click Add, Add custom connector, paste https://connector.get-ryze.ai/mcp, click Connect and Allow connection, and start a new chat. No Google Cloud project, API key or code is needed.
Is there a Google Analytics MCP server for Claude?
Yes, two kinds. The hosted Ryze AI connector at https://connector.get-ryze.ai/mcp works in claude.ai, Claude Desktop and the phone apps. Google's open-source analytics-mcp runs on your computer, so it works in Claude Desktop and Claude Code but not in claude.ai.
Does Google Analytics have an official MCP server?
Yes. Google publishes analytics-mcp on GitHub and PyPI under Apache-2.0; version 1.1.0 came out on November 6, 2026. It reads by default, and its three write tools need --allow-write and the analytics.edit scope.
What is the Google Analytics MCP URL for Claude?
With Ryze AI it is https://connector.get-ryze.ai/mcp, the same for every user. Google's analytics-mcp has no public address by default: Claude Desktop starts it from claude_desktop_config.json with pipx run analytics-mcp, and Claude Code registers the same command with claude mcp add.
Can one MCP server give Claude Google Analytics, Google Ads and Search Console data?
Yes. The Ryze AI connector serves GA4, Google Ads and Search Console tools from one address when all three are connected in the same Ryze AI workspace.
Does Claude need a connector to read GA4 data?
For live data, yes. Claude reads GA4 through an MCP server that calls the Google Analytics Data and Admin APIs. You can use a hosted connector such as Ryze AI, or run Google's open-source analytics-mcp server yourself. Downloading a report as CSV and attaching it to a chat also works, but only for that one snapshot.
Which Google Analytics role do I need?
At least Viewer on the GA4 property or on the account above it. Analyst, Marketer, Editor and Administrator all include Viewer permissions, so they work too. If your user has the No Revenue Metrics or No Cost Metrics restriction, those metrics come back as 0 through the API as well.
Which Claude plan do I need?
Anthropic lists custom connectors on the Free, Pro, Max, Ultra, Team and Enterprise plans, with Free limited to one custom connector. On Team and Enterprise an Owner adds the connector in Organization settings first, then each member clicks Connect. Checked November 14, 2026.
Does it work in Claude Desktop and Claude Code?
Yes. Remote connectors are tied to your Claude account, so a connector added on claude.ai is also in Claude Desktop, and in Claude Code when you sign in with the same claude.ai account. You can also register it in Claude Code with claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp --scope user and finish the sign-in with /mcp.
Can Claude change my GA4 settings?
Not through Ryze AI. All nine GA4 tools on the connector read data, and the Admin API tool accepts GET requests only. Key events, custom dimensions, data streams and property settings stay as they are.
How is Ryze AI different from Google's official Google Analytics MCP server?
Google's analytics-mcp is open source and runs from Python with pipx or uv. It needs a Google Cloud project with the Analytics Admin and Data APIs enabled and Application Default Credentials with the analytics.readonly scope, and it runs in Claude Desktop and Claude Code, not in claude.ai. Its GitHub README lists 13 tools, three of which write only when you pass --allow-write. Ryze AI is hosted: you sign in with Google in Ryze AI, paste one URL into Claude and get nine read tools, four of them for AI-assistant traffic.
Which GA4 connector should I use with Claude?
Ryze AI is the best GA4 connector for marketers who want Claude to report AI-assistant traffic and ad performance in the same chat, because it adds four AI-referral tools and the same URL also covers Google Ads, Meta Ads and Search Console. The caveat is that it only reads, so changes to GA4 settings still happen in GA4 or through a tool that writes. Google's own server suits developers who already run a Google Cloud project and want to host the code themselves.
Can I connect several GA4 properties or clients?
Yes. One Google login reaches every property it has access to, and you can add more Google logins to the same workspace with Add one more account. For separate clients, use one Ryze AI workspace per client; one Claude connection can cover up to 20 workspaces, and you name the client in chat.
Why do the GA4 tools not show up in Claude?
The Ryze AI help center says Claude keeps the connector's tool list from when you added it, so GA4 connected afterwards does not appear. Remove the Ryze AI connector in Customize, Connectors, add it again and start a new chat. Reconnecting GA4 in Ryze AI does not refresh Claude's list.
How much does it cost to connect Claude to GA4?
The connector is included in every Ryze AI plan. Paid Ads is $89 per month with a 7-day free trial, SEO Starter is $129 per month with a 3-day free trial, and annual billing takes 30% off the first year. A paid Claude plan, if you use one, is billed by Anthropic separately.
Can Claude see traffic from ChatGPT and other AI assistants in GA4?
Yes. Four tools report AI-referral traffic: sources with sessions and conversions, top landing pages, traffic by engine against a prior period, and daily sessions. Ask, for example: Which pages did ChatGPT and Perplexity send visitors to this month?