Meta Ads MCP Server: Connect Claude or ChatGPT, What It Can Change, and the Rules to Set First
Meta runs an official ads MCP server at https://mcp.facebook.com/ads. Add it to Claude as a custom connector, sign in with Facebook, pick your business portfolio, and the assistant can pull campaign reports, spot anomalies and check pixel health. With the right permissions it can also create campaigns, edit budgets, change audiences and switch ads on. An advertiser doesn't need a Meta developer app for any of this. If anyone on the team will use it for more than reporting, set the ads MCP server rules in Meta Business Suite before the first prompt.
Everything below comes from Meta's ads MCP server documentation, its Business Help Center article and the July 16 developer announcement, read on November 16, 2026.
What Meta shipped and when
Meta announced "Meta ads AI connectors" in open beta on April 29, 2026. The family has two parts: the ads MCP server, which any MCP client can call, and an ads command line interface. On July 16 Meta added two things: developers can now connect through their own Meta app, and advertisers got rules that limit what an agent may do on an ad account or catalog.
Two caveats from Meta itself. The help article opens with "You may not have access to all of these tools and features yet", and the developer post says tools are rolling out gradually. Jon Loomer, who set it up in Claude in the first weeks, saw 29 tools at the time. Your list may be longer or shorter, so ask the assistant which tools it has before you plan around one.
The open-source "Meta Ads MCP" projects you'll find on GitHub and Reddit are community builds. Meta's server is remote-hosted, so there's nothing to install.
Connect it to Claude
This route needs no developer app. Meta's announcement puts it as "For MCP, no developer credentials, API setup, or coding required."
- In Claude, open Customize, then Connectors.
- Click "+", choose "Add custom connector", give it a name and paste
https://mcp.facebook.com/ads. Click Add. - Click Connect. Facebook Login opens and asks which business portfolios Claude may use.
- In a new chat, open "+" > Connectors and check that the Meta connector is switched on.
Anthropic offers custom connectors on every Claude plan, but free accounts can have only one. On Team and Enterprise plans an Owner adds the connector for the organization first, and each member then signs in with their own Facebook account, so Claude sees only the ad accounts that person can already reach.
Loomer's walkthrough also lists ChatGPT and Perplexity as supported clients at launch.
Connect it with your own Meta app (Claude Code, ChatGPT, scripts)
Teams building their own tooling can go through a Meta developer app. In the app dashboard, add the use case "Create & manage ads with ads MCP server". Agencies, and anyone else managing ad accounts owned by other businesses, also have to pass app review to get Advanced Access on the ads_mcp_management permission.
For Claude Code, Meta gives one command:
claude mcp add --transport http --client-id <META_APP_ID> meta-ads https://mcp.facebook.com/ads
For ChatGPT, set your app's redirect URL to ChatGPT's specification, create the connector with OAuth as the authentication method, use the same server URL, and enter your Meta app ID as the OAuth Client ID under Advanced OAuth Settings.
Scripts can skip OAuth and pass a token in an Authorization: Bearer header. Meta accepts user tokens and system user tokens, with one catch: the system user must have the Employee role, because Admin-role system user tokens can't reach the server.
Which tools appear depends on the token's permissions. At minimum it needs ads_mcp_management plus either ads_read or ads_management, and Meta says adding ads_management, catalog_management, business_management, pages_show_list or instagram_basic unlocks more tools. For a reporting connection, request ads_read without ads_management. Then run tools/list and confirm what actually came back.
What the tools can read and change
Meta groups the tools into seven areas: reporting, ad creation and management, catalogs, signals and datasets, help and troubleshooting, A/B tests and lift studies, and activity logs. The tool pages list each one.
Start with the read tools:
ads_get_ad_entitiespulls campaigns, ad sets and ads with spend, impressions, CTR, CPC, CPM and conversions, with filters, breakdowns and date ranges.ads_insights_performance_trend,ads_insights_anomaly_signal,ads_insights_industry_benchmarkandads_insights_auction_ranking_benchmarkscover trends, unusual movements, peer benchmarks and auction results.ads_get_errorsreturns delivery-blocking errors, andads_account_get_activity_logsmirrors the Ads Manager change history.ads_get_dataset_qualityreports Event Match Quality scores and match-key coverage for your pixel and Conversions API events.ads_library_searchsearches the public Ad Library, which is handy for a quick look at competitors' creative.
The write tools reach campaigns, budgets, audiences, catalogs and pixels:
ads_create_campaign,ads_create_ad_setandads_create_adcreate new entities in a paused state.ads_activate_entityswitches a paused campaign, ad set or ad to active. Meta's own description adds "starts spending budget".ads_update_entityupdates fields on an existing campaign, ad set or ad.ads_create_custom_audience,ads_update_custom_audience_users(uploads hashed personal data) andads_delete_custom_audience.- Catalog tools that create, update and delete products, product sets and feeds. Deleting a feed also removes the products it ingested.
- Pixel event and parameter tools that create, update and delete event rules.
Meta says write tools create entities paused and that "your AI client asks for confirmation before activation". The help article adds a draft mode that "saves new campaign work for review before publishing and avoids automatically pausing running campaigns when you make changes". A confirmation prompt still lets the change through once someone clicks Allow, though, and that is where the rules come in.
Set the rules before anyone writes
Ads MCP server rules deny specific agent actions on a specific ad account or catalog, and Meta's server enforces them. You need full control of the business portfolio to set them.
- Open Settings in Meta Business Suite.
- Under Integrations, select Ads MCP server. If it isn't there, your business doesn't have the feature yet, since rules are in limited availability.
- Pick the ad account or catalog and switch actions between Allowed and Blocked.
The actions you can block, from Meta's rules reference:
| Rule | What it blocks | When a Shopify brand might use it |
|---|---|---|
| All actions on the account | Every agent action | A reporting-only setup while the team learns the tool |
| Create campaigns, ad sets or ads | New entities | When agents should only work on what already exists |
| Edit budget, percentage change | Increases above a set percentage | Keeping daily changes inside your normal scaling steps |
| Edit budget, absolute change or ceiling | Increases above an amount, or budgets above a ceiling | A hard cap, such as no budget over $1,000 |
| Edit targeting | Targeting and audience changes | Protecting tested audiences and exclusions |
| Edit creative | Creative changes | When creative goes through brand review |
| Edit status | Pausing or activating delivery | Stopping an agent from switching ads on |
| Catalog product edits while active in ads | Product and product set changes while the catalog runs ads | Protecting a live Advantage+ catalog |
Budget rules can apply to daily budgets, lifetime budgets or both. Meta's help article gives the cap example directly: set "Budgets set above this amount" to Blocked with USD 1,000, and any request to set a budget above $1,000 is denied.
A starting configuration for a small brand team: block all actions on the account for the first two weeks while people learn what the reports look like. Then allow creation, keep "edit status" blocked so new work stays paused until someone turns it on in Ads Manager, and add a percentage cap on budget increases at the size of your usual scaling step. Meta's developer post describes the same progression: start "in a read-only or approval-required posture" and widen access "as confidence grows".
If an agency runs your ads, it can set its own rules on the ad account you shared, and those rules apply only to people in the agency's business. Agencies scripting this across many clients should know Meta's rules API has no batch endpoint, so it takes one call per rule per account.
Will connecting it get the ad account banned?
Meta answers this in the help article: "It's safe to connect your ad account through Meta's ads MCP server, and it's unlikely that an account would be banned simply for using it." Bans follow policy violations, such as non-compliant ad content or creating new accounts to evade enforcement. An agent that writes non-compliant ad copy is still your ad account writing it, so creative review stays with a person.
Prompts that work for a Shopify brand
Try these with all actions blocked first:
- "Which ad account is this? List its currency and timezone." Ask this first in every new chat. An assistant connected to the wrong portfolio still answers fluently.
- "Show spend, purchases, cost per purchase and purchase ROAS by campaign for the last 14 days, compared with the 14 days before. Flag anything that moved more than 25%."
- "Run the anomaly check on this account for the last 7 days, then pull the activity log for the same window. Did anyone change a budget, audience or creative right before each anomaly?"
- "What's the Event Match Quality for our purchase event, and which match keys have low coverage?"
- "List delivery-blocking errors across all active campaigns."
The anomaly check plus the activity log tells you who changed what right before results moved, without scrolling the Ads Manager change history by hand. Our creative fatigue guide has the signals worth asking about, and scaling Meta without killing MER gives sensible step sizes for that budget cap.
Where Meta's numbers stop
Everything the server returns is Meta's view: Meta-attributed purchases and ROAS under the account's attribution setting. It won't match Shopify orders, and it knows nothing about refunds, margin, repeat purchases or what Google and email drove in the same week. Ask the assistant to "scale campaigns with ROAS above 3" and it will act on Meta's ROAS, which may be counting orders Shopify credits elsewhere. Our guide to reconciling Meta revenue with Shopify explains why the numbers drift and how finance teams settle them.
Triple Whale's CEO is quoted in Meta's announcement saying the company connected the server to Moby, its own agent, so analytics tools are starting to sit on top of it too.
Finsi reads Meta alongside Shopify, Google Ads, Klaviyo and subscription data under one set of definitions. Finsi MCP gives Claude or ChatGPT those reconciled numbers, read-only and logged. On the action side, the PULSE agent proposes Meta and Google Ads budget and campaign changes with its reasoning, and a person approves each one. Finsi doesn't change ad spend unattended. See how Finsi's agents work and our post on approval-gated agents. If you're wiring up the rest of the stack, our guides to the Google Ads MCP server, Klaviyo MCP and Google Analytics MCP cover the same ground for search ads, email and GA4.
Sources
- Meta for Developers, Ads MCP server overview, Get started, Rules best practices and the tool pages for ad creation and management and catalogs
- Meta for Developers blog, Meta's ads MCP server is now available for developers (July 16, 2026, updated September 22, 2026)
- Meta Business Help Center, Manage ads from an AI agent with Meta ads AI connectors
- Meta for Business, Introducing Meta Ads AI Connectors (April 29, 2026)
- Anthropic, Get started with custom connectors using remote MCP
- Jon Loomer, Meta Ads AI Connectors and Claude: Setup, Uses, and Risks