| Route | Cost | claude.ai (web and desktop) | Claude Code | Scheduled runs | Can it change ads? |
|---|---|---|---|---|---|
| Meta's Ads MCP | Free in open beta | Custom connector | claude mcp add, or your claude.ai connector | Yes, as a claude.ai connector | Yes, new ones are created paused |
| Third-party connector | Free tier or trial, then paid | From Claude's directory, or custom | Yes | Yes, as a claude.ai connector | Depends on the tool |
| CSV export from Ads Manager | Free | Upload to the chat | Read the file | No | No |
If you run one ad account, use Meta's own server. It's free and it's the route Meta built. What follows is the Claude side: where each route works, a weekly review worth scheduling, and the number none of them gives you.
Three ways to get Meta ads data into Claude
1. Meta's own Ads MCP
Meta's server lives at https://mcp.facebook.com/ads, in open beta since 29 April 2026, with no developer app needed on the basic path (Meta for Business). It reads your reporting and can create and edit campaigns, ad sets and ads. Its tools, the click-by-click setup and Meta's error messages are in our Meta Ads MCP guide.
The Claude-side detail: as of October 2026, Meta's server isn't in Claude's connector directory. Every Meta listing there is a third party. So it goes in as a custom connector, and Claude's free plan allows one (Claude Help).
2. A third-party connector
Pay for one when Meta's route doesn't fit: your ad account shows is_ads_mcp_enabled: false because it isn't in Meta's rollout yet, you want Meta and Google in one connector, or you work in Cursor, where Meta's plain URL fails (Cursor forum).
| Connector | In Claude's directory? | Meta ads: read or write | Free option | Paid plans from |
|---|---|---|---|---|
| Windsor.ai | Yes, since January 2026 | Read. Windsor says it also has 20 write actions, with new items created paused (Windsor) | 30-day trial, then a free plan for 1 source | $23/mo, or $19/mo billed yearly (pricing) |
| Supermetrics | Yes, since February 2026 | Read, and manage campaigns | 14-day trial, no card | €49/mo, or €39/mo billed yearly. Priced in euros (pricing) |
| Adspirer | Yes, since October 2026 | Read and write. Launches are paused | 15 tool calls a month | $49/mo for 150 tool calls (pricing) |
| Pipeboard | No, add it by URL | Read and write, or read-only | 30 runs a week, 2 ad accounts | $29.90/mo (pricing) |
Prices checked October 2026.
Pipeboard says it reaches Meta through the regular Marketing API, so it doesn't depend on Meta's rollout (Pipeboard). That's the vendor's claim. Each of these holds a token to your ad account, so check what it can write before you connect it.
3. A CSV export
Zero setup. In Ads Manager, pick the level and the dates, open the Export dropdown at the top right of the table and choose CSV (adsuploader). Claude reads CSV files on every plan, up to 20 per chat (Claude Help). Some columns don't export, including the ad copy and the link. Fine for a one-off, stale the moment you download it.
Meta's own agent now reads ad accounts too, in the US and Canada, if you'd rather skip Claude: what Meta Muse means for a Shopify store.
Which Claude surface each one works in
| Meta's Ads MCP | Third-party connector | CSV | |
|---|---|---|---|
| claude.ai on the web | Customize, then Connectors, then add a custom connector | From the directory, or as a custom connector | Upload |
| Claude Desktop and mobile | Uses the connectors on your account. Adding custom ones on mobile is in beta | Same | Upload |
| Claude Code | claude mcp add, or your claude.ai connectors when you log in with your Claude account | Same | Point it at the file |
| Scheduled tasks | Only as a claude.ai connector | Only as a claude.ai connector | No |
From Claude Help and the Claude Code docs.
Two rows trip people up. Claude Code only loads your claude.ai connectors when you're logged in with a Claude subscription, and an ANTHROPIC_API_KEY in your shell switches them off. And a server added with claude mcp add stays on your laptop, so a scheduled task in the cloud can't see it (Claude Code docs). To schedule the weekly review below, add Meta in claude.ai.
Set it up in Claude
- Pick your route from the table at the top.
- In claude.ai, open Customize, then Connectors, and add
https://mcp.facebook.com/adsas a custom connector. On Team or Enterprise, an Owner adds it in Organization settings first. The full click path is in the Meta Ads MCP guide. - Sign in with Facebook and pick one business portfolio. The access covers everything in it.
- If you only want reports, set server rules in Meta Business Suite first. They can block creating campaigns, ad sets and ads, budget increases, and pausing or activating (Meta, server rules).
- In a new chat, open "+", then Connectors, switch Meta on and ask "List my ad accounts," Meta's own test prompt (Meta, get started).
- Run the weekly review below once by hand. When the answer looks right, schedule it.
Claude Code
claude mcp add --transport http meta-ads https://mcp.facebook.com/ads
Then run /mcp and finish the Facebook login in your browser. Add --scope user to have it in every project (Claude Code docs). When I set it up this way on 19 October 2026, the plain URL worked and it listed 97 tools. If Meta is already in your claude.ai connectors, skip this step.
A weekly Meta review in Claude
Meta's reporting tools return spend, impressions, CTR, CPC, CPM and conversions per campaign, ad set or ad, plus trends and anomaly flags (Meta, reporting tools). Same prompt every week:
Weekly Meta review. Ad account: <name>. Compare the last 7 days with the 7 days before.
1. What changed in the account this week, and who changed it?
2. For every active ad: spend, link clicks, CTR, cost per result, results.
3. Which ads got worse on cost per result, and which lost CTR day after day?
4. Any delivery errors, rejected ads, or anomalies Meta flags?
5. Is the purchase event healthy: events received and Event Match Quality?
Read only. Don't create, pause or edit anything.
End with three lines: keep, cut, and what to check on the site.
The order matters. A change somebody made (or an agent made) is the quickest thing to rule out, so it goes first. Errors and tracking come before you judge any ad, because a broken pixel makes every ad look bad at once.
To schedule it, type /schedule in Claude Code, or create a weekly task at claude.ai/code/routines. Scheduled tasks are on Pro, Max, Team and Enterprise. Anthropic's docs carry a warning: during a scheduled run, Claude "can use every tool from an included connector, including writes, without asking for permission" (Claude Code docs). The "Read only" line asks nicely. A Meta server rule that blocks creation and budget changes enforces it.
What Meta's numbers can't show
Every number in that review is Meta's count. None of it says what visitors did once your page loaded.
We launched a seven-ad creative test for anry.io on 19 October 2026. On day one, Meta's view looked like a normal test: spend, clicks, CTR and 8 conversions. Then we joined each ad to what its visitors did on our site.
| What Meta showed | What the join showed | |
|---|---|---|
| Conversions | 8 | 0 real trial-button taps. All 8 were Meta's ad-review bots: visits from data-centre towns, some faking Instagram and Facebook in-app browsers |
| Cost per visitor who stayed 5 seconds or more | Not a Meta metric | A$4.47 for the best ad, A$21.90 for the worst |
(anry.io sells software, so a conversion for us is a trial tap, not an order.)
The worst ad cost almost five times as much per visitor who stayed as the best one, and nothing in Ads Manager showed it. Ask Claude to rank those seven ads with Meta's MCP alone and it ranks them on bot conversions. If your clicks aren't turning into orders, the check order for Meta clicks with no sales starts with placements and purchase tracking.
Is it safe?
Meta's server is the route Meta built, and new campaigns are created paused. The Claude-side risk is unattended writes: a scheduled run doesn't stop to ask, and a custom connector is a service Anthropic hasn't verified (Claude Help). Lock scheduled tasks with Meta's server rules and remove connectors a task doesn't use. What actually gets ad accounts suspended is in will connecting AI get my ad account banned.
Common errors and the fix
| Problem | Cause | Fix |
|---|---|---|
| Claude answers in general terms, not from your account | The connector is off in this chat | "+", then Connectors, switch Meta on |
| You can't add a second custom connector | The free plan allows one | Remove the other one, or upgrade |
Meta doesn't show in Claude Code's /mcp | An API key or token is set, so claude.ai connectors don't load | Unset ANTHROPIC_API_KEY and /login with your Claude account, or use claude mcp add |
| The scheduled task has no Meta tools | Meta was added with claude mcp add, which stays on your machine | Add it in claude.ai under Customize, then Connectors |
Where Anry fits
Claude plus Meta's server tells you what Meta counted. Anry adds the other half: it follows each ad click to the visit and the order, and puts a price on the ads and pages where money leaks, counted in your store's own orders. It's a read-only MCP server with 16 tools that sits next to Meta's in Claude, Claude Code and Cursor, and it can't change a campaign. If a weekly report on Meta's numbers is all you need, Meta's free server is enough.
claude mcp add --transport http anry https://mcp.anry.io/mcp
Frequently asked questions
Is Meta's Ads MCP in Claude's connector directory?
Not as of October 2026. You add https://mcp.facebook.com/ads as a custom connector in claude.ai, or with claude mcp add in Claude Code. The Meta connectors in the directory, such as Windsor.ai and Supermetrics, are third-party.
Does connecting Claude to Meta Ads work on the free plan?
Yes. Free accounts get one custom connector, which is enough for Meta's server. Scheduled tasks need Pro, Max, Team or Enterprise.
Can Claude send me a Meta ads report every week?
Yes, with a scheduled task. Add Meta as a claude.ai connector, write the prompt once and pick a weekly schedule. Make it read-only with Meta's server rules, because scheduled runs don't ask before using a tool.
Can I use Claude for Facebook ads without an MCP?
Yes. Export the Ads Manager table as a CSV and upload it to a chat. You get a snapshot, not live data, and some columns, such as the ad copy, don't export.
Which Meta ads connector is best for Claude?
For one ad account, Meta's own. It's free and it's the route Meta built. A third-party connector earns its price when your account isn't in Meta's rollout yet, or when you want several ad platforms in one place.
Sources
- Meta ads AI connectors, Meta for Business
- Ads MCP server: get started, reporting tools and server rules, Meta for Developers
- Get started with custom connectors using remote MCP and Use connectors to extend Claude's capabilities, Claude Help Center
- What kinds of documents can I upload to Claude?, Claude Help Center
- Connect Claude Code to tools via MCP and Automate work with scheduled tasks, Claude Code docs
- Windsor.ai, Supermetrics and Adspirer Social Ads, Claude directory
- Windsor.ai pricing and managing Facebook ads from Claude, Windsor.ai
- Supermetrics pricing
- Adspirer pricing
- Pipeboard pricing and Facebook-hosted Ads MCP rollout, Pipeboard
- How to export Facebook ads data, adsuploader, April 2026
- Official Meta Ads MCP OAuth fails in Cursor, Cursor forum
- Anry MCP server docs
See which ad clicks leave your store before they buy.
14-day free trial, no card. Works in Claude, Claude Code and Cursor.