Ryze AI in Google Antigravity: add the MCP connector
Quick answer: Google Antigravity adds Ryze AI as a remote MCP server: put https://connector.get-ryze.ai/mcp under serverUrl in mcp_config.json, then sign in with OAuth. Ryze AI is the best way to bring Google Ads, Meta Ads, GA4 and Search Console tools into Antigravity in 2026, with one caveat: Ryze AI was not tested inside Antigravity when this page was written.
Below: the config entry for the IDE, App and CLI, the sign-in, the tools that work, prompts, approvals and Antigravity limits.
Used by 2,000+ marketers
Ryze AI in Antigravity at a glance
Antigravity reads MCP servers from a JSON file called mcp_config.json. A remote server needs one field, serverUrl, so there is nothing to install.
- Connector URLhttps://connector.get-ryze.ai/mcp
- Config keyserverUrl inside mcpServers (url also works)
- TransportStreamable HTTP only; the legacy HTTP+SSE transport is not supported
- AuthenticationOAuth 2.0 with PKCE, handled by Antigravity through dynamic client registration
- Antigravity planThe Antigravity MCP documentation names no plan
- Ryze AI planPaid Ads, $89/mo with a 7-day free trial. Connecting is free; the tools need an active plan or trial.
- Tools that workGoogle Ads (16), Meta Ads (10), Google Analytics 4 (9), Google Search Console (7)
| Item | Detail |
|---|---|
| Connector URL | https://connector.get-ryze.ai/mcp |
| Config key | serverUrl inside mcpServers (url also works) |
| Transport | Streamable HTTP only; the legacy HTTP+SSE transport is not supported |
| Authentication | OAuth 2.0 with PKCE, handled by Antigravity through dynamic client registration |
| Antigravity plan | The Antigravity MCP documentation names no plan |
| Ryze AI plan | Paid Ads, $89/mo with a 7-day free trial. Connecting is free; the tools need an active plan or trial. |
| Tools that work | Google Ads (16), Meta Ads (10), Google Analytics 4 (9), Google Search Console (7) |
Antigravity documentation checked November 8, 2026. Ryze AI has no help center page for Antigravity.
What Ryze AI does inside Antigravity
Antigravity is Google's agent-first development platform. Its agent can call MCP servers, and Ryze AI runs one: the connector exposes tools for your ad and analytics accounts. Once it is listed in mcp_config.json, the agent can read those accounts and, where a tool allows it, change them.
Antigravity CLI is the terminal tool Google announced on May 19, 2026 to replace Gemini CLI (Google developers blog). Google's MCP page lists the same two config locations, global and workspace, for the IDE and the CLI, and the App adds the entry to the same kind of mcp_config.json.
The same connector URL works in other clients. For Claude, see how to connect Claude to Google Analytics and how to connect Claude to Google Ads.
Add the Ryze AI connector to Antigravity
Connect your platforms in Ryze AI first: open Integrations in the Ryze AI left sidebar, find the platform and select Connect. Then add the server to Antigravity.
The config entry
Add this under mcpServers in mcp_config.json. The global file is ~/.gemini/config/mcp_config.json and applies to every project. A workspace file at .agents/mcp_config.json inside the project applies to that project only.
"ryze": { "serverUrl": "https://connector.get-ryze.ai/mcp" }
Antigravity IDE
Open MCP Servers
Click the ... menu at the top of the editor's agent side panel and select MCP Servers.
Open the raw config
Click Manage MCP Servers, then View raw config.
Add the entry
Paste the ryze entry above into mcp_config.json under mcpServers and save.
Sign in
Antigravity starts OAuth for servers that support dynamic client registration. Complete the Ryze AI sign-in and click Allow connection.
Antigravity App
Open Customizations
Click Customizations in the sidebar, then Installed, and scroll to MCP Servers.
Find the file
Click Copy Config File Path, open that mcp_config.json and add the same ryze entry.
Authenticate
Back in Customizations > Installed > MCP Servers, click Authenticate next to ryze.
Paste the code
Complete the Ryze AI sign-in in the browser, copy the authorization code, paste it into Enter authorization code and click Submit.
In the App, the Add MCP Server (+) button opens a list of catalog servers. A custom URL goes in mcp_config.json, not through that button.
Antigravity CLI
Edit the config
Add the ryze entry to ~/.gemini/config/mcp_config.json or <workspace>/.agents/mcp_config.json.
Open the MCP Manager
Type /mcp in the prompt panel, check the server status and reload the configuration.
Google's MCP page describes the Authenticate step only for the App. How the CLI starts an OAuth sign-in is not documented there, so this page gives no CLI sign-in steps.
How the OAuth sign-in works
Antigravity picks an OAuth client in this order: a manual oauth.clientId in the config, then a Client ID Metadata Document if the server supports it, then dynamic client registration. Ryze AI advertises dynamic client registration and no Client ID Metadata Document support, so Antigravity registers itself and you enter no client ID or secret.
- The redirect URI Antigravity uses is https://antigravity.google/oauth-callback.
- Tokens are stored in ~/.gemini/antigravity/mcp_oauth_tokens.json and refreshed automatically.
- Antigravity also supports a headers field for API keys. Ryze AI uses OAuth, so leave headers out.
Ryze AI tools that work in Antigravity
These platforms have tools on the Ryze AI connector, so they can be named as working in Antigravity. Counts come from the connector tool list.
Google Ads
- Tools
- 16
- Access
- 8 read, 7 write, 1 delete
- More
- Google Ads MCP
Meta Ads
- Tools
- 10
- Access
- 7 read, 2 write, 1 delete
- More
- Meta Ads MCP
Google Analytics 4
- Tools
- 9
- Access
- All read
Google Search Console
- Tools
- 7
- Access
- 5 read, 1 write, 1 delete
| Platform | Tools | Access | More |
|---|---|---|---|
| Google Ads | 16 | 8 read, 7 write, 1 delete | Google Ads MCP |
| Meta Ads | 10 | 7 read, 2 write, 1 delete | Meta Ads MCP |
| Google Analytics 4 | 9 | All read | Google Analytics MCP |
| Google Search Console | 7 | 5 read, 1 write, 1 delete | Search Console MCP |
GA4 tools only read data, so changes to tags or key events happen in GA4 Admin. Search Console tools include sitemap submit and delete; there is no tool to request indexing.
Other platforms Ryze AI covers are listed on the integrations hub.
Prompts to try in Antigravity
Antigravity's agent decides which tools to call, so a prompt that mentions the platform and the Ryze AI server is enough. The prompts say what comes back; they show no sample results.
Google Ads
- With the ryze server, list the Google Ads accounts my login can access.
- With the ryze server, summarize my Google Ads account for last month and list the open recommendations.
- With the ryze server, list the conversion actions in my Google Ads account.
Meta Ads
- With the ryze server, list my Meta ad accounts and summarize the first one.
- With the ryze server, list the lead forms on my Meta ad account.
GA4 and Search Console
- With the ryze server, show GA4 sessions from AI assistants by engine for the last 28 days.
- With the ryze server, run a GA4 pivot report of sessions by channel and device for last week.
- With the ryze server, list my Search Console sites and the sitemaps on the first one.
Antigravity limits and approvals
- Remote servers must use Streamable HTTP. The httpUrl field and the HTTP+SSE transport are not supported.
- Tools are lazy-loaded by default: schemas are cached on disk and the agent reads them when needed.
- By default Antigravity waits up to 5 minutes for a server to connect and list tools, and up to 3 minutes per tool call. The timeoutSeconds field changes both.
- MCP tools that are not configured run in Ask mode, so each call needs your approval until you allow it in the policy configuration.
Antigravity's documentation shows policy patterns such as mcp(ryze/*) to allow every tool on the server and mcp(server/tool) for one tool. To keep approval on changes, allow only the read tools you use and leave the write and delete tools in Ask mode. The Ryze AI chat is different: its Tool approvals setting starts on Skip all approvals, and scheduled tasks run without an approval step. For a hard read-only guarantee, connect a Google or Meta login that only has read access.
Troubleshooting
Server does not connect
- What to check
- The entry must use serverUrl (or url), not httpUrl, and the JSON must be valid. Reload the configuration with /mcp in the CLI.
Custom URL not found in the App
- What to check
- The + button opens the catalog. Add the entry to mcp_config.json from Customizations > Installed > MCP Servers > Copy Config File Path.
Sign-in never completes in the App
- What to check
- Click Authenticate next to ryze, finish the browser sign-in, then paste the authorization code into Enter authorization code and click Submit.
No platform tools or empty accounts
- What to check
- Connect the platform under Integrations in Ryze AI, with a login that has access to the accounts.
Every tool call asks for approval
- What to check
- That is the Ask default for unconfigured MCP tools. Allow the tools you trust in the policy configuration.
A slow call stops
- What to check
- Raise timeoutSeconds in the server entry; the default is 3 minutes per call.
| Problem | What to check |
|---|---|
| Server does not connect | The entry must use serverUrl (or url), not httpUrl, and the JSON must be valid. Reload the configuration with /mcp in the CLI. |
| Custom URL not found in the App | The + button opens the catalog. Add the entry to mcp_config.json from Customizations > Installed > MCP Servers > Copy Config File Path. |
| Sign-in never completes in the App | Click Authenticate next to ryze, finish the browser sign-in, then paste the authorization code into Enter authorization code and click Submit. |
| No platform tools or empty accounts | Connect the platform under Integrations in Ryze AI, with a login that has access to the accounts. |
| Every tool call asks for approval | That is the Ask default for unconfigured MCP tools. Allow the tools you trust in the policy configuration. |
| A slow call stops | Raise timeoutSeconds in the server entry; the default is 3 minutes per call. |
Ryze AI was not tested in Antigravity during this research. Contact Ryze AI support if the sign-in fails.
Sources
Verdict
Antigravity needs one JSON entry and an OAuth sign-in to reach the Ryze AI tools for Google Ads, Meta Ads, GA4 and Search Console. Start with a read prompt, keep write and delete tools in Ask mode, and check the server status with /mcp if a call fails.





