By Ira Bodnar, Ryze AI · Updated · Connector tested November 13, 2026
Quick answer
The main way to connect Antigravity to Google Ads is the Ryze AI connector. Connect Google Ads in a Ryze AI workspace with the Google login that reaches your ad accounts, then give Antigravity's mcp_config.json a ryze entry whose serverUrl is https://connector.get-ryze.ai/mcp and finish the Ryze AI sign-in. The agent then has 16 Google Ads tools: 8 that read, 7 that write and 1 that deletes.
- In Ryze AI open Integrations, find Google Ads and click Connect with every permission checked
- In Antigravity open MCP Servers, Manage MCP Servers, View raw config and add the ryze entry
- Complete the Ryze AI sign-in and click Allow connection
- Start a new agent chat and ask for last week's spend by campaign
Antigravity to Google Ads at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector: a hosted MCP server that Antigravity reaches through one serverUrl entry, with nothing to install or keep running |
| Server address | https://connector.get-ryze.ai/mcp |
| Where the entry goes | mcp_config.json, either ~/.gemini/config/mcp_config.json for every project or .agents/mcp_config.json inside one workspace. The IDE, the App and the CLI read the same format |
| Sign-in | OAuth 2.0 with PKCE in the browser. The connector offers dynamic client registration, so you type no client ID or secret. The App adds an Authenticate button and a code to paste back |
| Google Ads tools | 16 in all: 8 read, 7 write and 1 delete, each with an optional connection_id |
| Can it change campaigns | Yes, when the connected Google user has Standard or Admin access. Antigravity keeps any MCP tool without a rule in Ask mode, so each change waits for your click by default |
| Other data in the same chat | Meta Ads, GA4 and Search Console tools, among others, when those platforms are connected in the same Ryze AI workspace |
| Antigravity plan needed | None is named. Google's MCP page lists no plan, and the plans page gives every plan all product features |
| Ryze AI price | Adding the connector costs nothing. The tools need an active plan or trial: Paid Ads is $89 per month with a 7-day free trial, Agency $279 per month |
| Google's own options for Antigravity | google-ads-mcp, an open-source server you run yourself that reads reports and handles assets, video uploads and labels but not campaigns, and the Developer Assistant plugin, which runs read-only reports and writes changes out as code |
| Last tested | Connector checked on November 13, 2026, and nine Google Ads calls sent through it from Claude Code that day. Sign-in data compared with Antigravity's OAuth order on November 15, 2026. Nothing was run inside Antigravity |
Before you start
- Google Antigravity. Google's MCP documentation for Antigravity names no plan, and its FAQ says personal Google accounts can use Antigravity on any plan, the free tier included. The IDE, the App and the CLI all read the same mcp_config.json format, so any of them works. Enterprise accounts cannot sign in to the standalone IDE. They use the App, the CLI or the IDE extensions, and an admin may first have to allow MCP servers in Gemini Enterprise.
- A Google login with access to your Google Ads accounts. Sign in with the login that reaches the accounts you want. Standard or admin access is needed to allow changes. For a hard read-only guarantee, connect a login that only has read access. Agencies connect the manager (MCC) login once.
- A Ryze AI workspace on a plan or free trial. Paid Ads is $89 per month with a 7-day free trial, and Agency is $279 per month. Connecting is free; the Google Ads tools need an active plan or trial. Annual billing takes 30% off the first year.
How to connect Antigravity to Google Ads
These steps are for the Antigravity IDE. Two happen in Ryze AI and Google, four in the editor. The App and the CLI use the same config entry and are covered below.
Connect Google Ads in Ryze AI
Create a Ryze AI account or sign in, open Integrations in the left sidebar and find Google Ads under Advertising. Click Connect.
Sign in with Google and approve every permission
Sign in with the Google login that has access to your ad accounts and keep every requested permission checked. Back in Ryze AI the card shows Connected. There is no account to pick: Ryze AI sees every Google Ads account that login can reach.
Open the raw MCP config in the Antigravity IDE
In the agent side panel of the editor, click the ... menu at the top and select MCP Servers. Click Manage MCP Servers, then View raw config. This opens mcp_config.json. The global file is ~/.gemini/config/mcp_config.json and a per-workspace file is .agents/mcp_config.json.
Add the ryze entry
Under mcpServers add an entry named ryze with the serverUrl https://connector.get-ryze.ai/mcp and save the file. There is no client ID or secret to enter, because Antigravity handles OAuth 2.0 with PKCE on its own for servers that support dynamic client registration, and the Ryze AI connector does.
Sign in to Ryze AI
Antigravity handles the browser sign-in for the server by itself, and Google's MCP page gives no IDE steps for how it begins. When the Ryze AI page comes up, choose the workspace that holds your Google Ads connection and click Allow connection.
Ask your first question
Open a new agent chat and ask: Which campaigns spent the most in the last 7 days, and what was the ROAS of each? Antigravity asks for approval before an MCP tool runs until you allow it, so approve the first call.
The Ryze AI help article for Google Ads covers the Google side of the connection. There is no Ryze AI help page for Antigravity, and Ryze AI was not tested in it for this page.
Sources: Google's Antigravity MCP documentation, checked November 15, 2026, and the Ryze AI Google Ads guide.
Antigravity App
The Antigravity App lists its MCP servers on the Customizations page and has an Authenticate button of its own, so signing in works differently from the IDE. Since App 2.30.0 there is one catch: in the Knowledge Work layout the Installed tab shows plugins only, and the MCP Servers section is not there. Switch to Software Engineering under Settings > General > Interface Layout before step 1. Business and enterprise accounts always get the Software Engineering layout.
- Click Customizations in the sidebar, then Installed, and scroll to MCP Servers.
- Click Copy Config File Path and add the ryze entry shown below to that mcp_config.json.
- Back in Customizations, Installed, MCP Servers, click Authenticate next to ryze.
- Complete the Ryze AI sign-in in the browser, copy the authorization code, paste it into Enter authorization code and click Submit. The server then reconnects by itself.
The entry to add is the same in the IDE, the App and the CLI:
{
"mcpServers": {
"ryze": {
"serverUrl": "https://connector.get-ryze.ai/mcp"
}
}
}The App's Add MCP Server (+) button opens a searchable catalog with no field for an address, so a custom server like this one is written into mcp_config.json by hand. Remote servers have to speak Streamable HTTP: Google's docs rule out the legacy HTTP+SSE transport and the httpUrl key, and take url as another name for serverUrl. Antigravity's OAuth redirect URI is https://antigravity.google/oauth-callback.
Antigravity CLI
The Antigravity CLI (agy) loads the same two files. Put the ryze entry in ~/.gemini/config/mcp_config.json or in <workspace>/.agents/mcp_config.json, then type /mcp in the prompt panel. The MCP Manager that opens shows a status ring for each server, reloads the configuration and shows connection logs. Give the global and the workspace entry different names, because when two files use one name the server already running keeps it. Gemini CLI, which the Antigravity CLI replaced for personal accounts, declared servers inside ~/.gemini/settings.json, and Google's migration page asks for serverUrl in place of url or httpUrl.
Google writes Authenticate steps for the App only. The CLI changelog refers to the sign-in link for MCP servers that use OAuth (version 1.5.2, November 6, 2026), but no Google page lists the steps, so this guide does not either. The changelog also names mcp add, remove, list, enable and disable subcommands for the user-level file; their exact syntax is unpublished, so no command line is given here. Tokens are kept in ~/.gemini/antigravity/mcp_oauth_tokens.json, where expired ones are refreshed and invalid ones removed.
Sources: Google's Antigravity MCP documentation, the Gemini CLI to Antigravity CLI update, the Gemini CLI migration page, the Antigravity changelog and the connector checks on this page. Checked November 15, 2026.
Antigravity and MCP: the facts in one table
| Topic | What Google's Antigravity pages say |
|---|---|
| Where MCP works | The MCP page covers the Antigravity App, the Antigravity CLI and the standalone IDE. The Visual Studio extension page documents the same two mcp_config.json files |
| Config format | One schema on every surface: an mcpServers map keyed by server name. An enabled plugin can bring servers in its own <plugin-root>/mcp_config.json |
| Local or remote | command starts a local stdio process, and serverUrl (or url) points at a remote server over Streamable HTTP. Each entry names exactly one of the two |
| Headers | A headers object on a remote entry sends extra HTTP headers, such as an Authorization bearer token or an API key |
| OAuth | Automatic for servers offering Client ID Metadata Documents or dynamic client registration. Antigravity tries oauth.clientId from the file first, a metadata document second and registration third. In the IDE, metadata documents need version 2.6.0 or later |
| Approvals | MCP tools with no rule wait in Ask mode. Rules are written mcp(server/tool), mcp(server/*) or mcp(*), and Deny outranks Ask, which outranks Allow |
| Presets that stop asking | Turbo, in the App on a personal account, runs MCP tools without a prompt. In the CLI the default request-review prompts first, while always-proceed skips the prompt except where an ask or deny rule applies |
| Hiding tools | enabledTools keeps only the tools you list, disabledTools hides the ones you list, and disabled: true pauses a server without deleting its entry |
| Loading and output | Tools load lazily from schemas cached on disk unless a tool is marked eager. In the CLI a lazily loaded tool hands up to 10 KB of its result straight to the agent |
| Plan and enterprise | No plan is named for MCP. The standalone IDE is not supported for enterprise deployments, and admins can set MCP allowlists |
| Moving servers over | With the Software Engineering role at first launch, the App offers to import MCP servers, skills and rules from Claude Code, Codex, Cursor and Gemini CLI |
Sources: MCP, permissions, settings, plans, enterprise, getting started, Visual Studio extension and changelog pages of Google Antigravity. Checked November 15, 2026.
Other AI clients
The same URL works in other MCP clients. Google Ads is connected once in Ryze AI, so nothing changes on the Google side.
Gemini
Google's other assistant has its own steps. See How to connect Gemini to Google Ads. For the Antigravity client in general, see Ryze AI in Antigravity.
Claude and Claude Code
Claude uses a custom connector with the same URL. See How to connect Claude to Google Ads and Claude Code.
Google Ads access and permissions
The Google side of the connection is a Google sign-in inside Ryze AI. Antigravity adds its own OAuth step on top, for the Ryze AI connector. Four things decide what the agent can see and change.
- Google Ads scope
- The Ryze AI sign-in asks for the Google Ads scope https://www.googleapis.com/auth/adwords plus openid, email and profile. Keep every requested permission checked, and use a login with access to at least one Google Ads account.
- Which accounts
- Ryze AI sees every Google Ads account the connected login can reach, including client accounts under a manager (MCC) login. Agent default accounts picks the ones the agent works with first. Over MCP every Google Ads tool takes an optional connection_id for a specific connected login, and client accounts under a manager need loginCustomerId.
- Read or write
- Changes need standard or admin access in Google. Google Ads permissions are set in Google, not in Ryze AI, so a read-only login cannot make changes.
- How Antigravity signs in
- Antigravity tries a manually set oauth.clientId first, then a Client ID Metadata Document if the server supports one, then dynamic client registration. The Ryze AI connector advertises dynamic client registration and no metadata document, so the third path applies and you enter nothing.
The four Google scopes behind the connection
Antigravity signs in to the connector only, and the connector's discovery data names two scopes for that, mcp:read and mcp:write. The Google login and its OAuth scopes stay inside Ryze AI. The Google sign-in there asks for four scopes, each described below in Google's own words.
| Scope requested from Google | How Google describes it |
|---|---|
| https://www.googleapis.com/auth/adwords | See, edit, create, and delete your Google Ads accounts and data. |
| openid | Associate you with your personal info on Google |
| See your primary Google Account email address | |
| profile | See your personal info, including any personal info you've made publicly available |
Google Ads has no separate read-only scope. Google's access model page says the API uses the same scopes for reading and for changing data, so the adwords scope alone cannot keep Antigravity to reports. The access level of the Google user you connect is what draws that line.
What each Google Ads access level allows
Google's access-level table, as it read on November 14, 2026. Billing access only sees billing, and Email-only access appears in none of these rows.
| In a Google Ads account, the user | Access levels that allow it |
|---|---|
| Can view campaigns and use planning tools | Read-only, Standard, Admin |
| Can edit and run campaign performance reports | Read-only, Standard, Admin |
| Can edit campaigns | Standard, Admin |
| Can view users, managers, and product links | Read-only, Standard, Admin |
| Can add or remove product links | Admin |
| Can give account access, change access levels, and cancel invitations from other users | Admin |
| Can view billing information | Billing, Read-only, Standard, Admin |
Agencies working through a manager account should know three rules from Google's API pages. Someone invited to a manager account reaches the client accounts linked below it, and a role given at manager level carries down to them. Google's list of accessible customers holds only the accounts a user reaches directly, so a client account may not show up in listAccessibleCustomers. When a call goes through a manager, it has to carry the manager's customer ID as login-customer-id, which the Ryze AI tools accept as loginCustomerId in digits only. Without it Google answers AuthorizationError.USER_PERMISSION_DENIED.
What the default connection does not include: Google Ads accounts the connected login cannot open, client accounts under a manager login that nobody connected, any change while the connected user is Read-only, video file uploads (a video ad needs a YouTube link), taking people off a Customer Match list, since the upload tool only adds them, and restoring a removed item, because Google Ads has no undo.
Sources: Google OAuth 2.0 scopes, Google Ads API access model, Google Ads API call structure, Google Ads access levels. Checked November 14, 2026.
Limits that shape the answers
These limits shape what comes back in prompts. The first three come from Ryze AI's documentation of the connection, the last three from Google's Antigravity MCP page.
| Area | Limit |
|---|---|
| Change history | GAQL change history from change_event covers up to the last 30 days and shows who changed what and when. |
| Reporting lag | Ryze AI cannot speed up Google's own reporting lag for recent conversions, or Google's review of new campaigns, which takes about a business day. |
| Removals | Google Ads has no undo, so a removed item cannot be re-enabled. Video ads need a YouTube link, because video files cannot be uploaded. |
| Timeouts | Antigravity waits up to 5 minutes for a server to connect and list its tools and up to 3 minutes for each tool call. The timeoutSeconds setting changes both. |
| Tool loading | MCP tools load lazily by default: schemas are cached on disk and the agent reads them when needed. |
| Tool approval | An MCP tool without a configured rule runs in Ask mode, so each call needs your approval until you allow it in the policy configuration. |
Sources: the Ryze AI Google Ads guide and Google's Antigravity MCP documentation, checked November 15, 2026.
Removing access
To remove access, disconnect Google Ads on its card in Ryze AI, or withdraw the access on your Google Account permissions page (myaccount.google.com/permissions). In Antigravity, delete the ryze entry from mcp_config.json, or set disabled: true on it to pause the server and keep the entry. In the App, More actions (⋮) next to the server also offers Disable and Delete. Stored OAuth tokens live in ~/.gemini/antigravity/mcp_oauth_tokens.json.
What Antigravity can do in Google Ads
The Ryze AI connector exposes 16 Google Ads tools: 8 that read, 7 that write and 1 that deletes. In the tool definitions seen on November 13, 2026, all 16 take an optional connection_id, and all but listAccessibleCustomers take customerId and loginCustomerId.
| Tool (google_ads__ prefix) | Type | What it does |
|---|---|---|
| getAccountSummary | Read | Returns aggregate account metrics for a date range. |
| getAccountHierarchy | Read | Returns the manager and sub-account hierarchy for an account. |
| listAccessibleCustomers | Read | Lists every Google Ads customer account the connected login can access. |
| listConversionActions | Read | Lists the conversion actions in an account. |
| listRecommendations | Read | Lists Google's optimization recommendations for an account. |
| runRawGaql | Read | Runs a raw GAQL query against the Google Ads API, including change history from change_event. |
| generateKeywordIdeas | Read | Generates Keyword Planner ideas from seed keywords, a URL or both. |
| generateKeywordHistoricalMetrics | Read | Returns Keyword Planner history (average monthly searches, competition, top-of-page bid range) for a known keyword list. |
| runRawMutate | Write | Creates or updates resources such as campaigns, budgets, ad groups, ads, keywords, criteria and assets through a raw mutate. |
| runRawCustomAudienceMutate | Write | Creates or updates custom audiences based on keywords, URLs, place categories or apps. |
| runRawUserListMutate | Write | Creates or updates user lists, including Customer Match lists. |
| uploadCustomerMatchMembers | Write | Adds people to a Customer Match list. The server normalizes and SHA-256 hashes every identifier before it reaches Google. |
| uploadImageAsset | Write | Uploads an image from a URL as an image asset that can then be linked to campaigns, ad groups, asset groups or ads. |
| applyRecommendation | Write | Applies Google's recommendations. |
| dismissRecommendation | Write | Dismisses Google's recommendations. |
| runRawMutateDelete | Delete | Removes resources through a raw mutate. Removals are permanent, and the tool description tells the agent to use it only on an item-by-item approved list. |
In Antigravity, an MCP tool with no configured rule runs in Ask mode, so every call waits for your approval. Google's docs give the rule forms mcp(server/tool) for one tool and mcp(server/*) for all tools on a server. Allow the read tools if you like, and leave the 8 write and delete tools in Ask mode, because they change live campaigns and spend. Four of them take a validateOnly switch for a dry run (runRawMutate, runRawMutateDelete, runRawCustomAudienceMutate and runRawUserListMutate), so you can ask the agent for a dry run of a change before the real call. The item-by-item rule of the delete tool lives only in the tool's description, and the server does not enforce it. In the Ryze AI chat, changes follow the chat's Tool approvals setting, which starts on Skip all approvals.
Google Ads limits in numbers
Google meters the API per Google Cloud project and per account, and the daily figures depend on the project's API access level. Ryze AI's facts do not name the level of the project behind the connector, so the first row lists Google's figure for each level and this guide does not say which one applies to the connector. If you run google-ads-mcp or the Developer Assistant, your own project's level applies.
| Limit | Figure or rule | Who sets it |
|---|---|---|
| API operations per day | Test access: 15,000, test accounts only. Explorer: 2,880 against production accounts and 15,000 against test accounts. Basic: 15,000. Standard: no daily cap, after a review that typically takes 10 business days | |
| What a day and an operation are | A day is a sliding 24 hours per Google Cloud project. One Search or SearchStream request is one operation however many batches it returns; refused requests count, follow-up pages with a valid page token do not | |
| Explorer access gaps | No planning services such as Keyword Planner, no account creation, user management or billing. Those need Basic or Standard | |
| Rate limits | Requests per second are limited per customer ID and per Cloud project with a token bucket, and Google also names limits on requests and operations per minute. None has a published number. The error is RESOURCE_TEMPORARILY_EXHAUSTED, and Google suggests backing off 2, 4, then 8 seconds plus jitter | |
| One page of a report | Up to 10,000 rows, fixed. A next_page_token stops working after about two hours unused | |
| One response | 64 MB, the gRPC message ceiling in Google's client libraries. A bigger answer fails with RESOURCE_EXHAUSTED (HTTP 429) | |
| IN clause in GAQL | 20,000 values at most, or FILTER_HAS_TOO_MANY_VALUES | |
| One mutate request | 10,000 operations at most, or TOO_MANY_MUTATE_OPERATIONS | |
| Keyword Planner calls | 1 request per second per customer ID, counted as 60 per 60 seconds. One history request takes up to 10,000 keywords and 10 geo targets. Monthly volumes go back up to 4 years, and the competition index runs from 0 to 100 | |
| Change history | The past 30 days. The query needs a date filter and a LIMIT of 10,000 rows or fewer, and a change can take up to 3 minutes to appear | |
| Data freshness | In most cases clicks, impressions and cost refresh hourly. Impression share and auction insights usually update once a day, and search click share runs 3 days behind. Conversions under attribution models other than last click arrive later | |
| Customer Match uploads | 20 identifiers per UserData object and 100,000 per upload request; Google recommends at most 1,000,000 operations per job | |
| API versions | A major version lives about 12 months. v26 came out on October 14, 2026, and the oldest one still served, v23, sunsets in February 2027 | |
| Ryze AI tool inputs | A GAQL query of 1 to 10,000 characters, 1 to 100,000 Customer Match members per call, and an image asset name of 1 to 128 characters | Ryze AI |
| Tool output in the CLI | Up to 10 KB of a lazily loaded tool's result goes to the agent directly | Antigravity |
Sources: Google Ads API quotas, access levels, rate limits, paging, keyword historical metrics, change event, data freshness and sunset dates, checked November 14, 2026. Ryze AI tool inputs from the test of November 13, 2026. The CLI figure from the Antigravity changelog, checked November 15, 2026.
Google Ads calls tested through the connector
On November 13, 2026 the Ryze AI connector took nine Google Ads calls from Claude Code, on the default connection to a real account. Antigravity was not the client, but it talks to the same server and the same tools. Two calls were meant to bring data back and seven were built to be refused. Account IDs and every figure from the account are left off this page.
| Call | Tool | Outcome |
|---|---|---|
| List the accounts the login reaches | listAccessibleCustomers | Worked. Resource names came back as customers/ followed by an ID; the IDs are not shown here |
| Keyword history for google ads mcp, connect chatgpt to google ads and google ads api, in English for the United States on Google Search | generateKeywordHistoricalMetrics | Worked. 3 results, each with average monthly searches, competition, a competition index, a top-of-page bid range and 12 monthly values from November 2025 to October 2026 |
| A query selecting campaign.daily_budget | runRawGaql | Refused, HTTP 400, UNRECOGNIZED_FIELD |
| A query on campaign_experiment | runRawGaql | Refused, HTTP 400, UNRECOGNIZED_FIELD |
| A query that opens with SELEC | runRawGaql | Refused, HTTP 400, EXPECTED_SELECT |
| change_event without a LIMIT | runRawGaql | Refused, HTTP 400, LIMIT_NOT_SPECIFIED |
| change_event with LIMIT 10001 | runRawGaql | Refused, HTTP 400, INVALID_LIMIT_CLAUSE |
| A query for a made-up 10-digit customer ID | runRawGaql | Refused, HTTP 401, CUSTOMER_NOT_FOUND |
| Keyword history with the bare IDs 1000 and 2840 for language and location | generateKeywordHistoricalMetrics | Refused, HTTP 400, RESOURCE_NAME_MALFORMED |
Each refusal arrived as JSON with a code, a message, a status and a GoogleAdsFailure detail holding the error code and a request ID. The payloads named the API version in use, google.ads.googleads.v24.
First 3 prompts to run
1. Find where spend is going
Which campaigns spent the most in the last 7 days? Show spend, conversions and ROAS for each, and flag the ones where spend rose while conversions did not.
Tools used: getAccountSummary, runRawGaql
What comes back: A per-campaign table for the date range from your own account. Recent conversions can still be catching up because of Google's reporting lag.
2. Audit what changed
Pull the change history for the last 14 days. Who changed budgets, bids or keywords, and when? List each change in order.
Tools used: runRawGaql against change_event
What comes back: A dated list of changes with the user and the resource touched. Change history covers up to the last 30 days.
3. Research keywords for a landing page
Generate keyword ideas from my pricing page URL, then show average monthly searches, competition and the top-of-page bid range for the 15 most relevant ones.
Tools used: generateKeywordIdeas, generateKeywordHistoricalMetrics
What comes back: A keyword list with Keyword Planner history. Nothing is added to a campaign unless you ask for it.
Each answer comes from your own accounts, so this page describes what comes back instead of showing sample numbers. Changes to budgets, bids and keywords run on live campaigns.
10 jobs to hand to Antigravity
Ten jobs to hand the Antigravity agent, each with the tool that does the work. In the November 13 test, sent through the connector from Claude Code, only the account list and the keyword history returned a result, and the change history job got as far as its two LIMIT refusals; the other rows follow Ryze AI's tool list. A job that changes the account needs a Google user with Standard or Admin access, and it waits in Ask mode unless you have allowed the tool.
| Job | Ask the agent | Tool | Works on the default connection |
|---|---|---|---|
| Spend and ROAS by campaign | Show spend, conversions and ROAS for each campaign over the last 30 days, biggest spender first. | getAccountSummary, runRawGaql | Yes |
| Change log | Who edited budgets, bids or keywords in the last 14 days? Keep the LIMIT at 10,000 or less. | runRawGaql on change_event | Yes, inside Google's 30-day window |
| Account map | List every account my login reaches, then show which client accounts sit under each manager. | listAccessibleCustomers, getAccountHierarchy | Yes. The account list ran in the test |
| Keyword ideas | Suggest keywords for this landing page URL and these three seed terms. | generateKeywordIdeas | Yes |
| Keyword volumes | For this keyword list, give average monthly searches, competition and the top-of-page bid range in the United States. | generateKeywordHistoricalMetrics | Yes. It ran in the test for three keywords |
| Conversion setup | List the conversion actions set up in this account. | listConversionActions | Yes |
| Google's recommendations | List Google's recommendations for this account, apply the two I pick and dismiss the rest. | listRecommendations, applyRecommendation, dismissRecommendation | Listing, yes. Applying or dismissing needs Standard or Admin access |
| Campaign edits | Add these negative keywords to the brand campaign and lower its daily budget by 10 percent. | runRawMutate | Yes with Standard or Admin access. It fails with Read-only access |
| New image asset | Upload the image at this public URL and link it to the asset group of my Performance Max campaign. | uploadImageAsset, runRawMutate | Yes with Standard or Admin access. Video files cannot be uploaded; a video ad takes a YouTube link |
| Customer Match list | Create a Customer Match list and add the contacts I give you to it. | runRawUserListMutate, uploadCustomerMatchMembers | Yes with Standard or Admin access. Contacts are hashed with SHA-256 before they reach Google, and the upload can only add people |
5 ways to connect Antigravity to Google Ads
Five ways can give the Antigravity agent your Google Ads accounts. This guide treats the first, the Ryze AI connector, as the main way: Antigravity stores one serverUrl entry, the Google sign-in happens once inside Ryze AI, and there is no Google Cloud project, OAuth client or local Python install to set up. The other four name Antigravity on their own pages, read on November 14, 2026, and none of them was installed for this guide. The setup column shows how each one goes into Antigravity.
| Way | Runs where | Setup in Antigravity | What it reaches in Google Ads | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI. One address for Antigravity, Claude, ChatGPT and other MCP clients | A ryze entry with serverUrl https://connector.get-ryze.ai/mcp in mcp_config.json, then the browser sign-in. In the App, Authenticate and a pasted code | 16 tools: account reports, any GAQL query including change history, Keyword Planner ideas and history, recommendations, changes to campaigns, budgets, bids, keywords, ads and assets, custom audiences and Customer Match, plus a separate delete tool | Free to add. The tools need an active plan or trial: Paid Ads $89 per month with a 7-day free trial, Agency $279 per month |
| Google Ads MCP server (google-ads-mcp), from Google's Ads API team | On your computer as a stdio process started by pipx, or on infrastructure you deploy, such as Cloud Run | On your computer: a command entry in mcp_config.json that runs pipx run --spec google-ads-mcp==0.0.6 google-ads-mcp, with GOOGLE_CLOUD_PROJECT and GOOGLE_APPLICATION_CREDENTIALS under env, after gcloud auth application-default login with the adwords scope. Deployed: allow https://antigravity.google/oauth-callback as a redirect URI on your OAuth client and put the service URL with /mcp in serverUrl. Google lists that client's ID and secret as needed for a deployment, and Antigravity reads them from oauth.clientId and oauth.clientSecret. Needs Python 3.10 or later, pipx, the gcloud tool and a Google Cloud project with the Google Ads API on and Explorer, Basic or Standard access | 7 tools. Three read: accessible customers, GAQL searches built from parameters, and resource metadata. Four make changes, each with a propose-and-confirm step: assets, video uploads (local mode only), labels and label links. Google says it cannot create, modify, pause or enable campaigns, ad groups, ads, budgets or bids, and its tool list has no Keyword Planner or recommendations tool. tools_config.yaml can switch the change tools off | No price on Google's page. Open source under Apache-2.0, version 0.0.6 of November 2, 2026 |
| Google Ads API Developer Assistant 4.0.0 | On your computer, as a plugin inside Antigravity or Claude Code | Clone github.com/googleads/google-ads-api-developer-assistant and run ./install.sh agy (on Windows, .\install.ps1 -Type agy). Needs Git, Python 3.10 or newer, the Antigravity CLI (agy), a Google Cloud project with Explorer, Basic or Standard access, and a Google Ads configuration file such as google-ads.yaml with OAuth 2.0 credentials in your home folder | Builds and checks GAQL, runs read-only API calls and streams reports to the terminal or a CSV file, and writes client library code. Creates, updates and deletes are saved as code under saved/code/ and never run by the assistant. Google calls it an open-source project, not an official Google product | No price on Google's page |
| Composio | Hosted by Composio | Composio lists Antigravity among its clients, though the steps on the pages read here are written for ChatGPT. In Antigravity that comes down to a serverUrl entry for https://connect.composio.dev/mcp followed by Composio's authentication. Google Ads is then authorized on first use through Composio's managed OAuth app, with no Google Ads developer credentials of your own | 78 Google Ads tools that read and write, for example Batch Mutate Google Ads Resources, Create Experiment, Generate Keyword Forecast Metrics and Create customer list | Composio's pricing page: Free with $2 in one-time credits and up to 10,000 tool calls a month, Standard $18 per seat per month, extra calls $0.005 each. Its Google Ads page quotes other free figures |
| Zapier MCP | Hosted by Zapier | Generate an MCP URL in Zapier and choose the Google Ads actions, then add that URL as a serverUrl entry and sign in. Zapier lists Antigravity among its More MCP clients and requires Streamable HTTP, the only remote transport Antigravity accepts | A fixed set of 2 triggers, 10 create or update actions, 4 searches and 1 find-or-create, such as Create Report, Set Campaign Status, Send Offline Conversion and API Request, which sends a raw HTTP request with the integration's sign-in. No action is made for GAQL or for building a campaign | Each successful tool call takes 2 tasks from your Zapier plan; failed calls take none |
Google's guide to its server describes no Google Ads endpoint that Google hosts: the server runs on your machine or on a deployment you manage. For a deployment, Google warns never to leave out the two OAuth variables when using --allow-unauthenticated, since the server would then fall back to Application Default Credentials and expose the container's service account credentials to anyone calling it. Google retired developer tokens on September 9, 2026, and a token sent in a header is now ignored. The Ryze AI connector asks you for no developer token, and google-ads-mcp needs none. Besides Antigravity, Google's guide and README show google-ads-mcp set up in the Gemini command-line tool, Claude, ChatGPT, Claude Code, Codex, Cursor and VS Code.
Options that do not fit Antigravity
- Google Ads API agent skills (google/skills, folder skills/ads). Antigravity is one of four agents Google names, next to Claude Code, Codex and Cursor: turn on the Google Ads API bundle under Build with Google, during onboarding or in Settings > Customizations, or run npx skills add google/skills/skills/ads --agent=antigravity. The three skills hold instructions, best practices and local scripts, one of them for setting up google-ads-mcp. Google describes no account access that belongs to the skills and presents them as a complement to its MCP server.
- Antigravity's MCP Store and Plugin Marketplace. The IDE installs catalog servers from its MCP Store, and the App and CLI from the Plugin Marketplace that opened on October 29, 2026. Google's MCP page lists 77 MCP Store servers, and Ryze AI is not one of them. This guide did not check either catalog for a Google Ads entry.
- Coupler.io. Read-only answers from Google Ads data it syncs on a schedule, so the AI tool never queries Google Ads itself. Its page names Claude, ChatGPT, Gemini, Perplexity, Cursor, Copilot and OpenClaw, and Antigravity is not on that list. For other clients Coupler.io offers a Custom MCP option, a server URL plus an Authorization: Bearer header. An Antigravity entry has a headers field for such a token, but this guide did not check which transport that server uses or try it.
- Windsor.ai. A data connector for 350+ sources that can also pause campaigns and change budgets from ChatGPT and Claude. Its pages name Claude, ChatGPT, Perplexity, Cursor, Gemini and Copilot, without Antigravity.
- cohnen/mcp-google-ads, open source. Five reporting tools behind a Python process. The README has sections for Claude Desktop and Cursor and the repository description adds Windsurf; Antigravity is not among them, and the README still asks for a developer token that Google now ignores.
Which one to pick
Ryze AI is the best way to connect Antigravity to Google Ads when you want reports, keyword research and campaign changes from one hosted address that the IDE, the App and the CLI share, with three caveats: the tools need a Ryze AI plan once the trial ends, the Google sign-in is held by Ryze AI outside any Google Cloud project of yours, and it cannot upload video files or take people off a Customer Match list. Pick google-ads-mcp when nothing may stand between Antigravity and Google and you can look after a Google Cloud project and its credentials; it brings GAQL reports, assets, video uploads and labels, plus a read-only switch. The Developer Assistant suits developers writing Google Ads API code who want read-only checks beside it. Composio has the longest Google Ads tool list, with experiments and keyword forecasts, and Zapier fits a team whose Google Ads tasks already run through Zapier. The connector and google-ads-mcp can share one mcp_config.json under different names.
Sources: Google Ads MCP server guide, googleads/google-ads-mcp, Google Ads API Developer Assistant, Google Ads API agent skills, developer token sunset, Composio Google Ads, Composio pricing, Zapier MCP for Google Ads, Zapier MCP quickstart, Coupler.io, Windsor MCP, cohnen/mcp-google-ads, checked November 14, 2026. Antigravity setup and catalogs from the Antigravity MCP documentation, checked November 15, 2026.
Google Ads, Antigravity and MCP: dates that matter
| Date | Event |
|---|---|
| October 7, 2025 | Google's Ads Developer Blog announced the open-source Google Ads API MCP server. That first release could only read. |
| November 18, 2025 | Google Antigravity shipped as an AI-powered IDE, version 1.11.2. The launch entry does not mention MCP. |
| December 16, 2025 | A Google Cloud blog post explained installing Google Cloud MCP servers from the Antigravity MCP Store. It is the oldest dated Google page on MCP in Antigravity that the research found. |
| May 19, 2026 | Google released the Antigravity App and the Antigravity CLI and began moving Gemini CLI users to the new CLI. |
| June 11, 2026 | Antigravity App 2.1.4 let mcp_config.json take url as well as serverUrl. The IDE got the same change in 2.1.1 on June 22. |
| August 24, 2026 | Google Ads API Developer Assistant 4.0.0 became a plugin and added Claude Code beside Antigravity. |
| September 9, 2026 | Google sunset Google Ads API developer tokens. API access levels now belong to the Google Cloud project, and a token in the header is ignored. |
| October 2, 2026 | Antigravity CLI 1.2.15 fixed sign-in to MCP servers whose client registration answers HTTP 200 instead of 201. |
| October 14, 2026 | Google released Google Ads API v26, its newest major version. |
| October 29, 2026 | The Plugin Marketplace opened in the Antigravity App and CLI. |
| November 2, 2026 | google-ads-mcp 0.0.6 added asset and label tools with a propose-and-confirm flow. It is the first release whose notes add tools that change an account. |
| November 6, 2026 | Antigravity CLI 1.5.2 fixed MCP OAuth sign-ins that failed with Invalid PKCE code_verifier when the server reconnected during the sign-in. |
| November 9, 2026 | Antigravity App 2.30.0 brought the Knowledge Work layout, which hides the MCP Servers list, and an import of MCP servers from Claude Code, Codex and Cursor into a plugin. |
| November 13, 2026 | Google's guide to the Google Ads MCP server shows this date as its last update. The same day, Antigravity CLI 1.5.8 stopped signing users out of OAuth servers without a client secret once an access token expired. |
| February 2027 | Google Ads API v23, the oldest version still served in November 2026, reaches its sunset. |
| May 2027 | Sunset of Google Ads API v24, the version named in the error payloads of the November 13 test calls. |
Sources: Google Ads Developer Blog, October 2025, google-ads-mcp releases, Developer Assistant releases, developer token page, Google Ads API sunset dates and the MCP server guide, checked November 14, 2026; Antigravity changelog, Google Cloud blog, December 2025, Google Developers Blog, May 2026 and Antigravity blog, October 2026, checked November 15, 2026.
How this guide was tested
Three dates stand behind this guide. On November 13, 2026 the connector was checked and nine Google Ads calls went through it from Claude Code. On November 14 the Google Ads sources were read again. On November 15 the connector's sign-in data was compared with the OAuth order in Google's Antigravity docs.
| Check | Result |
|---|---|
| Connector address without a sign-in, November 13 | A request to https://connector.get-ryze.ai/mcp came back as HTTP 401 with a WWW-Authenticate header that points to the sign-in details. |
| The connector's two discovery files, November 13 | Both loaded. They name the authorize, token and register endpoints, the authorization code and refresh token grants, PKCE with S256, and two scopes: mcp:read and mcp:write. |
| Sign-in data against Antigravity's client order, November 15 | A register endpoint is listed, Client ID Metadata Documents are marked unsupported and clients without a secret are accepted. Antigravity's third route, dynamic client registration, is therefore the one that applies. |
| The resource value Antigravity checks, November 15 | The protected resource file for the /mcp path names https://connector.get-ryze.ai/mcp, the match Antigravity requires. The file at the root names the host without /mcp, and Google does not say which of the two Antigravity reads. |
| Tool definitions in a signed-in client, November 13 | 16 Google Ads tools under the names in the tools table: 8 read, 7 write, 1 delete. |
| Account list, November 13 | listAccessibleCustomers worked. The IDs it returned are not recorded. |
| Keyword Planner history, November 13 | Results for all three test keywords with volume, competition, bid range and 12 monthly values. The numbers stay off this page because they came through a real account. |
| Calls built to be refused, November 13 | Seven, each answered by the Google Ads API with a message listed in the errors table below. |
| Quota and rate limits | No answer carried a quota counter or a rate-limit header, and no limit was reached. |
Not run for this guide: anything inside Google Antigravity. The IDE, the App and the CLI were not opened, and no Ryze AI sign-in was completed from them, so the setup, sign-in and approval steps follow Google's Antigravity documentation as read on November 15, 2026. The Google Ads calls came from Claude Code, which talks to the same server. Because the Google Ads account is real, no report that returns account data was run: no account summary, hierarchy, conversion actions, recommendations, keyword ideas or GAQL report with rows. None of the 7 write tools was called and neither was the delete tool, because they change a live account.
Antigravity and Google Ads errors and fixes
Exact messages from the test
The Google Ads API returned these messages word for word in the test on November 13, 2026. Every 400 answer also carried the outer line "Request contains an invalid argument.", so when a call fails in Antigravity, read the inner message.
| Message | What it means | What to do |
|---|---|---|
| Unrecognized field in the query: 'campaign.daily_budget'. | The field does not exist on that resource in the API version in use (UNRECOGNIZED_FIELD). The Ryze AI tool description points to campaign_budget.amount_micros, selected FROM campaign. | Ask the agent to correct the field name and run the query again. |
| Unrecognized field in the query: 'campaign_experiment.name'. | Google reports a resource that does not exist as an unknown field. Experiments live in the experiment resource, as the tool description says. | Have the agent query the experiment resource. |
| Error in query: expected SELECT instead of SELEC. | The GAQL text is malformed (EXPECTED_SELECT). | Ask again; the agent rewrites the query. |
| Change event requests must specify a LIMIT in query and LIMIT should be less than or equal to 10k. | A change history query had no LIMIT (LIMIT_NOT_SPECIFIED). | Add a LIMIT of 10000 or less. |
| Change event requests must specify a LIMIT less than or equal to 10k. | A change history query asked for more than 10,000 rows; the test sent LIMIT 10001 (INVALID_LIMIT_CLAUSE). | Lower the LIMIT, or split the dates and carry on after the last timestamp. |
| No customer found for the provided customer id. | The customer ID does not exist (HTTP 401, CUSTOMER_NOT_FOUND). The outer message speaks of a missing credential, yet the same connection had answered other calls seconds before, so the ID was the cause. | Have the agent run listAccessibleCustomers and use an ID from that list. |
| Resource name '1000' is malformed: expected 'languageConstants/{criterion_id}'. | Keyword Planner wants full resource names for language and location, such as languageConstants/1000 and geoTargetConstants/2840, not bare numbers (RESOURCE_NAME_MALFORMED). | Ask again; the agent resends the full names. |
Other problems
- The server never finishes connecting
- Antigravity waits up to 5 minutes for a server to connect and list its tools. Check that mcp_config.json is valid JSON, that the entry uses serverUrl (or url) and not httpUrl, and reload the configuration.
- Authenticate does nothing in the App
- Complete the Ryze AI sign-in in the browser, copy the authorization code it shows, paste it into Enter authorization code and click Submit.
- The MCP Servers section is missing in the App
- The App is in the Knowledge Work layout, whose Installed tab lists plugins only. Open Settings > General > Interface Layout and pick Software Engineering.
- The Google Ads tools do not appear
- Tool lists can be cached from before you connected Google Ads. Remove the ryze entry, add it again, then start a new chat. Also check that the Google Ads card in Ryze AI shows Connected.
- An account is missing from answers
- Ryze AI only sees accounts the connected login can reach. For a client account under a manager login, connect the manager login and name the account in the prompt.
- Changes are refused
- The connected Google user probably has read-only access. Google Ads permissions are set in Google, not in Ryze AI.
- Recent conversions look low
- Google's own reporting lag applies to recent conversions. Ask again later or compare an older date range.
- Every tool call asks for approval
- That is Antigravity's Ask mode for MCP tools without a rule. Allow chosen tools in the policy configuration, using the mcp(server/tool) form.
- The tools say a subscription is required
- The Google Ads tools need an active Ryze AI plan or free trial. Start the trial, then retry.
Terms on this page
- MCP
- The Model Context Protocol, an open standard through which an assistant such as Antigravity calls tools on outside servers.
- GAQL
- Google Ads Query Language. A query picks fields FROM one resource and returns rows of attributes, segments and metrics.
- Customer ID and login-customer-id
- The customer ID is an account's 10-digit number, written without hyphens in API calls. login-customer-id carries the manager's ID when access to a client account runs through a manager.
- Manager account (MCC)
- A Google Ads account from which you view and run several other accounts, other manager accounts included, in one place.
- Access level
- Two things share the name. In an ad account it is the user's role (Email-only, Billing, Read-only, Standard or Admin), which decides who may edit campaigns. In the API it is the Google Cloud project's tier (Test, Explorer, Basic or Standard), which decides the daily operations.
- Change event
- The API resource behind change history: what changed, the old and new values, the user and the client type, for the past 30 days.
- Ask mode
- Antigravity's default for an MCP tool that has no rule: each call waits until you approve it.
Sources: Google Ads MCP server guide, GAQL overview, call structure, manager accounts, change_event, checked November 14, 2026; Antigravity MCP documentation, checked November 15, 2026.
Frequently asked questions
How do I connect Antigravity to Google Ads?
Connect Google Ads in a Ryze AI workspace: open Integrations, click Connect on Google Ads and approve every permission. Then add a ryze entry with the serverUrl https://connector.get-ryze.ai/mcp to Antigravity's mcp_config.json and complete the Ryze AI sign-in.
Is there a Google Ads MCP server that works in Antigravity?
Yes, several do. The Ryze AI connector at https://connector.get-ryze.ai/mcp is hosted and goes into mcp_config.json as one serverUrl entry. Google's open-source google-ads-mcp runs on your computer or on a deployment you manage, and Composio and Zapier MCP both list Antigravity among their clients.
Which Google Ads MCP connector can I add to Antigravity without running a server?
A hosted one: the Ryze AI connector, Composio or Zapier MCP, which all run on their vendors' servers so Antigravity only stores an address. Google's google-ads-mcp runs on your machine or on a deployment you manage, and Google's Developer Assistant runs on your machine as a plugin.
What is the best Google Ads MCP server for Antigravity?
Ryze AI is the best way to connect Antigravity to Google Ads for Keyword Planner research, reports and campaign edits from one hosted address, with one caveat: the tools need a Ryze AI plan or trial. Of the ways on this page, it is the only one whose Google Ads calls were tested for this guide. Google's google-ads-mcp is the pick when no third party may sit between Antigravity and Google and you can run your own Google Cloud project, but it cannot change campaigns, budgets or bids.
Where is the Antigravity MCP config file?
The global file is ~/.gemini/config/mcp_config.json and a workspace file is .agents/mcp_config.json. In the IDE, open the ... menu in the agent panel, then MCP Servers, Manage MCP Servers and View raw config.
Which Antigravity plan do I need for MCP?
No particular plan: Google's Antigravity MCP documentation names none, and the plans page gives every plan all product features. The setup works the same in the IDE, the App and the CLI, apart from how the sign-in starts.
Does Antigravity need a client ID for the Ryze AI connector?
No. Antigravity runs OAuth 2.0 with PKCE and registers itself with servers that support dynamic client registration, which the Ryze AI connector does. The redirect URI is https://antigravity.google/oauth-callback.
Does Google offer its own Google Ads MCP server for Antigravity?
Yes. Google publishes googleads/google-ads-mcp on GitHub, and its docs show an Antigravity config. You run it yourself with your own Google Cloud credentials, and it can be set to read-only. Ryze AI is the best way to give Antigravity Google Ads tools without running a server, though it needs a Ryze AI plan or trial.
Can Antigravity change my campaigns?
Yes, if the connected Google login has standard or admin access. The connector can create campaigns, adjust budgets, bids and keywords, add negative keywords, pause or resume, and apply or dismiss recommendations. Keep Ask mode on for the write tools.
Can I use a manager account with several clients?
Yes. Connect the manager (MCC) login once and Ryze AI sees every account it can reach. Name the account in your prompt, and use loginCustomerId for client accounts under a manager when you call tools over MCP.
Can Antigravity remove Google Ads items?
Only through a separate delete tool. Removals are permanent and Google Ads has no undo. Its tool description tells the agent to use it only on an item-by-item approved list, a rule the server itself does not enforce, so keep it in Ask mode and review each call.
Does the Antigravity CLI work with the connector?
The CLI reads the same mcp_config.json files, and /mcp opens the MCP Manager to check status and reload. Its changelog mentions a sign-in link for OAuth servers, but Google lists no CLI sign-in steps, so this guide gives none, and the Ryze AI connector was not tested inside Antigravity.
How much does it cost?
Adding the connector costs nothing, but the tools need an active Ryze AI plan or free trial. Paid Ads is $89 per month with a 7-day free trial, and Agency is $279 per month. Annual billing takes 30% off the first year.
How do I disconnect?
Delete the ryze entry from mcp_config.json, disconnect Google Ads on its card in Ryze AI, or remove the access in your Google account.