By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Antigravity to Meta Ads is the Ryze AI connector. Sign in to Meta once in a Ryze AI workspace, add a ryze entry with the serverUrl https://connector.get-ryze.ai/mcp to Antigravity's mcp_config.json, and finish the Ryze AI sign-in. The agent then has 10 Meta Ads tools: 7 that read, 2 that write and 1 that deletes.
- In Ryze AI open Integrations, find Meta Ads under Advertising 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 which campaigns spent the most last week
Antigravity to Meta Ads at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, a hosted MCP server. Antigravity stores one serverUrl entry, and nothing runs on your computer |
| Server address | https://connector.get-ryze.ai/mcp |
| Where the entry goes | mcp_config.json: ~/.gemini/config/mcp_config.json for all projects, or .agents/mcp_config.json in one workspace. The IDE, the App and the CLI read the same format |
| Sign-in | Two steps. You sign in to Meta inside Ryze AI, and Antigravity signs in to the connector with OAuth 2.0 and PKCE. The connector offers dynamic client registration, so you type no client ID or secret |
| Meta Ads tools | 10 in all: 7 read, 2 write and 1 delete, each with an optional connection_id |
| Can it change campaigns | Yes, when the connected Meta login may edit ads. Antigravity runs an MCP tool that has no rule in Ask mode, so each call waits for your approval by default |
| Other data in the same chat | Tools for the other platforms connected to the same Ryze AI workspace, such as Google Ads and Search Console |
| Antigravity plan needed | None is named. Google's MCP page lists no plan, and its plans page gives every plan all product features |
| Ryze AI price | Connecting is free. The tools need an active plan or trial: Paid Ads is $89 per month with a 7-day free trial, Agency $279 per month |
| Meta's own option for Antigravity | Meta's ads MCP server at https://mcp.facebook.com/ads, in open beta since April 29, 2026. Meta's pages give no Antigravity steps, and Meta's written setup for other clients uses your own Meta developer app |
| Last tested | 11 Meta Ads calls sent through the connector from Claude Code on November 14, 2026. Connector 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 names no plan for it, and the FAQ says personal Google accounts can use Antigravity on any plan, the free tier included. Any of the IDE, the App or the CLI works, because all three read one mcp_config.json format. Enterprise accounts cannot sign in to the standalone IDE: they use the App, the CLI or an IDE extension, and an admin may first need to allow MCP servers in Gemini Enterprise.
- A Meta login with access to your ad accounts. Ryze AI asks for at least Advertiser access on the ad account, ideally granted through Meta Business Manager, and Admin access to allow changes. For a hard read-only guarantee, connect a Meta login that only has read access. Meta's table calls that role Analyst.
- 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. Annual billing takes 30% off the first year. Connecting is free, and the Meta Ads tools need an active plan or trial.
How to connect Antigravity to Meta Ads
These steps are for the Antigravity IDE. The first two happen in Ryze AI and Meta, the other four in the editor. The App and the CLI use the same config entry and are covered below.
Connect Meta Ads in Ryze AI
Create a Ryze AI account or sign in, open Integrations in the left sidebar and find Meta Ads under Advertising. Click Connect.
Sign in to Meta and approve every permission
Sign in to Meta and keep every requested permission checked. Back in Ryze AI the card shows Connected. There is no ad account to pick, because Ryze AI sees every ad account that Meta login can reach.
Open the raw MCP config in the Antigravity IDE
At the top of the editor's agent side panel, click the ... menu and choose MCP Servers. Click Manage MCP Servers, then View raw config. The file that opens is mcp_config.json: ~/.gemini/config/mcp_config.json applies to every project and .agents/mcp_config.json to one workspace.
Add the ryze entry
Under mcpServers add an entry named ryze whose serverUrl is https://connector.get-ryze.ai/mcp, then save. No client ID or secret goes in, since Antigravity registers itself with servers that offer dynamic client registration and the Ryze AI connector does.
Sign in to Ryze AI
Antigravity runs the browser sign-in for the server, and Google's MCP page does not describe how it starts in the IDE. When the Ryze AI page opens, pick the workspace that holds your Meta connection and click Allow connection.
Ask your first question
Open a new agent chat and ask: Which Meta campaigns spent the most in the last 7 days, and what was the ROAS of each? Antigravity asks before an MCP tool runs until you allow it, so approve the first call.
The Ryze AI help article for Meta Ads covers the Meta 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 Meta Ads guide.
Antigravity App
The Antigravity App keeps its MCP servers on the Customizations page and has an Authenticate button, so the sign-in differs from the IDE. One catch since App 2.30.0: in the Knowledge Work layout the Installed tab lists plugins only, and the MCP Servers section is missing. Switch to Software Engineering under Settings > General > Interface Layout before step 1. Business and enterprise accounts always use the Software Engineering layout.
- Click Customizations in the sidebar, then Installed, and scroll down to MCP Servers.
- Click Copy Config File Path and add the ryze entry shown below to that mcp_config.json.
- Back under Customizations, Installed, MCP Servers, click Authenticate next to ryze.
- Finish 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 on its own.
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 and has no field for an address, so a custom server such as this one goes into mcp_config.json by hand. Remote servers must use Streamable HTTP. Google's docs rule out the older HTTP+SSE transport and the httpUrl key, and accept url as another name for serverUrl. The redirect URI Antigravity uses for OAuth is https://antigravity.google/oauth-callback.
Antigravity CLI
The Antigravity CLI (agy) reads the same two files. Put the ryze entry in ~/.gemini/config/mcp_config.json or <workspace>/.agents/mcp_config.json, then type /mcp in the prompt panel. The MCP Manager overlay shows the status of each server, reloads the configuration and lists connection logs. Give the global and the workspace entry different names: when both files use one name, the server that is already running keeps it. The older Gemini CLI listed servers in ~/.gemini/settings.json, and Google's migration page asks for serverUrl in place of url or httpUrl.
Google writes the Authenticate steps for the App only. The CLI changelog mentions a sign-in link for OAuth servers (version 1.5.2, November 6, 2026), but no Google page lists the steps, so this guide gives none. The changelog also names mcp add, remove, list, enable and disable subcommands for the user-level file, and their exact syntax is unpublished, so no command line is shown. Access tokens are stored in ~/.gemini/antigravity/mcp_oauth_tokens.json, where expired ones refresh and invalid ones are 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 is documented | The MCP page covers the Antigravity App, the Antigravity CLI and the standalone IDE. The Visual Studio extension page lists the same two mcp_config.json files |
| Config format | One schema everywhere: an mcpServers map keyed by server name. An enabled plugin can add servers through its own <plugin-root>/mcp_config.json |
| Local or remote | command starts a local stdio process. serverUrl (or url) points at a remote server over Streamable HTTP |
| 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 that offer Client ID Metadata Documents or dynamic client registration. Order of tries: oauth.clientId from the file, then a metadata document, then registration. Metadata documents need IDE 2.6.0 or later |
| Approvals | An MCP tool with no rule waits in Ask mode. Rules read mcp(server/tool), mcp(server/*) or mcp(*), and Deny outranks Ask, which outranks Allow |
| Presets that skip the prompt | Turbo in the App on a personal account runs MCP tools without asking. In the CLI the default request-review prompts first, and always-proceed skips the prompt unless 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 and keeps 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 returns up to 10 KB 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. Meta Ads is connected once in Ryze AI, so nothing changes on the Meta side.
Gemini
Google's other assistant has its own steps. See How to connect Gemini to Meta Ads. For the Antigravity client in general, see Ryze AI in Antigravity.
Claude and ChatGPT
Both take the same URL as a custom connector. See How to connect Claude to Meta Ads and How to connect ChatGPT to Meta Ads.
Meta Ads access and permissions
The Meta side of the connection is a Meta sign-in inside Ryze AI. Antigravity adds a second OAuth step for the Ryze AI connector on top. Four things decide what the agent can see and change.
- Meta permissions
- The Ryze AI sign-in requests 11 permissions: ads_management, ads_read, business_management, pages_show_list, pages_read_engagement, pages_manage_ads, leads_retrieval, catalog_management, instagram_basic, instagram_manage_comments and public_profile. Keep every one checked. The list comes from Ryze AI's facts, not from a live consent screen.
- Which ad accounts
- One Meta login reaches every ad account it can access, and Ryze AI sees all of them. Agent default accounts picks the ones the agent works with first, and the others stay reachable when you name them. Several Meta logins can be connected to one workspace, with a star on the primary. Over MCP every meta_ads tool takes an optional connection_id.
- Read or write
- Ryze AI asks for at least Advertiser access on the ad account and Admin access to allow changes. Meta's role table says the Advertiser role can already create and edit ads, and Admin adds the payment method and permission management. Roles are set in Meta, not in Ryze AI.
- How Antigravity signs in
- Antigravity tries a manual oauth.clientId first, then a Client ID Metadata Document if the server supports one, then dynamic client registration. The Ryze AI connector lists dynamic client registration and no metadata document, so the third route applies and you enter nothing.
The 11 Meta permissions 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 Meta login and its permissions stay inside Ryze AI. The Meta sign-in there requests the 11 permissions below, each summed up from Meta's permissions reference.
| Permission requested from Meta | What it allows, in short |
|---|---|
| ads_management | Read and manage the ad accounts the app owns or was granted access to: create campaigns, manage ads, fetch metrics |
| ads_read | Read Ads Insights reports for ad accounts the app owns or was granted access to |
| business_management | Read and write with the Business Manager API, such as managing business assets like an ad account |
| pages_show_list | See the list of Pages a person manages |
| pages_read_engagement | Read content posted by the Page, followers data, the profile picture, and metadata and insights about the Page |
| pages_manage_ads | Manage ads associated with the Page |
| leads_retrieval | Retrieve the information captured by a lead ads form |
| catalog_management | Create, read, update and delete the product catalogs the user administers |
| instagram_basic | Read an Instagram account's profile info and media |
| instagram_manage_comments | Create, delete and hide comments for the Instagram account linked to a Page |
| public_profile | Read the default public profile fields; granted to all apps automatically |
Having a permission does not mean a tool uses it. leads_retrieval covers lead data, yet the connector has no tool that exports leads: meta_ads__listLeadForms lists the forms on a Page and stops there. In the same way the facts list no job for instagram_manage_comments, and catalog work would go through the Graph read and write tools, since there is no catalog tool.
What each Meta ad account role allows
Meta's Business Help Center says ad accounts have 3 permission roles. This is what it lists for each, as read on November 14, 2026.
| Role on the ad account | What Meta says it can do |
|---|---|
| Admin | View ads, access reports, create and edit ads, edit the payment method, manage admin permissions |
| Advertiser | View ads, access reports, create and edit ads. Cannot change the payment method or add or remove other people's access |
| Analyst | View ads and access reports only |
Two Page rules from the same Meta help page. To advertise for a Facebook Page you need full control or partial access (Ads) to that Page, and Instagram ads need a professional Instagram account connected to the Page. For agencies, Ryze AI keeps separate clients in separate workspaces, and one Claude or ChatGPT connection can cover up to 20 workspaces.
What the default connection leaves out: posting organic Facebook Page or Instagram posts (the Ryze AI Meta app holds neither pages_manage_posts nor instagram_content_publish), reading comments on a Facebook Page (no pages_read_user_content), exporting leads, restoring archived or deleted objects, and any ad account the connected login cannot open. Meta's own ads MCP server asks for ads_mcp_management, which is not in the Ryze AI list, because Ryze AI calls the Marketing API directly and does not go through Meta's server.
Sources: Meta permissions reference, Meta ad account roles, Marketing API authorization and the Ryze AI Meta Ads guide. 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 |
|---|---|
| Reconnects | Meta access expires more often than Google's. Ryze AI's help center asks you to reconnect after two-factor changes or Business Manager role changes. |
| Activity log | The ad account activity log, which shows who changed what, is read through the Graph read tool. |
| Archived and deleted items | Restoring an archived or deleted Meta object is not possible from the connector. |
| 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. timeoutSeconds changes both. |
| Tool loading | MCP tools load lazily by default: schemas are cached on disk, and the agent reads one when it needs it. |
| 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 Meta Ads guide and Google's Antigravity MCP documentation, checked November 15, 2026.
Removing access
To remove access, disconnect Meta Ads on its card in Ryze AI, or remove the app from your Meta account's connected apps. 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 (⋮) beside the server also offers Disable and Delete. Stored OAuth tokens live in ~/.gemini/antigravity/mcp_oauth_tokens.json.
What Antigravity can do in Meta Ads
The Ryze AI connector exposes 10 Meta Ads tools: 7 that read, 2 that write and 1 that deletes. All 10 names were loaded from the live connector on November 14, 2026, and each takes an optional connection_id. On the connection used for the test every tool also took a required workspace argument, because that connection covers several workspaces. Your connection may not ask for it.
| Tool (meta_ads__ prefix) | Type | What it does |
|---|---|---|
| listAdAccounts | Read | Lists every Meta ad account the connected user can access, with id, name and currency. |
| getAccountSummary | Read | Returns aggregate metrics for an ad account on Meta's default attribution window. |
| runRawInsights | Read | Runs a raw Insights query at account, campaign, ad set or ad level with breakdowns, filters and custom attribution windows. |
| listCreatives | Read | Lists the ad creatives in an ad account. |
| getCreative | Read | Gets one ad creative by id. |
| listLeadForms | Read | Lists the lead generation forms on a Facebook Page. |
| runGraphRead | Read | Reads any Meta Graph API object or edge, such as paused campaigns, targeting specs or the ad account activity log. |
| runGraphWrite | Write | Creates or updates campaigns, ad sets, ads, creatives and other objects through the Graph API. |
| uploadImageFromUrl | Write | Uploads an image from a URL to an ad account and returns an image hash for a creative. |
| runGraphDelete | Delete | Deletes or archives Meta objects. The tool description says it is meant for an explicit 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 a whole server. You can allow the 7 read tools and leave the 2 write tools and the delete tool in Ask mode, because they change live campaigns and spend. The item-by-item rule on the delete tool lives in its description only, and Antigravity does not enforce it. In the Ryze AI chat, changes follow the chat's Tool approvals setting, which starts on Skip all approvals. For a hard read-only guarantee, connect a Meta login that only has read access.
Meta Ads limits in numbers
Meta counts calls per ad account over one hour, and the allowance depends on the access tier of the Meta app that makes the calls. Ryze AI's facts do not say which tier its Meta app holds, so this guide does not either. Both tiers are listed, and the figures are Meta's.
| Limit | Figure or rule | Who sets it |
|---|---|---|
| Call score | A read costs 1 point and a write 3. Development tier: score maximum 60, decay 300 seconds, blocked 300 seconds at the maximum. Full access: maximum 9,000, decay 300 seconds, blocked 60 seconds. Errors 17 (subcode 2446079) or 613 (subcode 1487742) | Meta |
| Ads management quota | Per ad account per hour: 100,000 on Full access, or 300 plus 40 times the number of active ads on the development tier. Error 80004 | Meta |
| Ads Insights quota | Per ad account per hour: 190,000 on Full access, or 600 plus 400 times the number of active ads on the development tier, less 0.001 times user errors. Error 80000 | Meta |
| Create and edit bursts | 100 requests per second per app and ad account on create and edit calls for campaigns, ad sets and ads. Error 613, subcode 5044001 | Meta |
| Edits to one object | One edit per object every 30 seconds per app by default. Error 613, subcode 4841018 | Meta |
| Ad set budget changes | daily_budget or lifetime_budget can change 4 times per hour, then the change is blocked for an hour. Error 613, subcode 1487632 | Meta |
| Account spending limit changes | 10 per day. Error 17, subcode 1885172 | Meta |
| Insights history | 37 months at most. A time range that starts earlier fails with error 3018 (refused in the November 14 test) | Meta |
| Time slices | time_increment takes 1 to 90 days, monthly or all_days. 91 was refused in the November 14 test | Meta |
| Attribution windows | The default option means 7d_click and 1d_view in the read parameters of Meta's reference. The live API listed 26 accepted values on November 14, and since June 10, 2025 it follows each ad set's attribution setting | Meta |
| Data freshness | Insights refresh every 15 minutes and stop changing 28 days after they are reported. Metrics can keep updating for a couple of days after an ad has finished | Meta |
| Reach with breakdowns | Since June 10, 2025, reach, frequency and cpp are not returned for standard queries with breakdowns and a start date more than 13 months old. Asynchronous jobs can still get them, 10 requests per ad account per day | Meta |
| Report size | No fixed row limit is published. Too much data in one call returns error 100 with subcode 1487534 | Meta |
| Access tiers | A new app starts on Limited access. Full access needs at least 500 Marketing API calls in 15 days and an error rate under 15% in the last 500 calls | Meta |
| API versions | v27.0 is current since November 4, 2026. v24.0 stopped on November 10, 2026, and v25.0 is available until February 23, 2027 | Meta |
| Ryze AI tool inputs | A Graph read takes a path of up to 4,096 characters and a fields list of up to 2,048 (the second was confirmed by a refused call). A Graph write or delete takes a path of up to 512. listCreatives returns 100 by default and 1,000 at most. runRawInsights offers 4 levels and 8 breakdowns | Ryze AI |
| Tool output in the CLI | Up to 10 KB of a lazily loaded tool's result goes straight to the agent | Antigravity |
Sources: Marketing API rate limiting, Graph API rate limiting, Ad account insights reference, Insights best practices, authorization and access tiers and versioning, checked November 14, 2026. Ryze AI tool inputs from the test of November 14, 2026. The CLI figure from the Antigravity changelog, checked November 15, 2026.
Meta Ads calls tested through the connector
On November 14, 2026 the Ryze AI connector took 11 Meta Ads calls from Claude Code, on a live Meta connection. Antigravity was not the client, but it would reach the same server and the same tools. One call was meant to return data, and ten were built to fail: 8 were refused with a message, and 2 came back with ids only. Account IDs and every figure from the account are left off this page.
| Call | Tool | Outcome |
|---|---|---|
| List the ad accounts the login reaches | listAdAccounts | Worked. A list came back, each entry with id, account_id, name and currency |
| Read an ad account's campaigns edge asking for a field that does not exist | runGraphRead | No error. Rows came back holding only an id, with paging cursors, and the unknown field was ignored |
| Read an ad account node asking for a field that does not exist | runGraphRead | No error. Only the id of the node came back |
| Read an object ID that does not exist | runGraphRead | Refused by Meta, code 100, subcode 33 |
| Read an edge that does not exist on an ad account | runGraphRead | Refused by Meta, code 2500 |
| Read with a fields value of 2,100 characters | runGraphRead | Refused by the connector before Meta saw it, invalid_arguments, maximum 2048 |
| Insights with a field that does not exist | runRawInsights | Refused by Meta, code 100 |
| Insights for an ad account ID the login cannot reach | runRawInsights | Refused, status not_allowed with Meta error 200 |
| Insights with the attribution window 99d_click | runRawInsights | Refused by Meta, code 100, with the list of 26 accepted values |
| Insights for a time range starting in January 2020 | runRawInsights | Refused by Meta, code 3018 (37 months) |
| Insights with timeIncrement 91 | runRawInsights | Refused by Meta, code 100 (maximum 90) |
The description of the Ryze AI Graph read tool says one unknown Graph field fails the whole read. In the two calls above that named one, the field was ignored instead, so do not count on an error to catch a misspelled Graph field. The unknown Insights field did fail.
First 3 prompts to run
1. Find where spend is going
Which Meta campaigns spent the most in the last 7 days? Show spend, ROAS and CTR for each, and flag the ones where spend rose while ROAS fell.
Tools used: getAccountSummary, runRawInsights
What comes back: A per-campaign table for the date range from your own ad account. getAccountSummary uses Meta's default attribution window.
2. See who changed an ad account
Read the ad account activity log for the last 14 days. Who changed budgets or campaign status, and when? List the changes in order.
Tools used: runGraphRead
What comes back: A dated list of changes from the activity log. A first page of a Graph read can be shorter than the whole log, so ask for every page.
3. Review creatives
List the ad creatives in this ad account, then open the three newest and summarize their copy and call to action.
Tools used: listCreatives, getCreative
What comes back: A list of creatives, then the detail of the ones you pick. The call returns 100 creatives by default and at most 1,000.
Each answer comes from your own ad accounts, so this page describes what comes back instead of showing sample numbers. Changes to budgets, status and creatives 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 14 test, sent through the connector from Claude Code, only the ad account list returned data, and the Insights job got as far as Meta's own validation of fields, windows and dates. The other rows follow Ryze AI's tool list. A job that changes the account needs a Meta login with a role that may edit ads, and it waits in Ask mode unless you have allowed the tool.
| Job | Ask the agent | Tool | Works on the default connection |
|---|---|---|---|
| Account map | List every Meta ad account my login can reach, with its currency. | listAdAccounts | Yes, with any ad account role. It ran in the test |
| Spend and ROAS | Give spend, ROAS and CTR for this ad account over the last 30 days. | getAccountSummary | Yes, on Meta's default attribution window, which this tool cannot change |
| Breakdowns and windows | Break results down by age, gender and placement at ad set level, using a 7-day click window. | runRawInsights | Yes, from 37 months back at most, in slices of 1 to 90 days, monthly or all days |
| Creative inventory | List the creatives in this ad account. | listCreatives | Yes, 100 per call by default and 1,000 at most |
| One creative | Open the creative with this id and show its copy, image and call to action. | getCreative | Yes, once you have the creative id |
| Lead forms | List the lead forms on this Facebook Page. | listLeadForms | Yes, with a role on the Page. It lists forms and does not export leads |
| Activity log and targeting | Read the activity log, the paused campaigns and the targeting spec of this ad set. | runGraphRead | Yes. Follow paging.next until it is absent |
| Campaign edits | Lower this ad set's daily budget by 10 percent and pause the weakest ad. | runGraphWrite | Yes with a role that may edit ads. Budgets are in minor units, so 5000 means 50.00, and Meta allows 4 budget changes per ad set per hour |
| New creative image | Upload the image at this public URL and give me the image hash. | uploadImageFromUrl | Yes with the same role. A video goes through runGraphWrite with a video URL |
| Archive or delete | Archive these three named ad sets and nothing else. | runGraphDelete | Yes, from a list you approved item by item. Archived and deleted objects cannot be restored |
6 ways to connect Antigravity to Meta Ads
Six ways can give the Antigravity agent your Meta ad accounts. This guide treats the first, the Ryze AI connector, as the main way: Antigravity stores one serverUrl entry, the Meta sign-in happens once inside Ryze AI, and there is no Meta developer app, system user or token to manage. The other five were read on their own pages on November 14, 2026, and none was installed for this guide. Only Composio's page names Antigravity. The setup column shows how each one would go into Antigravity.
| Way | Runs where | Setup in Antigravity | What it reaches in Meta 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 | 10 tools: ad account list and summary, raw Insights with breakdowns and attribution windows, creatives and lead forms, any Graph object, writes to campaigns, ad sets, ads and creatives, image upload, and 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 |
| Meta ads MCP server, from Meta | Hosted by Meta at https://mcp.facebook.com/ads | Meta's pages give no Antigravity steps. Its written setup covers Claude Code and ChatGPT with your own Meta developer app, whose app ID is the OAuth client ID. Antigravity reads oauth.clientId from the entry, and a headers object can carry a bearer token, which Meta accepts as a user access token or an Employee-role system user token. Neither route was tried for this guide | Seven tool categories: reporting, ad creation and management, catalogs, signals and datasets, help and troubleshooting, A/B tests and lift studies, activity logs. Meta ads only. 88 distinct tool names on Meta's category pages when counted on November 14 | No extra cost from Meta to connect, and the AI tool's own terms still apply. Open beta since April 29, 2026, with a phased rollout, so not every ad account has access yet |
| Ads CLI (command meta, package meta-ads), from Meta | On your computer, macOS or Linux. Python 3.12 or later for the pip package | Meta names no AI assistant. The commands run in a shell, for example meta ads campaign list, and the sign-in is a system user access token set as ACCESS_TOKEN with AD_ACCOUNT_ID. How Antigravity would call it was not tried for this guide | Campaigns, ad sets, ads, creatives, insights, catalogs and product sets and feeds, datasets, ad accounts and Pages, plus guidance and ad studies as list commands | No price on Meta's pages. Version 1.3.1 of October 30, 2026 |
| Composio, Metaads toolkit | Hosted by Composio | Composio's toolkit page lists Antigravity among its clients. The setup steps there are written for ChatGPT and Claude Code. Metaads needs your own OAuth app, registered with Meta, whose client ID and secret you add in Composio's dashboard | 99 tools that read and write, for example Create Campaign, Create Ad Set, Create Ad Creative, Create Custom Audience and Delete Campaign | Composio's pricing page: Free with 10,000 app tool calls a month and 3 members, Standard $18 per seat per month, extra calls $0.005 each. Its toolkit page quotes a different free allowance |
| Pipeboard Meta Ads MCP | Hosted at meta-ads.mcp.pipeboard.co, or self-hosted with your own Meta developer app | Antigravity is not named. The README shows Claude and Cursor with a remote URL and a Pipeboard login, and a Pipeboard API token can be appended to the URL | 42 tools in the README's family table and 28 in its numbered list: campaigns, ad sets, ads, creatives, image upload, insights, targeting search and page management. Writes ask for confirmation and new campaigns start paused, per the README | Free: 30 weekly AI tool executions and 2 ad account slots. Pro $29.90 per month, Premium $99, Agency $199. Source-available under the Business Source License 1.1 |
| Windsor.ai, Windsor MCP | Hosted by Windsor.ai | Antigravity is not named. Windsor lists Claude, ChatGPT, Microsoft Copilot, Gemini Enterprise and Perplexity, and a remote MCP server for other clients | Reads 656 metrics and 212 dimensions and offers 20 write actions: create campaigns, ad sets and ads (created paused), pause or enable, set budgets, edit copy and links, upload images and videos, boost a post. It cannot delete, or manage catalogs, custom audiences and pixels | Forever Free: 1 user, 1 data source, data from the past 30 days. Basic $23 per month ($19 billed annually), Standard $118 ($99), Plus $299 ($249), Professional $598 ($499) |
Meta's marketing page describes its standard path as one URL in your AI tool plus a Facebook sign-in, with no developer credentials, API setup or code. It names ChatGPT, Claude and Perplexity as supported AI tools, and Meta's developer overview says the server works with any MCP-compatible AI agent. No Meta page opened on November 14 gives click-by-click steps per assistant for that path without your own app, and the developer page's steps for Claude Code and ChatGPT use one. An unauthenticated request to Meta's server on that day returned HTTP 401 and named 10 scopes. Seven of them are also in the Ryze AI list, and three are not: ads_mcp_management and two branded content scopes. Windsor.ai's page says its connection listed 104 tools in Claude on November 6, 2026. That is Windsor's count, and the number was not confirmed on a Meta page.
Options that do not fit Antigravity
- Zapier MCP. Hosted, and Antigravity would need a Streamable HTTP entry, since that is the only remote transport it accepts. Zapier has no Meta Ads or Facebook Ads MCP page: both addresses returned 404 on November 14. Its three Meta-related app pages offer Send Funnel Event for Facebook Lead Ads, 4 actions for Facebook Custom Audiences and 4 for Facebook Conversions. None of them reads campaign results or edits a campaign. Each successful call uses 2 tasks from your Zapier plan.
- Coupler.io. Read-only for the AI tool, answering from data synced on a schedule, so the tool never queries Meta itself. Its page says the AI tool cannot create campaigns, change a daily budget or delete campaigns. It names Claude, ChatGPT, Gemini, Perplexity, Cursor, Copilot and OpenClaw, and Antigravity is not among them. Its Custom MCP option takes a server URL and an Authorization bearer header. An Antigravity entry has a headers field for that, but this guide did not try it.
- Supermetrics MCP. Hosted, with OAuth 2.0 and a 14-day free trial that needs no credit card. A Supermetrics help article updated on November 12, 2026 says campaigns can be created and updated on Facebook Ads from an AI tool, that every proposed change is shown before it is applied and that new campaigns are created paused. The page names Claude, ChatGPT, Copilot and n8n, and its FAQ adds other clients. Antigravity is not named.
- Meta AI business assistant. Meta's own assistant inside Ads Manager. It is not a route for an outside assistant. Meta says it works in Ads Manager, while the connectors bring Meta ads into the AI tools you use elsewhere.
- 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 among them. The full Marketplace catalog was not checked for a Meta Ads entry.
- Open-source servers on GitHub. A repository search for meta ads mcp on November 14 returned 432 results. The top of the list by stars was mathiaschu/meta-ads-analyzer at 470 stars, then amekala/ads-mcp at 107 and mikusnuz/meta-ads-mcp at 95, which describes 135 tools on Marketing API v25.0. Their READMEs were not opened, so nothing is claimed about their setup, safety or Antigravity support.
Which one to pick
Ryze AI is the best way to connect Antigravity to Meta Ads when you want reports, creative reviews 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 Meta sign-in is held by Ryze AI instead of a Meta developer app of yours, and it cannot post organic Page or Instagram content or restore archived objects. Pick Meta's own ads MCP server when you want Meta as the only party between Antigravity and your ads, your ad account has access in the phased rollout, and you can work out the Antigravity sign-in yourself, since Meta documents no Antigravity steps. Pick the Ads CLI for scripts that run on a machine you control. Composio lists 99 tools and names Antigravity, and Windsor.ai lists 656 metrics and 212 dimensions for reporting. The connector and Meta's server can sit in one mcp_config.json under different names.
Sources: Meta ads MCP server page, Meta ads AI connectors announcement, Meta ads MCP server, get started, Ads CLI, get started, meta-ads on PyPI, Composio Metaads, Composio pricing, Pipeboard Meta Ads MCP, Pipeboard pricing, Windsor.ai, Windsor.ai pricing, Zapier MCP quickstart, Zapier Facebook Custom Audiences, Coupler.io, Supermetrics MCP and a GitHub search, checked November 14, 2026. Antigravity setup and catalogs from the Antigravity MCP documentation, checked November 15, 2026.
Meta Ads, Antigravity and MCP: dates that matter
| Date | Event |
|---|---|
| June 10, 2025 | Meta changed the Insights API: reach with breakdowns stopped coming back for start dates more than 13 months old, and the API began following each ad set's attribution setting, as Ads Manager does. |
| November 18, 2025 | Google Antigravity shipped as an AI-powered IDE, version 1.11.2. The launch entry does not mention MCP. |
| April 29, 2026 | Meta announced its Meta ads AI connectors in open beta, made of an ads MCP server and the Ads CLI. meta-ads 1.0.0 and 1.0.1 reached PyPI the same day. |
| May 4, 2026 | Meta renamed Ads Management Standard Access to Marketing API Access Tier, with Limited access and Full access, and lowered the Full access threshold from 1,500 to 500 calls in 15 days. |
| May 19, 2026 | Google released the Antigravity App and the Antigravity CLI and began moving Gemini CLI users to the new CLI. On the same day Meta stopped allowing the creation, duplication and update of Advantage+ shopping and app campaigns through the API, on every version. |
| 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. |
| July 16, 2026 | Meta's ads MCP server update let any AI application connect with your own developer app, and added ads MCP server rules for people with full control of a business portfolio. |
| July 29, 2026 | Marketing API v26.0 was released. |
| October 2, 2026 | Antigravity CLI 1.2.15 fixed sign-in to MCP servers whose client registration answers HTTP 200 instead of 201. |
| October 27, 2026 | Three Marketing API v26.0 changes took effect for all versions: poll ads are gone, applink_treatment=web_only is deprecated for Web and App campaigns, and housing, employment and financial campaigns with constrained targeting must set the advantage_audience flag explicitly. |
| October 29, 2026 | The Plugin Marketplace opened in the Antigravity App and CLI. |
| November 4, 2026 | Marketing API v27.0 was released and is the current version. |
| 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 10, 2026 | Marketing API v24.0 stopped being available. |
| November 13, 2026 | Antigravity CLI 1.5.8 stopped signing users out of OAuth servers without a client secret once an access token expired. |
| February 23, 2027 | Marketing API v25.0 is available until this date. |
Sources: Meta ads AI connectors announcement, Meta for Developers blog, July 2026, Marketing API changelog, Marketing API versions, Insights best practices and meta-ads on PyPI, checked November 14, 2026; Antigravity changelog, Google Developers Blog, May 2026 and Antigravity blog, October 2026, checked November 15, 2026.
How this guide was tested
Two dates stand behind this guide. On November 14, 2026 the Meta Ads sources were read and 11 Meta Ads calls went through the connector from Claude Code. 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 15 | A POST to https://connector.get-ryze.ai/mcp returned HTTP 401 with a WWW-Authenticate: Bearer header that points to the protected resource file. |
| The connector's two discovery files, November 15 | Both loaded. They list one authorization server and two scopes, mcp:read and mcp:write. |
| Sign-in data against Antigravity's client order, November 15 | A registration endpoint is present, Client ID Metadata Documents are marked unsupported, PKCE with S256 is offered and the token endpoint accepts clients without a secret. 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, which matches the server address as 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 14 | 10 Meta Ads tools under the names in the tools table: 7 read, 2 write, 1 delete. |
| Ad account list, November 14 | listAdAccounts worked. The names and IDs it returned are not recorded. |
| Calls built to fail, November 14 | Ten. Eight were refused with a message listed in the errors table below, and two returned only ids. |
| Meta's own server, November 14 | An unauthenticated request to https://mcp.facebook.com/ads returned HTTP 401 and named 10 scopes. Its two OAuth discovery files loaded. No signed-in call was made. |
| Quota and rate limits | No answer carried a rate-limit header or a usage percentage, 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 Meta Ads calls came from Claude Code, which talks to the same server. Because the ad accounts are real, getAccountSummary, listCreatives, getCreative and listLeadForms were not called and no Insights call that returns metrics was run. The write, upload and delete tools were not called either, because they change a live ad account. No call was made to Meta's own ads MCP server or the Ads CLI with a sign-in.
Antigravity and Meta Ads errors and fixes
Exact messages from the test
The messages below came back in the test on November 14, 2026, word for word except that IDs are removed. Meta's errors reach the agent with the Meta code, so when a call fails in Antigravity, read the code first.
| Message | What it means | What to do |
|---|---|---|
| Unsupported get request. Object with ID '<redacted>' does not exist, cannot be loaded due to missing permissions, or does not support this operation. | Code 100, subcode 33. The ID is wrong, or the connected Meta login has no access to that object. Meta gives one message for both. | Have the agent list ad accounts or campaigns first and use an ID from the list. If the object exists, check the login's access in Meta Business Manager. |
| (#100) not_a_field_xyz is not valid for fields param. | The Insights API does not know that field. The tool description gives common cases: roas is purchase_roas, and status, placement and creative are not Insights fields. | Ask again with a valid Insights field, or have the agent read object attributes with runGraphRead. |
| Meta Graph error (code 200): (#200) Ad account owner has NOT grant ads_management or ads_read permission | The connector returned status not_allowed. The login cannot reach that ad account, or the ID is wrong. | Use an ID from listAdAccounts, give the login access in Meta Business Manager, or connect another Meta login in Ryze AI. |
| (#100) action_attribution_windows[0] must be one of the following values: 1d_view, 7d_view, 28d_view, 1d_click, 7d_click, 28d_click, ... | The window name is not one Meta accepts. The full message lists 26 values. | Pick a window from the list. The tool description names 1d_click, 7d_click, 28d_click and 1d_view as the ones to use. |
| (#3018) The start date of the time range cannot be beyond 37 months from the current date. | Meta keeps 37 months of Insights data. The message gives the earliest start date for the account. | Start the report inside the last 37 months. |
| (#100) Param name_placeholder must be a number less than or equal to 90 | A time slice in days can be 1 to 90. Meta prints name_placeholder where the parameter name time_increment belongs. | Use a number from 1 to 90, or monthly, or all_days. |
| Unknown path components: /not_an_edge_xyz | Code 2500. The path names an edge that does not exist on that object. | Use a real edge such as campaigns, adsets, ads, adcreatives, customaudiences or activities. |
| Too big: expected string to have <=2048 characters | status invalid_arguments from the Ryze AI connector, so the call never reached Meta. The fields list of one Graph read may hold 2,048 characters at most. | Ask for fewer fields per call, or split the read. |
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, that the entry uses serverUrl (or url) and not httpUrl, and reload the configuration.
- Authenticate does nothing in the App
- Finish 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 Meta Ads tools do not appear
- Tool lists can be cached from before Meta was connected. Remove the ryze entry, add it again and start a new chat. Also check that the Meta Ads card in Ryze AI shows Connected.
- Meta asks you to reconnect
- Meta access expires more often than Google's. Ryze AI's help center says to reconnect after a two-factor change or a Business Manager role change.
- An ad account is missing from answers
- Ryze AI sees only the ad accounts the connected login can reach. Give the login access in Meta Business Manager, or connect a second Meta login under View, Add one more account.
- Changes are refused
- The connected Meta login probably lacks a role that may edit ads. Roles are set in Meta, not in Ryze AI.
- A creative write is slow or refused
- Meta's default is one edit per object every 30 seconds per app, error 613 with subcode 4841018. An ad set budget can change 4 times per hour. Wait, then retry.
- 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 Meta 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.
- Ad account
- The container Meta bills and reports on. Campaigns, creatives and access roles hang off it, and its ID is written act_ followed by a number.
- Campaign, ad set and ad
- Meta's three levels. The campaign holds the objective, the ad set holds budget, schedule, bidding and audience, and the ad holds the creative.
- Attribution window
- How long after a click or a view a conversion still counts for an ad, for example 7 days after a click and 1 day after a view.
- Insights API
- The reporting part of Meta's Marketing API. It needs ads_read and works at the account, campaign, ad set and ad level.
- Business Use Case rate limit
- Meta's hourly call quota for the Marketing API, counted per ad account and per kind of work: ads management, ads insights, custom audiences and catalogs.
- Ask mode
- Antigravity's default for an MCP tool that has no rule: each call waits until you approve it.
Sources: Ad account reference, Marketing API overview, Insights API, Graph API rate limiting, checked November 14, 2026; Antigravity MCP documentation, checked November 15, 2026.
Frequently asked questions
How do I connect Antigravity to Meta Ads?
Connect Meta Ads in a Ryze AI workspace: open Integrations, click Connect on Meta 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 finish the Ryze AI sign-in.
Is there a Meta Ads MCP server that works in Antigravity?
Yes, more than one. The Ryze AI connector at https://connector.get-ryze.ai/mcp is hosted and goes into mcp_config.json as one serverUrl entry. Meta also hosts an ads MCP server at https://mcp.facebook.com/ads, in open beta, though its pages give no Antigravity steps. Composio lists Antigravity among its clients.
What is the Meta Ads connector for Antigravity?
The Ryze AI connector is the one this guide tested. It is a hosted MCP server with 10 Meta Ads tools, and Antigravity reaches it through a single serverUrl entry. Meta's own connector is its ads MCP server, announced on April 29, 2026, which Meta calls part of its Meta ads AI connectors.
Can I connect Antigravity to Meta Ads without running a server?
Yes. The Ryze AI connector, Meta's ads MCP server, Composio, Pipeboard and Windsor.ai all run on their vendors' servers, so Antigravity only stores an address. Meta's Ads CLI runs on your computer, and self-hosted open-source servers run wherever you put them.
Which Meta Ads MCP server should I pick for Antigravity?
It depends on who you want between Antigravity and your ads. The compare section lays out six ways side by side. Of them, only the Ryze AI connector had its Meta calls tested for this guide, and it needs a Ryze AI plan or trial. Meta's server needs no Ryze AI plan, is still in a phased rollout and documents no Antigravity steps.
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 Meta offer its own MCP server for Antigravity?
Meta hosts an ads MCP server at https://mcp.facebook.com/ads and says it works with any MCP-compatible AI agent, but Meta names ChatGPT, Claude and Perplexity, and its written steps cover Claude Code and ChatGPT with your own Meta developer app. It is in open beta with a phased rollout, so not every ad account has access yet.
Can Antigravity change my Meta campaigns?
Yes, if the connected Meta login may edit ads. Through the connector it can create campaigns, ad sets, ads and creatives, adjust budgets, pause or resume, and swap creatives. Keep Ask mode on for the write and delete tools.
Can I use several ad accounts or clients?
Yes. One Meta login reaches every ad account it can access, and Agent default accounts sets which ones the agent uses first. You can connect more Meta logins to a workspace. Separate clients belong in separate workspaces.
Can Antigravity delete or restore Meta campaigns?
It can archive or delete through a separate delete tool, and it cannot restore anything afterwards. The tool description says to use it only on an item-by-item approved list, a rule Antigravity does not enforce, so keep it in Ask mode and review each call.
Can Antigravity post to my Facebook Page or Instagram?
No. The Ryze AI Meta app holds neither pages_manage_posts nor instagram_content_publish, so organic Page and Instagram posts are out. It also cannot read comments on a Facebook Page or export leads from a lead form.
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. Ryze AI was not tested inside Antigravity.
How much does it cost?
Connecting is free, 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 Meta Ads on its card in Ryze AI, or remove the app in your Meta account.