What the Meta Ads connector actually is
For years the only ways into Meta's Marketing API were Ads Manager or code.
That changed on 29 April 2026, when Meta shipped ads AI
connectors in open beta. There are two halves to the release. The
ads MCP server is the chat route, a Meta-hosted endpoint at
https://mcp.facebook.com/ads that any MCP-compatible assistant
can call. The ads CLI is the terminal route, aimed at
developers and technical media buyers who want scripted runs. If you are a
marketer, you want the MCP server.
The important part is who does the authenticating. You are not handing an API key to a third party and hoping it stores it well. You sign in through Facebook Login for Business, choose which business portfolios to expose, and the token lives between you and Meta. That also means it is Meta-sanctioned traffic, which matters given that advertisers were reporting account restrictions earlier in 2026 for unapproved AI integrations.
Connector or MCP server? Same thing, seen from two ends. The MCP server is the service Meta runs. The connector is what you add and see inside Claude. You never touch the server directly, and for this one you never touch a key either.
What it can do, category by category
Meta groups the tools into seven categories. The counts below come from our read of Meta's documentation in July 2026, and the surface has grown quickly: write-ups from the launch window counted 29 tools, where the docs now describe around 90. Expect your own connector to list somewhere in between while the beta rolls out, and expect the number to keep moving.
| Category | Tools | What it means for a marketer |
|---|---|---|
| Comprehensive reporting read only | 7 | The part you will use daily. ads_get_ad_entities pulls spend, impressions, CTR, CPC, CPM and conversions at any level with filters and breakdowns. Alongside it: industry benchmarks against similar advertisers, auction ranking, anomaly detection, performance trends, and an account opportunity score out of 100. |
| Ad creation and management read and write | 27 | Build campaigns, ad sets and ads. Also custom audiences including lookalikes, Instagram post boosting, placement previews, and ads_library_search for competitor research in the public Ad Library. |
| Catalog creation and management read and write | 34 | The biggest category, and mostly an ecommerce concern. Catalogs, products, product sets, feeds, feed rules and event sources, plus diagnostics for why an item is not showing and a health check for Advantage+ catalog ads. |
| Signals and datasets read and write | 13 | Pixel and Conversions API health. Event volume, Event Match Quality scores, data freshness by channel, and rules for which events and parameters a pixel captures. |
| A/B tests and lift studies read and write | 7 | Check eligibility, create split tests by defining cells, pull results, and run conversion lift studies to measure incremental impact rather than last-click. |
| Help and troubleshooting read only | 2 | ads_get_errors sweeps for delivery-blocking errors across a whole account in one prompt, and a Business Help Center search grounds answers in Meta's own policy pages. |
| Activity logs read only | 1 | The Ads Manager campaign history page, queryable. Who changed what and when, scoped by object, time window or user. |
Set it up in Claude, step by step
Claude is a good first client for this because custom connectors are available on every plan, including free, and the whole flow is clicks rather than config files. Budget about ten minutes.
Check your access before you start
You need an advertiser or admin role on the ad account in Meta Business Manager. On the Claude side, free accounts can hold one custom connector at a time, so if you already use one you will have to choose. On a Team or Enterprise plan the organisation owner has to add the connector in organisation settings first, then members authenticate individually.
Beta caveat. Open beta does not mean everyone. Some advertisers can complete every step below and still get nothing back, because their account has not been switched on yet. If that happens, the setup is not wrong, it is waiting.
Add the custom connector
In Claude, open Customize, then Connectors. Click the plus button and choose Add custom connector. Name it something you will recognise, like Meta Ads, and paste the server URL exactly, with no trailing slash and nothing appended.
https://mcp.facebook.com/ads
Leave the advanced OAuth settings alone. Those exist for people connecting through their own Meta developer app, which you do not need for this route.
Authorise, and be picky about scope
The connector appears in your list but is not connected yet. Click Connect and Claude hands you to Facebook Login for Business, where you sign in and choose which business portfolios and ad accounts to expose.
This is the one screen worth slowing down on. The connector inherits the access your Facebook user already has, and for anyone at an agency that can mean a long list of client accounts. Grant the accounts you actually intend to work on and nothing else. You can revoke or change this later in your Meta business settings.
Turn it on inside the chat
A connector that exists in settings is still dormant in a conversation. Start a new chat, click the plus button, open Connectors and toggle Meta Ads on. This is per conversation, which is a feature rather than a nuisance: you can keep a research chat that has no path to your ad account at all.
Verify with something read-only
Do not open with a campaign build. Ask for a list of your ad accounts. If real names, currencies and timezones come back, you are connected, and you have learned what the connector can see without changing anything.
List the Meta ad accounts you can see, with their currency and status. Don't change anything.
Other clients. The same server works in ChatGPT, Perplexity and Cursor. Claude Code is different: Meta documents it as claude mcp add --transport http --client-id <META_APP_ID> meta-ads https://mcp.facebook.com/ads, which needs your own Meta developer app ID and a matching redirect URL registered in its Facebook Login settings. Without that registration the OAuth handshake fails. For a marketer, the browser or desktop app is the path of least resistance.
The first five prompts worth running
The connector's value shows up fastest on questions that are annoying in Ads Manager, not on questions Ads Manager already answers well. If you know the columns and filters you want, the dashboard is quicker. What this replaces is the moment you would normally export to a spreadsheet to answer something slightly more specific.
Top 10 ad sets by ROAS over the last 30 days, but only ones with at least 50 conversions, broken out by placement. Flag any where frequency is above 3.
What's unusual about this account this week? Check for anomalies, then compare my CPM and CTR against industry benchmarks for similar advertisers.
Sweep every active campaign and ad set for delivery-blocking errors and summarise what's broken and how urgent each one is.
Review my pixel setup: event volume over the last 28 days, Event Match Quality by match key, and data freshness. Tell me what to fix first.
Search the Meta Ad Library for ads currently running from [competitor]. Summarise their angles, formats and offers, and where they overlap with mine.
The jobs it is genuinely good at
After a few weeks of these connectors being in the wild, a pattern has settled: the read-heavy work is where the value is obvious and the risk is near zero, and it gets more debatable the closer you get to spending money.
- Reporting without the export step. Any level, any period, any breakdown, asked in a sentence. This is the one that earns its place immediately.
- Diagnostics. Frequency creep, CPM spikes and conversion drops surfaced before you would have noticed them, with benchmark context to tell you whether it is your account or your whole category.
- Error sweeps. One prompt across the account instead of clicking into each entity. Configuration errors only, so it will not catch policy rejections.
- Signal health. The pixel and Conversions API audit that always gets postponed, done in a paragraph.
- Catalog troubleshooting. For ecommerce, why an item is not showing, which feed rule broke, whether the catalog is healthy enough for Advantage+ catalog ads.
- Structured build-out. Duplicating a proven ad set with new variants, paused, ready for review. Faster than the Ads Manager click path and reviewable before it goes live.
- Change forensics. Activity logs turn "when did this budget change and who did it" into a question rather than an investigation.
What it will not do
Four limits are worth internalising before you build a process on top of this, because none of them are obvious from the announcement.
- It does not make your creative. The creative tools here assemble and inspect, they do not generate.
ads_create_creativebuilds a single-image link creative, and the other tools list images and videos already uploaded to the account or render a placement preview. The image or video itself has to come from somewhere else, which is what the image tools and video tools guides are for. - It does not run on its own. There are no triggers and no background execution. Nothing happens unless you are in a conversation asking for it, so "watch my CPA and act overnight" is not what this is.
- It is one platform. Facebook, Instagram and Audience Network together, and nothing else. Google, TikTok and the rest need their own connectors.
- It is a beta. Tools appear, change and occasionally break. It is free now, and Meta has said nothing about what it costs later or when general availability lands.
Before you connect a live account
The honest framing is that this is a read and write connection to the system
that spends your money, so a little friction up front is worth it. Meta has
built in the most important guardrail already: write tools create
campaigns, ad sets and ads in a paused state, and your AI client asks
for confirmation before activation. Spend starts only when
ads_activate_entity runs, which is a separate and deliberate
step.
That still leaves edges. Budget and targeting edits to something already live take effect immediately, with no draft state to catch them. So:
- Set account-level spend caps in Meta before you connect, not after.
- Authorise one account first, ideally a low-spend one, and add more when you are comfortable. Do not grant a portfolio of high-spend client accounts on day one.
- Live in read-only prompts for the first week, and say so explicitly in the prompt when you mean it.
- Ask for paused output by default, and keep activation as something you do yourself in Ads Manager.
- Put a recurring reminder in to review connected integrations in your Meta business settings, and revoke what you are no longer using.
The subtler risk is not technical. It is deciding that because a task can be automated, its output no longer needs reading. Reporting and diagnosis are genuinely low risk. Structural changes to a spending account are not, and the lesson plenty of advertisers are learning this year is that the expensive mistakes are the ones nobody looked at.
Meta's official connector versus a third-party one
Third-party Meta ads MCP servers existed well before Meta's, and some still do things the official one does not. This is not a ranking, just where the real differences sit.
| Route | Where it wins | What you give up |
|---|---|---|
| Meta's official MCP server mcp.facebook.com/ads | First-party OAuth with no key to store or rotate, sanctioned traffic, and by far the widest tool surface, including catalogs, lift studies and signal quality that third parties rarely reach. | One account at a time in practice, no cross-account roll-ups, no scheduling or alerting, and beta instability. |
| Third-party MCP servers various vendors | Cross-account and cross-platform reporting, scheduled runs and alerts, and a free tier or flat plan you can read up front. | Another vendor holding access to your ad account, a narrower tool set, and dependence on how quickly they track Meta's API changes. |
| Meta's ads CLI terminal | Repeatable scripted workflows, and pairs well with a coding agent for bulk operations. | It is a developer tool. If the command line is not already part of your day, this is the wrong half of the release for you. |
For most marketers the answer is to start with Meta's own connector, because the auth story is the best and it costs nothing right now, and only add something else once you hit a specific wall like multi-account reporting.
Where Plainpaper fits
Meta's connector is the account layer: it reads performance and writes structure. What it has no opinion about is the middle of the job, where a concept becomes copy, copy gets a visual, and a human decides the thing is good enough to run. That work currently scatters across a chat log.
Plainpaper is the board it lands on instead. The agent reads spend results through the Meta connector, drafts the next round of creative, pulls the image from a design tool, and each variant becomes a card with its brief and its approval state attached. You approve the real rendered ad, and only then does anything get built and activated. The Claude and Meta Ads creative workflow walks through that half in detail.
The connector can build a campaign in a minute. The board is where one human looks at the actual ad and decides it deserves budget.
Pull last 30 days by ad set from Meta and find my three best-performing angles. Draft two new creative variants for each, put them on cards for approval, and build them in Meta as paused ad sets once I've signed off.
Key takeaways
- Meta's ads MCP server is a Meta-hosted endpoint at mcp.facebook.com/ads that you add to Claude yourself as a custom connector. No API key, no code, no Meta developer app for that route.
- Around 90 tools across seven categories as of July 2026. The "29 tools" figure circulating from launch is out of date, and your own connector may still show fewer while the beta rolls out.
- Custom connectors work on every Claude plan including free, with a limit of one at a time on free. Team and Enterprise need the owner to add it first.
- Write tools create entities paused and the client confirms before activation, so spend needs a deliberate step. Edits to already-live campaigns are immediate, so set spend caps before you connect.
- The connector inherits your Facebook user's account access, so authorise one low-spend account first rather than a whole client portfolio.
- It reports, diagnoses and builds structure. It does not generate creative, does not run on a schedule, and covers only Meta.
Frequently asked questions
Do I need a developer or a Meta app to use the Meta Ads MCP server?
Not for the Claude connector route. You paste the server URL into Claude, sign in with Facebook Login for Business, and pick your business portfolios. A Meta developer app is only needed for the programmatic routes, such as Claude Code or a raw access token, where you supply your own app ID as the OAuth client ID.
Is the Meta Ads MCP server free?
It is free during the open beta that started on 29 April 2026. Meta has not announced a general availability date or post-beta pricing, so treat today's price as a beta condition rather than a permanent one.
Can Claude launch a campaign and start spending my budget?
Not by accident. Write tools create campaigns, ad sets and ads paused, and your client asks for confirmation before activation, so spend starts only when the activation tool runs on a paused entity. Budget and targeting edits to something already live are immediate, though, which is why account spend caps belong in place before you connect.
How many tools does the Meta Ads MCP server have?
Meta's July 2026 documentation describes around 90, across comprehensive reporting, ad creation and management, catalog creation and management, signals and datasets, A/B tests and conversion lift studies, help and troubleshooting, and activity logs. Launch-window articles counted 29 because the beta surface was much smaller then.
Does it work on the free Claude plan?
Yes. Custom connectors are available on every Claude plan including free, though free accounts hold one custom connector at a time. Team and Enterprise organisations need the owner to add it in organisation settings before members can authenticate.
What is the difference between the ads MCP server and the ads CLI?
Two halves of the same release. The MCP server is the chat route your AI assistant calls in natural language. The CLI is a terminal tool for scripted, repeatable runs. Marketers want the MCP server.
Can the connector write my ad creative?
Only partly. It writes copy fields, assembles a single-image link creative, lists media already in the account, and renders a placement preview. It does not generate the image or the video, so those come from a creative tool you connect separately and the ads connector attaches the result.
Next step: give the account a front end
Connect the server, spend a week asking it read-only questions, and you will have a clear sense of what it is worth to you before anything writes to a campaign. The piece that turns it from a smarter dashboard into a workflow is the board in the middle, where the creative your agent drafts becomes a real rendered ad you approve before it gets budget. Plainpaper is free to try and connects to your agent in a couple of minutes. Browse the rest of the tools gallery, or read the Claude and Meta Ads creative workflow for the half of the job the connector does not cover.