Connect Claude to Meta Ads: the setup, and what it can actually do
Setup takes about three minutes. The useful part is knowing what you have once you are connected — and most guides describe a version of this connector that no longer exists.
Add https://mcp.facebook.com/ads as a custom connector in Claude, sign in to Meta,
and pick the ad accounts you want it to reach. That is the whole setup — no code, no API key,
no developer account. If it comes back saying the account is not enabled, that is Meta's rollout
gate and there is no setting on your side that changes it. Once connected, Claude reads your
performance data and your creatives, drafts campaigns, and will happily state a number
that is wrong, so verify anything you act on.
Most setup guides for this were written within a few weeks of launch and never revised. They walk you through the same three minutes correctly, then describe a connector that has since changed — wrong tool counts, capabilities listed as missing that now work, and nothing at all about the two things people actually get stuck on.
So: the setup, briefly. Then the part worth your time.
The setup
-
Add the connector 3 MINUTES
In Claude, add a custom connector pointing at
https://mcp.facebook.com/ads. This is Meta's own endpoint — announced by Meta, hosted by Meta. The trade: it only reaches Meta. Shopify, Google and the rest are separate connectors — which matters the first time you cross-check Meta’s purchases against Shopify. -
Sign in and choose accounts
You authenticate through Meta's own login and pick which ad accounts to expose. Nothing stores your password anywhere. The trade: whatever you grant, it has — so grant one account first and widen later, especially if you handle clients.
-
Ask it something read-only
Start with "List the ad accounts you can access and the last 7 days of spend for each." If that returns your real accounts and plausible numbers, you are connected. The trade: plausible is not the same as correct — cross-check one figure against Ads Manager before you trust the second answer.
That is genuinely it. If you were expecting an API key, a developer account or a terminal, those belong to the unofficial tools, not this one.
I checked for each of those by name. This is why searching for "meta ads mcp documentation" turns up vendor blog posts rather than docs. There is a real gap, and what fills it is people reporting what they saw happen — useful, but not the same thing as a rule. This page included.
What you actually get once you are in
This is where the older guides mislead. The connector's surface has grown substantially since launch, and the widely repeated tool count is the launch-day figure. Two corrections worth having before you plan a workflow around it:
| What guides usually say | What is actually true |
|---|---|
| It reads text fields only — headlines, primary text, descriptions | It reads your creatives too. There are 6 creative-facing tools, and the preview tool renders an ad in any of 8 placements. The full correction. |
| It exposes 29 tools | That is the April 2026 launch-day count, repeated ever since. I enumerated the live manifest — it is far larger, and a third of it is catalog tooling nobody writes about. |
| Paused-by-default is just a prompting convention | Stronger than that — it is enforced by the connector. All three creation tools — campaign, ad set and ad — describe themselves as creating "in PAUSED state", and there is no parameter on any of them that would let you ask for anything else. Activating is a separate, explicit step. It is a property of the tooling, not of how carefully you phrase your request. Meta's announcement page does not mention this; the tool definitions do. |
Knowing what it exposes is step one; having a routine that uses it every week is the actual job. See the weekly routine →
The two things that actually go wrong
It says your account is not enabled. Access has been rolling out account by account since April. There is no toggle in Ads Manager, Business Suite or Claude that changes it, and any guide implying otherwise is guessing. Accounts are gated independently, so check every one you can reach before concluding you are blocked — what the flag means and what to do instead of waiting.
It gives you a confident number that is wrong. Not often, but often enough to matter, and it never announces it. Fix the date window yourself, ask it to show the calls it made, and spot-check two figures in Ads Manager before acting. That habit is worth building deliberately — it is the failure that actually costs money here, not anything dramatic.
Nothing here goes rogue. The thing that costs you is a figure that arrives sounding finished when it is not.
Official connector or a third-party server?
There are a dozen third-party Meta ads MCP servers — Pipeboard, GoMarble, KonQuest and others. Some are genuinely good. The distinction that matters is not features:
- What you hand over is the real difference. Meta's own path asks you to sign in; most third-party servers ask for a long-lived token instead. There are three situations where that trade is still worth making — the honest comparison. On the underlying fear, the longer answer on account safety.
- Third-party servers really can be text-only. "It cannot see your creatives" is false of Meta's connector but true of some wrappers. If you are on one, test it rather than assuming either way.
- Governance only exists on the official path. In July 2026 Meta added portfolio-level rules letting an admin bound what an agent may do. A third-party server sits outside that entirely.
Try this tonight Connect one account, then ask: "List every tool you have from this connector, grouped by what they do." It takes a minute, touches nothing, and tells you more about what you actually have than any article — this one included.
Frequently asked questions
Do I need Claude Pro, or does the free plan work?
Custom connectors are a paid-plan feature. You also want the headroom — a real account analysis moves a lot of data, and the free tier's limits will interrupt you mid-task.
Can Claude run my ads for me?
Not autonomously. It reads, analyses and drafts; you approve and launch, and budgets stay manual. The reason that line is drawn where it is comes down to the failure mode being a confident wrong number rather than a rogue action — the full answer is here, and the four classes that decide it are here.
Does this work with ChatGPT or Gemini instead?
The connector is a standard MCP server, so other clients that support custom connectors can reach it. The setup differs per client (which clients Meta lists, and what Gemini needs instead); the capabilities are the connector's, not the model's. What changes once you leave the Claude app — and what each tool call carries with it — is covered here.
What about multiple client accounts?
Grant one account at a time and keep a separate Claude project per client so context cannot leak between them. This is about data hygiene more than anything technical. Note accounts are gated independently, so if one returns not-enabled, check the others.
Connected. Now what do you do every week?
The Claude Ads Operator is the routine that comes after setup — what to ask on Monday, how to find the winners, how to get fresh creative drafted, and the rules about what an AI is allowed to touch. Everything it drafts starts paused.
See what's inside — $67 founding pricePre-sale: the modules are still being recorded and founding members get the checkout link first. No charge today. Public price $97.