By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Antigravity to Google Analytics is the Ryze AI connector. Connect your GA4 property in Ryze AI with a Google sign-in, then add https://connector.get-ryze.ai/mcp to Antigravity as a serverUrl entry named ryze in mcp_config.json and finish the sign-in. All 9 Google Analytics tools are read tools, so nothing in GA4 can be changed.
- In Ryze AI open Integrations, find Google Analytics 4 and click Connect
- Sign in to Google, keep every permission checked, then pick a Property and click Save
- Add the ryze entry with serverUrl to mcp_config.json in the Antigravity IDE, App or CLI
- Finish the sign-in, start a new session and ask which properties you can see
Antigravity to Google Analytics at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector: one hosted MCP address, added to Antigravity as a serverUrl entry in mcp_config.json |
| Server address | https://connector.get-ryze.ai/mcp |
| Sign-in | OAuth 2.0 with PKCE in the browser. Antigravity registers itself through dynamic client registration, so there is no client ID or secret to paste. The Google sign-in for GA4 happens once, inside Ryze AI |
| Google Analytics tools | 9, all read tools |
| Can it change GA4 | No. There are no write tools and the Google scope is analytics.readonly |
| Other data in the same chat | Other platforms connected in the same Ryze AI workspace are served from the same address |
| Antigravity plan needed | Google's MCP page names none |
| Ryze AI price | Paid Ads is $89 per month with a 7-day free trial. The GA4 tools also work on SEO Starter and Agency. Adding the connector is free |
| Google's own option for Antigravity | analytics-mcp, an open-source server that runs on your computer. It needs Python, a Google Cloud project with two APIs enabled and your own credentials. Google's docs page names Antigravity CLI and IDE |
| GA4 access of the connection | The read-only scope analytics.readonly plus openid, email and profile. The Google login needs at least the Viewer role on the property |
| Last tested | Connector calls on November 14, 2026. Antigravity's documentation read on November 15, 2026 |
Before you start
- An Antigravity install. Google's MCP page names no plan, and Google's plans page gives every plan all product features. Antigravity has three surfaces with MCP: the IDE, the App and the CLI (agy). On enterprise accounts the standalone IDE is not supported, and an admin may need to allow MCP servers in Gemini Enterprise first.
- A Google login with at least the Viewer role on a GA4 property. Universal Analytics properties are not supported. A role carrying the No Revenue Metrics or No Cost Metrics restriction will not get those metrics through any connector.
- A Ryze AI workspace on a plan or free trial. 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 Agency is $279 per month. Adding the connector is free, but the GA4 tools need an active plan or trial.
How to connect Antigravity to Google Analytics
Two steps happen in Ryze AI and Google, two in Antigravity, and the last is your first question. The connector URL is the same for every user.
Connect Google Analytics 4 in Ryze AI
Create a Ryze AI account or sign in, open Integrations in the left sidebar and find Google Analytics 4 under Analytics. Click Connect, sign in to Google and approve access, keeping every requested permission checked.
Pick the Property and save
Back in Ryze AI, pick the Property for this workspace (listed as account and property) and click Save. Until a Property is saved the card shows Require setup.
Add the ryze server to mcp_config.json
Open mcp_config.json for your Antigravity surface (IDE: ... in the agent side panel, MCP Servers, Manage MCP Servers, View raw config; App: Customizations, Installed, Copy Config File Path; CLI: edit the file directly). Add the entry shown below under mcpServers. Use ~/.gemini/config/mcp_config.json for every project or .agents/mcp_config.json inside one workspace.
{ "mcpServers": { "ryze": { "serverUrl": "https://connector.get-ryze.ai/mcp" } } }Sign in to the Ryze AI server
In the App click Authenticate next to ryze under Customizations, Installed, MCP Servers, finish the Ryze AI sign-in in the browser, copy the authorization code, paste it into Enter authorization code and click Submit. In the IDE and CLI, Antigravity handles the OAuth sign-in itself and Google's MCP page gives no click-by-click steps. On the Ryze AI page choose the workspace and click Allow connection.
Ask your first question
Start a new session, approve the tool call when Antigravity asks, and try: List every GA4 property my Google login can read, with the property IDs.
The Ryze AI help center page for Google Analytics 4 covers the Google side of the connection. Ryze AI has no help center page for Antigravity; the Ryze AI developers page covers MCP setup in general.
Sources: Antigravity MCP documentation, Ryze AI Google Analytics guide. Checked November 15, 2026.
IDE, App and CLI
The same mcp_config.json format is used by the IDE, the App, the CLI and plugins. Remote servers must use the Streamable HTTP transport. The legacy HTTP+SSE transport and the httpUrl field are not supported, and url works in place of serverUrl.
{
"mcpServers": {
"ryze": {
"serverUrl": "https://connector.get-ryze.ai/mcp"
}
}
}Antigravity IDE
- Click ... at the top of the editor's agent side panel and select MCP Servers.
- Click Manage MCP Servers, then View raw config.
- Add the ryze entry under mcpServers and save the file.
- Antigravity runs the OAuth sign-in on its own for servers that support dynamic client registration. Google's MCP page does not say how the IDE opens it. Complete the Ryze AI sign-in and click Allow connection.
Antigravity App
- Click Customizations in the sidebar, then Installed, and scroll to MCP Servers. The Add MCP Server (+) button opens a catalog list; a custom address goes in mcp_config.json.
- Click Copy Config File Path in the section header and add the ryze entry to that file.
- Click Authenticate next to ryze, finish the sign-in in the browser, copy the authorization code, paste it into Enter authorization code and click Submit.
- If the MCP Servers section is missing, you are in the Knowledge Work layout, where Installed lists plugins only. Switch to Software Engineering under Settings, General, Interface Layout.
Antigravity CLI
- Add the ryze entry to ~/.gemini/config/mcp_config.json or to <workspace>/.agents/mcp_config.json.
- Type /mcp in the prompt panel to open the MCP Manager, check the server status and reload the configuration.
- Google's MCP page does not document how the CLI starts an OAuth sign-in, so this guide gives no CLI sign-in steps.
Antigravity and MCP: the facts in one table
| Topic | What Google's documentation says |
|---|---|
| Config files | ~/.gemini/config/mcp_config.json for every project, <workspace>/.agents/mcp_config.json for one workspace. Plugins can add servers from their own mcp_config.json |
| Transports | stdio for local servers. Streamable HTTP only for remote servers |
| Sign-in | OAuth 2.0 with PKCE. Client order: a manual oauth.clientId, then a Client ID Metadata Document, then dynamic client registration. The redirect URI is https://antigravity.google/oauth-callback |
| Token storage | ~/.gemini/antigravity/mcp_oauth_tokens.json, refreshed automatically. The App changelog (v2.2.1) adds the OS keyring |
| Tool approval | Unconfigured MCP tools run in Ask mode, so each call needs approval until a policy allows it: mcp(server/tool), mcp(server/*) or mcp(*). Deny beats Ask beats Allow |
| Tool loading | Lazy by default: schemas are cached on disk and the agent reads them when needed. A tool with eager set to true is registered up front |
| Tool filtering | enabledTools and disabledTools per server, and disabled to pause a server without removing it |
| Timeouts | Up to 5 minutes for a server to connect and list tools, 3 minutes per tool call. timeoutSeconds replaces both |
| Where servers are managed | IDE: ... in the agent side panel, MCP Servers. App: Customizations, Installed, MCP Servers. CLI: /mcp |
| Admin controls | In Google Cloud, Gemini Enterprise, Settings, AI developer tools has an MCP servers setting (default status Disabled) and an allowed server configuration list. App v2.5.0 added admin MCP allowlists |
| Plan | The MCP page names none; the plans page says every plan gets all product features |
Sources: Antigravity MCP, settings, permissions, changelog, Gemini Enterprise AI developer tools settings. Checked November 15, 2026.
Claude, ChatGPT and Cursor
The same URL works in other MCP clients. GA4 is connected once in Ryze AI, so nothing changes on the Google side.
Claude
Add https://connector.get-ryze.ai/mcp as a custom connector under Customize > Connectors, choose the workspaces and start a new chat. Anthropic lists custom connectors on Free (one connector), Pro, Max, Ultra, Team and Enterprise plans. The Claude guide for Google Analytics is linked below.
ChatGPT
OpenAI's help article lists custom MCP servers on ChatGPT Business and Enterprise/Edu, with read and fetch permissions only on Pro. Add the same URL from Plugins and choose OAuth. If the connector was added before GA4 was connected in Ryze AI, remove and re-add it so the tool list refreshes, then start a new chat.
Cursor
Cursor takes the same address as a url entry in mcp.json or through the Add to Cursor link on the Ryze AI developers page, and signs in with OAuth.
Google access and scopes
Two sign-ins are involved: Google for GA4 and Ryze AI for the connector. Three things decide what Antigravity can reach.
- Which property
- The Property you saved for the workspace. No property is selected inside the tools: the agent passes a property ID, which it can find with the account listing tool. You can connect several Google logins to one workspace with Add one more account; the tools accept an optional connection_id.
- Which Google role
- The Google login needs at least the Viewer role on the property, the same minimum Google's own server asks for. Viewer can see settings and data. A Google response of insufficient permissions means the property does not exist or the login has no role on it.
- What Antigravity asks first
- Antigravity runs unconfigured MCP tools in Ask mode, so each Google Analytics call needs your approval until a policy rule allows it. Allow single tools by name rather than mcp(ryze/*), because the same server carries the tools of every other platform connected in your workspace.
The 4 Google permissions of the connection
The Ryze AI connection asks Google for four permissions. This is the full list, with what Google says each one covers.
| Scope | What Google says it covers | With Ryze AI |
|---|---|---|
| analytics.readonly | See and download your Google Analytics data | Requested. Covers the Data API reports and the Admin API reads |
| openid | Associate you with your personal info on Google | Requested, basic sign-in |
| See your primary Google Account email address | Requested, basic sign-in | |
| profile | See your personal info, including any personal info you've made publicly available | Requested, basic sign-in |
Not requested: analytics.edit (edit Google Analytics management entities) and analytics.chatbot.read, the scope of the Ask Advisor chat method. Nothing can therefore be created or changed in GA4, and the Marketer and Editor roles are not needed. If your role carries No Cost Metrics or No Revenue Metrics, Google enforces that in API calls too.
Sources: Google OAuth scopes, Google Analytics roles and restrictions. Checked November 14, 2026.
Removing access
To remove access, disconnect Google Analytics 4 in Ryze AI. In Antigravity, use More actions on the ryze server (Restart, Disable or Delete) in the App, set disabled to true in mcp_config.json, or delete the entry.
What Antigravity can do in Google Analytics 4
The Ryze AI connector exposes 9 Google Analytics 4 tools, all of them read tools. Every tool takes a workspace and an optional connection_id.
| Tool | Type | What it does |
|---|---|---|
| google_analytics__listAccountSummaries | Read | Lists the GA4 accounts and properties the connected Google login can access, so the agent can find property IDs. |
| google_analytics__runRawReport | Read | Runs a GA4 Data API runReport with chosen dimensions, metrics, named date ranges, filters and ordering, and pages through the results. |
| google_analytics__runPivotReport | Read | Runs a GA4 Data API pivot-table report. |
| google_analytics__runRealtimeReport | Read | Runs a realtime report covering the last 30 minutes. |
| google_analytics__runAdminRead | Read | Reads a GA4 Admin API resource such as key events, custom dimensions or audiences. It is GET only and cannot write. |
| google_analytics__getAiTrafficByEngine | Read | Returns traffic from AI referrers grouped by source engine and compared with a prior period, for one property. |
| google_analytics__getAiTrafficDaily | Read | Returns daily traffic from AI referrers such as ChatGPT and Perplexity. |
| google_analytics__getAiLandingPages | Read | Lists the top landing pages that receive AI-referred traffic, up to 200 rows. |
| google_analytics__getAIReferrals | Read | Lists AI referral sources with their sessions and conversions. |
Some limits apply to every client, Antigravity included. Universal Analytics is not supported. Revenue shows as zero unless ecommerce tracking and purchase events are set up in GA4. GA4 and Shopify numbers will not match exactly because they attribute sessions differently. Without an active Ryze AI plan or trial, the connector can only list workspaces and connect platforms.
Because all 9 tools are read tools, the connector changes nothing in GA4. Antigravity still asks before each MCP call until you allow it. To keep a review step for other platforms in the same workspace, allow the Google Analytics tools one by one and leave the rest in Ask mode. The Ryze AI chat has its own Tool approvals picker that starts on Skip all approvals.
Limits in numbers
| Limit | Number |
|---|---|
| Daily token budget | 200,000 Data API core tokens per property per day on a standard property, 2,000,000 on Analytics 360 |
| Hourly token budget | 40,000 per property per hour on standard, 400,000 on 360. Per Google Cloud project and property: 14,000 on standard, 140,000 on 360 |
| Concurrent requests | 10 per property on standard, 50 on 360 |
| Cost of one request | Google: most requests charge 10 or fewer tokens. More rows, more dimensions and metrics, complex filters, long date ranges and high-cardinality dimensions such as pagePath cost more |
| When quota runs out | The API returns 429 RESOURCE_EXHAUSTED. Daily quotas refresh at midnight Pacific time, hourly quotas within an hour |
| Rows per report | 10,000 if unspecified, at most 250,000 per request. Larger results are paged with offset |
| Dimensions, metrics, date ranges | 9 dimensions, 10 metrics and 4 date ranges per report. The API refused 10, 11 and 5 in the test on November 14, 2026 |
| Realtime window | The last 30 minutes (60 on Analytics 360) |
| Admin API | 1,200 requests per minute and 600 per user per minute. The Ryze AI tools only read |
| AI landing pages | The tool accepts a limit of at most 200 rows |
| Data delay | Standard properties: intraday data typically 2 to 6 hours, daily data 12 hours. Google says processing can take 24 to 48 hours and data can change meanwhile |
| Demographic dimensions | 120 potentially thresholded requests per property per hour |
| Antigravity timeouts | 5 minutes to connect, 3 minutes per tool call, set with timeoutSeconds |
Sources: Data API quotas, runReport reference, realtime basics, Admin API quotas, data freshness, Antigravity MCP. Checked November 14, 2026.
What the default connection did in the test
Each row is a call made through the Ryze AI connector on November 14, 2026, from Claude Code, with a standard GA4 property in a test workspace. No property name, ID or metric value is shown here.
| What was run | What came back |
|---|---|
| listAccountSummaries with only the workspace | Worked. It returned accountSummaries, each with propertySummaries (property, displayName, propertyType, parent and canEdit). |
| runRawReport for one day and one metric (sessions) with returnPropertyQuota on | Worked. One row came back with metricHeaders, rowCount, metadata (currency code and time zone) and a propertyQuota block whose totals equal Google's standard-property limits. |
| runRawReport with a dimension name that does not exist | Refused with 400 INVALID_ARGUMENT. No data returned. |
| runRawReport with a metric name that does not exist | Refused with 400 INVALID_ARGUMENT. No data returned. |
| runRawReport with a property ID that does not exist | Refused with status not_allowed. No data returned. |
First 3 prompts to run
1. Find the property and check traffic by channel
List every GA4 property my Google login can read. For the one called by my site, show sessions, key events and revenue by default channel group for last month against the month before.
Tools used: google_analytics__listAccountSummaries, then google_analytics__runRawReport
What comes back: The accounts and properties with their IDs, then one report with two named date ranges and one row per channel group. Revenue is zero if ecommerce tracking is not set up.
2. See which AI assistants send visits
Which AI assistants sent visits to my site in the last 30 days, compared with the 30 days before? Then show the daily trend for ChatGPT and Perplexity.
Tools used: google_analytics__getAiTrafficByEngine, google_analytics__getAiTrafficDaily
What comes back: Visits grouped by source engine for both periods, then a day-by-day series. GA4 reports visits that arrive from AI assistants. It does not measure whether an assistant mentions your brand.
3. Find the landing pages that AI visits land on
List the landing pages that receive AI-referred visits and each AI referral source with its sessions and conversions.
Tools used: google_analytics__getAiLandingPages, google_analytics__getAIReferrals
What comes back: Up to 200 landing pages, and the referral sources with sessions and conversions.
No result tables are shown on this page, because the test calls ran on a real property and no account data is published. Replace the property and the periods with your own.
10 jobs to hand to Antigravity
Ten jobs to hand to Antigravity, each matched to the tool it uses. Only the account listing and the core report were run in the test. The rest follow the tool definitions loaded that day.
| Job | Ask Antigravity | Tool | Default connection |
|---|---|---|---|
| List properties | Which GA4 properties can this login read, with IDs | listAccountSummaries | Yes, run in the test |
| Channel comparison | Sessions, key events and revenue by default channel group, this month against last | runRawReport | Yes, up to 4 date ranges |
| Top landing pages | Top landing pages by sessions with engagement rate and key event rate for 28 days | runRawReport | Yes |
| Purchase revenue | Purchase revenue and purchases by source and medium | runRawReport | Yes, if ecommerce tracking is set up |
| Device pivot | A pivot of sessions by channel across device categories | runPivotReport | Yes, not run in the test |
| Live visitors | Who is on the site right now, by country and device | runRealtimeReport | Yes, last 30 minutes only |
| Property setup | List key events, custom dimensions and audiences | runAdminRead | Yes, GET only, not run in the test |
| AI engines | Which AI assistants sent visits, against the prior period | getAiTrafficByEngine | Yes, not run in the test |
| AI trend | Daily visits from ChatGPT and Perplexity | getAiTrafficDaily | Yes, not run in the test |
| AI landing pages | Landing pages that receive AI-referred visits, with referral sources | getAiLandingPages, getAIReferrals | Yes, up to 200 rows |
Not possible: creating, editing or deleting properties, key events, audiences or any other GA4 setting, because there is no write tool. Universal Analytics properties are out of scope.
8 ways to connect Antigravity to Google Analytics
There are eight ways to give Antigravity access to Google Analytics 4. This guide uses the first one, the Ryze AI connector, as the main way: you sign in to Google once in Ryze AI, create no Google Cloud project and paste one address. The others were checked on November 14, 2026 and are listed with what each needs.
| Way | Runs where | Setup in Antigravity | What it reaches in GA4 | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI | A serverUrl entry in mcp_config.json and a browser sign-in | 9 read tools: reports, pivot, realtime, Admin reads, account listing and 4 AI-traffic tools | Paid Ads $89 per month, 7-day free trial; connecting is free |
| Google's analytics-mcp, local | On your computer | A command entry in mcp_config.json (pipx run analytics-mcp). Needs Python 3.10, a Google Cloud project with the Admin and Data APIs enabled and Application Default Credentials | Read by default. Google's docs page lists 9 read tools. The README lists 13, including 3 opt-in write tools behind --allow-write | No price stated, open source (Apache-2.0) |
| Google's analytics-mcp, self-hosted HTTP | On infrastructure you run | Run it with --transport http, create your own Google OAuth web client, then add its address. The README names no chat assistant for this mode, so whether Antigravity accepts it is not stated | Same tools as the local server | No price stated; you pay for hosting |
| Composio | Hosted by Composio | Remote address https://connect.composio.dev/mcp, then sign in and connect Google Analytics. Composio lists an Antigravity page for its toolkit | 82 tools, read and write, including Create Audience | Free $0 with 10,000 tool calls per month; Standard $18 per seat per month |
| Zapier MCP | Hosted by Zapier | Add Zapier as a connector over Streamable HTTP. Antigravity is on Zapier's list of MCP clients | 6 Google Analytics 4 actions, read and write, such as Run Report and Create Conversion Event | Each tool call uses 2 tasks; Free $0 with 100 tasks per month |
| Windsor.ai | Hosted by Windsor.ai | Connect GA4 as a data source in Windsor, then add the Windsor connector. Windsor publishes an Antigravity guide | Read-only for GA4. The connector has 19 tools in total | Free $0 after a 30-day trial; Basic $23 per month |
| Coupler.io | Hosted by Coupler.io, on a synced copy of the data | Build a GA4 data flow, then use the Custom MCP option with an access token. Antigravity's docs describe a headers object for bearer tokens, but Coupler does not list Antigravity | Read-only, up to 10 metrics and 9 dimensions per data flow, refreshed on a schedule | Free $0 with manual refresh; Starter $32 per month |
| surendranb/google-analytics-mcp | On your computer | A uvx entry in mcp_config.json. The README names Google Antigravity. Needs a service account JSON file and your property ID | 8 read tools, including get_ga4_data and run_realtime_report | Free, MIT licence, 244 GitHub stars on November 14, 2026 |
Three Google options that do not fit this job
- Google's agent skills for Analytics. Two instruction files for coding agents, with Antigravity named. They help the agent write Data API and Admin API code and carry no data connection of their own.
- The Ask Advisor chat method. An alpha Data API method that returns answers from Ask Advisor to code you write, added September 14, 2026. It is not a connector you add to Antigravity.
- Google's hosted Data API MCP endpoint. Google's reference page for it returned 404 on November 14, 2026 while a Markdown copy loaded, and the endpoint is not on Google Cloud's list of remote MCP servers. Connecting needs your own Google credentials, because Google's remote MCP servers do not support Dynamic Client Registration. It is not treated here as a tested or announced route.
Which one to pick
Ryze AI is the best way to connect Antigravity to Google Analytics for read-only reporting and AI-traffic questions without a Google Cloud project, with one caveat: it has no GA4 write tools and needs a paid plan or free trial for the tools. Choose Google's local analytics-mcp when you want a free server and can set up Python, a Google Cloud project and credentials, and when you accept it asks Antigravity to run a command on your machine. Choose a self-hosted HTTP server when a team shares one server and you can run it. Composio and Zapier fit teams that already use them for other apps and want GA4 write actions. Windsor.ai and Coupler.io fit teams that already pull GA4 into a reporting tool.
Sources: Google Analytics MCP docs, googleanalytics/google-analytics-mcp, Google Analytics agent skills, Ask Advisor chat method, Google Cloud remote MCP servers, Google Cloud MCP authentication, Composio Google Analytics, Composio pricing, Zapier MCP for Google Analytics 4, Zapier pricing, Windsor.ai GA4 MCP, Windsor.ai pricing, Coupler.io Google Analytics MCP, Coupler.io pricing, surendranb/google-analytics-mcp, Ryze AI Google Analytics guide. Checked November 14, 2026.
Antigravity and Google Analytics MCP: dates that matter
| Date | What happened |
|---|---|
| May 6, 2024 | Data API: key event dimensions and metrics introduced. conversions becomes a deprecated metric name, replaced by keyEvents |
| November 18, 2025 | Google Antigravity launches with the Antigravity IDE (v1.11.2) |
| May 19, 2026 | Antigravity 2.0 (the App) and Antigravity CLI launch; Gemini CLI users are moved to the CLI |
| June 18, 2026 | Gemini CLI stops serving Google AI Pro, Ultra and free individual users, as announced May 19 |
| July 28, 2026 | Antigravity App v2.4.3 adds timeouts for MCP connections and tool calls |
| August 18, 2026 | Antigravity CLI v1.1.14 supports OAuth Client ID Metadata Documents for MCP servers |
| October 22, 2026 | analytics-mcp 0.8.0 adds its first write tool and the --allow-write flag |
| October 29, 2026 | Plugin Marketplace launches in the Antigravity App and CLI |
| November 3, 2026 | analytics-mcp 1.0.0 adds a multi-tenant Streamable HTTP transport and OAuth 2.1, and leaves experimental status |
| November 6, 2026 | analytics-mcp 1.1.0 adds a Dockerfile, Cloud Run docs and opt-in Admin API write tools. Antigravity CLI v1.5.2 fixes an MCP sign-in failure with Invalid PKCE code_verifier |
| November 9, 2026 | Antigravity App v2.30.0 adds the Knowledge Work layout, where Installed lists plugins only |
| November 10, 2026 | Google's Analytics MCP docs page last updated; it lists Antigravity CLI and IDE and says Gemini CLI is deprecated |
| November 13, 2026 | Antigravity CLI v1.5.8 stops signing out OAuth servers without a client secret when the access token expires |
Sources: Antigravity changelog, Google Developers Blog on Gemini CLI and Antigravity CLI, Plugin Marketplace post, analytics-mcp releases, Data API changelog, Google Analytics MCP docs. Checked November 14 and 15, 2026.
How this guide was tested
The Ryze AI side was checked on November 14 and 15, 2026. The table lists what was run and what came back.
| What was run | What came back |
|---|---|
| listAccountSummaries through the connector, November 14, 2026 | Worked and returned accounts with their properties. |
| One-day, one-metric runRawReport with returnPropertyQuota | Worked and returned a row, metadata and a quota block equal to Google's standard-property limits. |
| A dimension name and a metric name that do not exist | Both refused with 400 INVALID_ARGUMENT, each with a suggested name. |
| A property ID that does not exist | Refused with status not_allowed. |
| 10 dimensions, 11 metrics and 5 date ranges | Each refused with 400 INVALID_ARGUMENT, which fixes the caps at 9, 10 and 4. |
| Tool definitions loaded by exact name | All 9 names returned a definition and none contains a write verb. |
| The connector without a token, November 15, 2026 | Answered 401 with a Bearer challenge that points to its protected-resource metadata. |
| The connector's protected-resource and authorization-server metadata | The resource value matches the server URL as Antigravity requires. A registration endpoint is present, so Antigravity would use dynamic client registration. Client ID Metadata Documents are not supported and the S256 PKCE method is listed. |
Not run for this page: the steps inside the Antigravity IDE, App and CLI, and no Ryze AI sign-in was completed from Antigravity. Those steps follow Google's Antigravity documentation as it read on November 15, 2026. The client for the calls above was 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 would return data from a real account. No write tool exists for Google Analytics 4.
Antigravity and Google Analytics errors and fixes
Exact error messages from the test
These are the exact messages Google returned through the connector in the test on November 14, 2026. If Antigravity shows one of them, this is what it means.
| Message | What it means | What to do |
|---|---|---|
| Field trafficSauce is not a valid dimension. Did you mean manualSource? | 400 INVALID_ARGUMENT. The dimension name does not exist in the Data API. | Use a real name such as sessionSource, or take the name Google suggests. |
| Field sessionz is not a valid metric. Did you mean sessions? | 400 INVALID_ARGUMENT. The metric name does not exist. | Use the suggested name. conversions is deprecated, the current metric is keyEvents. |
| User does not have sufficient permissions for this property. | Status not_allowed. The property ID does not exist or the Google login has no role on it. Google answers the same in both cases. | Run listAccountSummaries to get the IDs the login can read, or ask a property admin for the Viewer role. |
| Requests are limited to 9 dimensions within a nested request. | 400 INVALID_ARGUMENT. One report breaks data down by at most 9 dimensions. | Ask for fewer breakdowns or split the question into two reports. |
| Requests are limited to 10 metrics within a nested request. | 400 INVALID_ARGUMENT. One report carries at most 10 metrics. | Ask for 10 or fewer, or run two reports. |
| Requests are limited to 4 dateRanges. | 400 INVALID_ARGUMENT. One report compares at most 4 date ranges. | Compare up to 4 periods, or use a date dimension over one longer range. |
Other problems
- The Google Analytics tools are missing
- Check that a Property is saved in Ryze AI; until then the card shows Require setup. If the connector was added before GA4 was connected, Antigravity may hold the old tool list, because it caches tool schemas on disk. Reload the configuration with /mcp in the CLI, use Restart in the App's MCP server menu, or remove the entry and add it again. This was not tested inside Antigravity.
- There is no MCP Servers section in the App
- You are probably in the Knowledge Work layout, where Installed lists plugins only. Switch to Software Engineering under Settings, General, Interface Layout. Business and enterprise accounts always use Software Engineering.
- The server does not connect and the file looks right
- Remote servers must use Streamable HTTP. A legacy SSE server or an httpUrl field is not supported. Use serverUrl or url.
- Every call waits for approval
- That is Antigravity's Ask mode for unconfigured MCP tools. Allow tools with mcp(ryze/google_analytics__runRawReport) style rules in the policy configuration, or pick a more permissive permission preset.
- The same server name in two config files
- Use different names in the global and workspace files. With the same name, the server that is already running keeps it.
- MCP servers are blocked on a work account
- On Gemini Enterprise an admin controls an MCP servers setting, whose default status is Disabled, and an allowed server configuration list. A custom remote server needs its url in that list. Ask your admin.
- A report returns 429 RESOURCE_EXHAUSTED
- A quota bucket reached 0. Daily quotas refresh at midnight Pacific time and hourly quotas within an hour. Ask for fewer rows, dimensions and long date ranges.
- Revenue is zero
- GA4 has no ecommerce tracking or purchase events set up, or the Google login has the No Revenue Metrics restriction.
- The numbers differ from the Google Analytics screen
- Recent data can change for 24 to 48 hours, and reports can be thresholded. Compare finished days.
Sources: Data API errors, Antigravity MCP. Checked November 14 and 15, 2026.
Terms on this page
- Property and property ID
- The unit of Google Analytics that reports are produced for. Every Data API request names its numeric property ID, shown under Admin, Property Settings.
- Key event
- An event that measures an action important to your business. It was called a conversion before; the API metric is keyEvents.
- Dimension and metric
- Metrics are measurements such as active users or event count. Dimensions break them down by criteria such as country or event name.
- Token (Data API quota)
- The unit Google charges for each report request. A standard property has 200,000 per day and 40,000 per hour.
- Default channel group
- Google's rule-based grouping of traffic sources, the dimension sessionDefaultChannelGroup, with values such as Direct, Organic Search and Paid Search.
- mcp_config.json and serverUrl
- The file where Antigravity keeps MCP servers, and the field that holds a remote server's Streamable HTTP address.
- Dynamic client registration
- The OAuth step where a client registers itself with the server, so you paste no client ID or secret. Antigravity uses it for the Ryze AI connector.
Sources: Google property ID guide, Google key events, Google channel groups, modelcontextprotocol.io. Checked November 14, 2026.
Frequently asked questions
How do I connect Antigravity to Google Analytics?
Connect Google Analytics 4 in Ryze AI under Integrations with a Google sign-in and save a Property. Then add https://connector.get-ryze.ai/mcp to Antigravity as a serverUrl entry named ryze in mcp_config.json and finish the sign-in. In the App, click Authenticate next to the server; the IDE and CLI start the sign-in themselves.
Is there a Google Analytics MCP server for Antigravity?
Yes. Google publishes analytics-mcp, an open-source server that runs on your computer, and its docs page names Antigravity CLI and IDE. The Ryze AI connector at https://connector.get-ryze.ai/mcp is a hosted option with 9 read tools. Composio, Zapier, Windsor.ai, Coupler.io and an open-source server are others.
Does Google Analytics have an official MCP server?
Yes. Google's analytics-mcp is on GitHub and PyPI and reached version 1.1.0 on November 6, 2026. Google's docs page says it is available for read requests only, while the README lists three opt-in write tools behind --allow-write, so it is read-only by default.
What is the Google Analytics MCP URL for Antigravity?
For the Ryze AI connector the address is https://connector.get-ryze.ai/mcp, the same for every user, and it goes in the serverUrl field. Google's local analytics-mcp has no address because Antigravity starts it as a command, for example pipx run analytics-mcp.
Which file do I edit to add the server in Antigravity?
Edit mcp_config.json: ~/.gemini/config/mcp_config.json for every project, or .agents/mcp_config.json inside one workspace. The IDE opens it through MCP Servers, Manage MCP Servers, View raw config. The App gives its path under Copy Config File Path.
Do I need a Google Cloud project?
No for the Ryze AI connector: you sign in with Google inside Ryze AI and create no project or OAuth client. Yes for Google's analytics-mcp, which needs a project with the Google Analytics Admin API and Data API enabled and Application Default Credentials.
Can Antigravity change my Google Analytics settings?
No through the Ryze AI connector. All 9 Google Analytics tools are read tools, the Google scope is analytics.readonly and the Admin read tool is GET only. Google's own server can write only when you start it with --allow-write and credentials that include analytics.edit.
What Google Analytics access does the connection need?
A Google login with at least the Viewer role on a GA4 property. Ryze AI asks for analytics.readonly plus openid, email and profile, and the login needs to keep every requested permission checked on the Google screen.
How much does connecting Antigravity to Google Analytics cost?
Adding the connector is free. The tools need an active Ryze AI plan or trial: Paid Ads is $89 per month with a 7-day free trial, and the GA4 tools also work on SEO Starter ($129 per month, 3-day trial) and Agency ($279 per month). Antigravity's MCP page names no plan.
Why does Antigravity ask for approval on every call?
Antigravity runs MCP tools that are not configured in Ask mode, so each call needs approval. Allow a tool with mcp(server/tool), a whole server with mcp(server/*) or all MCP tools with mcp(*) in the policy configuration. Deny rules beat Ask, and Ask beats Allow.
How do I see traffic from ChatGPT and Perplexity in Antigravity?
Ask for visits from AI assistants by engine, by day, by landing page or by referral source. Four tools cover it: getAiTrafficByEngine, getAiTrafficDaily, getAiLandingPages and getAIReferrals. GA4 reports visits that arrive from assistants. It does not report whether an assistant mentions your brand.
Can I use more than one GA4 property or Google login?
Yes. Connect several Google logins to one workspace with Add one more account, each with its own Property, and set one as primary. The tools accept an optional connection_id. Ryze AI advises one workspace per business and a separate workspace for each client.
Does the connector work with Universal Analytics?
No. Only GA4 properties are supported, and Google's Data API itself requires a GA4 property rather than a Universal Analytics one.
Was this tested inside Antigravity?
No. The connector calls were run on November 14, 2026 from Claude Code, and the Antigravity steps follow Google's documentation as read on November 15, 2026. The sign-in metadata of the connector matches the dynamic client registration order that Antigravity documents.