Meta's ads MCP server is a connector that lets Claude or ChatGPT read and change your Meta ad accounts. You ask in plain words, and it pulls the numbers, or builds and edits campaigns, ad sets and ads. It can also set a paused ad live, which Meta says starts spending budget.
MCP is a way of connecting AI assistants to other tools, and this is Meta's own server for it. Google says its server for Google Ads only reads, so on Meta the safety part comes first. I've managed €5M+ of ad spend over 10+ years, and when I take over an account, I look at everything before I touch anything.
In short:
- It reads your ad account, and it can also create, edit and set ads live.
- The campaigns, ad sets and ads it creates start paused. By default, the only check before one goes live is the question your AI app asks, so never click "Allow always".
- Before the first prompt, set Meta's agent rules, an account spending limit and a login that isn't an admin.
- All it takes is one address and a Facebook sign-in, with no developer app. The steps are at the end.
It reads your ad accounts, and it can change them too. It can build campaigns, edit them and set them live.
What it reads:
- campaigns, ad sets and ads, with spend, impressions, conversions and more, for the dates and breakdowns you choose
- the opportunity score and Meta's recommendations
- delivery errors and the account's activity history
- your pixel's data quality, and the public Ad Library
What it changes:
- campaigns, ad sets and ads: it creates them paused, edits them and sets them live
- ads with a single image, a video or a carousel, and boosts of your Instagram posts
- custom audiences, including the people on a customer list, and deleting them
- pixel event rules, catalogs, A/B tests and lift studies
Meta rolls these out account by account, so you may not have all of them yet. That's why my prompt below first asks what your connection can change.
You ask the way you'd ask a colleague. For example, "Which ad sets spent the most last week, and which are still learning?"
The reports alone are worth a lot. On Meta it can also make the fix, and in the setup we build for clients it does that once you say yes.
A prompt for your first report, to paste into Claude or ChatGPT
This is the first report I'd ask for on a new Meta account. It covers what the connection can change, then the money, then up to three changes to approve. Fill in the account and your target, and paste it as it is. Below it is Claude's answer on a sample store's account data. Then comes the answer, and the change Claude made and checked.
What it can't do, and what to watch
Meta lists no billing tool, and Ads Manager has no undo. Here's what that means, and what else I watch:
- No billing. Meta's tool list has no tool for payment methods, billing or the account spending limit. That's why the spending limit works so well as a safety net.
- No undo in Ads Manager. Once you edit a published campaign, Meta says "There's no option to reverse changes". So before every change, Claude writes down what was there.
- Edits to live ads have a cost. Meta says a new ad, or a change to targeting, creative or the optimization event, sends the ad to review and restarts learning. A big budget change can restart learning too. An ad set usually leaves learning after about 50 results in the week after its last significant edit. So wait 7 to 10 days after that before the next structural edit.
- A live ad keeps what it shows. It can upload images and videos from a public link, and delete a published campaign, ad set or ad. But it can't change the image or text of a live ad. It makes a new ad and pauses the old one. And no tool throws away a draft, so a draft it made by mistake waits for you in Ads Manager.
- No view of URL parameters. It can't show you the URL parameters on your ads. It can add them to a new ad, but only from a template you give it. So copy yours from Ads Manager (open an ad, then Tracking, then URL parameters) and check them on every new ad.
- Only Meta's side. It has no tool for your store, CRM or GA4, so it can't tell you if a purchase really happened.
How to keep its changes safe
Nothing should change until you say yes. Your AI app is the one that asks. In a Claude chat you approve each tool before it runs, but in Research it doesn't ask, so switch off the tools that make changes first. ChatGPT asks before every change by default. Never click "Allow always" in Claude, and never let ChatGPT remember your yes for the conversation. By default, that question is the only check before an ad goes live.
Meta also warns that an agent can do anything the access you grant allows, even when an instruction hidden in something it reads tells it to. So set three things on Meta's side before the first prompt. The rules and the spending limit back each other up, and the login is one more step on top.
- Meta's agent rules. You need full control of the business portfolio. In Meta Business Suite, go to Settings, and under Integrations select Ads MCP server. Pick the ad account, then switch "Budgets set above this amount" to Blocked, and enter the highest budget you'd approve. You can also block Create campaigns there, and delivery status changes if you'd rather set ads live yourself. If you don't see Ads MCP server, your business doesn't have access to the rules yet.
- An account spending limit. In Ads Manager, go to your Payment settings. In the Account spending limit section, click Options, then Set limit. Enter the amount, click Save, then Done. Once the account reaches it, your ads pause. Meta says only an admin can change it, and an account paid with available funds can't have one.
- A login that isn't an admin. Use someone with the Advertiser role, or in a business portfolio, partial access to manage campaigns. They can create and edit ads, but not change the payment method or who has access. Meta doesn't say the connector sticks to your role, so see it as an extra.
In the setup we build for clients, Claude shows you each change as it is now and as it will be, and makes it only after your yes. A new ad goes in as a draft, and it goes live only on a second yes, because that's the step that spends money. Then Claude reads the change back from the account and logs what was there before.
Within a day it checks that the ads it touched are running. If an ad gets rejected, it stops and tells you instead of trying again on its own.
How to connect it to Claude or ChatGPT
Meta hosts the server, so there's nothing to install. You add this address to your AI app and sign in with Facebook, and you don't need a Meta developer app.
https://mcp.facebook.com/ads
In Claude
- Go to Customize, then Connectors. Click "+ Add", then "Add custom connector".
- Name it Meta Ads, paste the address above as the server URL, and click Continue.
- Under Authentication, choose "Sign in now", leave the OAuth client as Claude detected it, and click Add.
- Sign in with the Facebook account that has access to your ad accounts. Meta asks which business portfolios it can reach, so pick the ones that hold your clients' accounts, and confirm. If Facebook doesn't open, find Meta Ads under Customize, then Connectors, and click Connect.
- In a chat, click the "+" button at the bottom left, choose Connectors and switch Meta Ads on.
Anthropic says you can only add one custom connector on the Free plan. On a Team or Enterprise plan, an owner adds it first under Organization settings, then Connectors, then Add, Custom and Web, and then each of you clicks Connect on it.
In ChatGPT
- On the web, go to ChatGPT Plugins. Select the plus button, then "Add custom MCP server".
- Name it Meta Ads. Under Connection, paste the address above as the Server URL.
- Choose OAuth as the way to sign in.
- Read the risk warning, select "I understand and want to continue", then "Create as a plugin".
- Install the plugin, and sign in with Facebook when it asks.
- In a chat, type @ and pick Meta Ads.
If you don't see Add custom MCP server, your plan or your workspace's settings don't allow it.
In Claude Code
Run this once in your terminal:
claude mcp add --transport http meta-ads https://mcp.facebook.com/ads
Then start Claude Code, type /mcp, pick meta-ads and sign in with Facebook in your browser. If you go through your own Meta developer app, Meta's docs add its ID:
claude mcp add --transport http --client-id <META_APP_ID> meta-ads https://mcp.facebook.com/ads
Then set its access, and test it
Once you've signed in, go to Settings on Facebook, then Business Integrations. Your AI app is listed there with its access, Read or Manage. Set it to Manage if you want it to make changes after your yes, or Read if you only want reports. That's also where you remove it.
To test it, ask "Which Meta Ads tools do you have?" and you should see the list. Then ask for last week's amount spent in one ad account. If it matches Ads Manager, it works.
To reach a client's account, the client shares its ad account, Page, Instagram account and dataset with your business portfolio as a partner. Meta also switches its server on account by account. If Claude says an account isn't enabled for it, you can't switch that on yourself, so that account waits for Meta.
One more thing before you connect client accounts. We only put client data through business plans, such as Claude Team or Enterprise, or ChatGPT Business.
Meta opened its ad accounts to outside AI, changes included. Meta's developer post says to start "in a read-only or approval-required posture" and widen "as confidence grows", and I think that's right. That's how we set it up for clients. Claude does the reading and prepares the changes, and nothing goes in until someone says yes. The next step is how agencies run checks like this every morning.