How to Connect Claude to Meta Ads: Official MCP Setup

Updated July 2026.

You connect Claude to Meta Ads by adding Meta's official MCP server — https://mcp.facebook.com/ads — as a custom connector in Claude and authorizing with your own Meta login. No API keys, no developer app, roughly fifteen minutes. It's the easiest official ad-platform connector shipped so far; this guide covers the verified steps, the known errors, and the half most tutorials skip — what Claude still can't do for your Meta account after you connect.

Before you start

• A paid Claude plan. Custom remote connectors aren't available on free tiers.
• Admin or full advertiser access to the Meta ad account, via the profile you'll authorize with.
• An account inside Meta's rollout. The Ads MCP launched April 29, 2026 as a gradual beta — US and higher-spend accounts first. If you're not enabled yet, calls fail with is_ads_mcp_enabled: false and there's no self-serve fix; see our troubleshooting guide.
• Use claude.ai web or Claude Desktop. Claude Code (the CLI) currently fails Meta's OAuth with "The provided redirect_uris are not registered for this client" — tracked in open GitHub issues with no user-side workaround.

How to connect Claude to Meta Ads: 6 steps

1. Open Claude's connector settings. On claude.ai: Settings → Connectors → Add custom connector.
2. Paste the official URL: https://mcp.facebook.com/ads. If a guide gives you any other URL, or asks you to create a Meta developer app or token, it's a third-party server — different risk profile, covered in is Meta Ads MCP safe?
3. Authorize with Meta. Complete the OAuth flow using the profile that has access to the right ad accounts. This is documented in the Meta Business Help Center.
4. Review tool permissions. The connector loads 29 tools, including write tools. Sensible default: leave reporting enabled and disable or restrict writes until you trust the workflow.
5. Test with a read-only prompt. "Summarize performance for ad account X over the last 14 days, split by campaign."
6. Set your working rules. Tell Claude your context (target CPA, break-even ROAS) at the start of each session — it won't remember — and require it to confirm before any write.

What to expect once connected

Meta's server exposes 29 tools across the areas named in its announcement: reporting and insights, campaign management, and catalog management. In practice that means plain-English performance pulls and breakdowns, campaign and ad set creation from a brief, budget and targeting edits, and product catalog work including feed troubleshooting.

Two behaviors to internalize before you touch anything:

• Everything Claude creates lands paused. New campaigns, ad sets, and ads must be activated manually in Ads Manager — Meta's deliberate guardrail.
• Edits to existing objects go live immediately. A budget change is real the moment the tool call succeeds. There is no draft or approval stage in the protocol.

Also expect throttling on large accounts — standard-access accounts sit under Meta's Marketing API rate limits, around 200 calls per hour by community measurement — and expect to reconnect roughly every 60 days when the access token expires.

What Claude still can't do for your Meta account

1. Remember anything. MCP is stateless. Every session starts from zero — context, targets, and yesterday's findings all have to be re-supplied.
2. Watch the account. Claude acts only when prompted. Between sessions, nothing is checking whether spend spiked or delivery collapsed.
3. Keep a change record. There's no log of what Claude changed, when, or why. Meta's native history wasn't built to reconstruct AI sessions — the gap explored in why ad platforms forget.
4. Prove what caused what. "Why did CPA jump?" gets a plausible narrative from the data in view, not measured causal inference against a change history.
5. See past Meta. One connector, one platform. Blending Google, LinkedIn, or TikTok into the analysis is on you.

The persistent layer underneath

Connect the MCP — for ad-hoc questions and drafting campaigns, it's genuinely excellent, and it's the officially supported way to put an AI on your Meta account. Then be clear-eyed that you've added a brilliant, amnesiac analyst who only works when spoken to. The Ad Spend is the layer that covers the rest: it monitors Meta (and Google Ads, LinkedIn, TikTok, and Reddit) roughly every 6 hours with 1,900+ detection algorithms, keeps a permanent version-controlled record of every change — who, what, when — traces performance moves to the exact change that caused them, and gates actions behind an approve-then-execute workflow in app or Slack, with everything logged. Connection is OAuth — no API keys, no developer setup, and no rollout waitlist. It complements Claude rather than competing with it: the assistant handles the questions you think to ask, the persistent layer handles everything you don't. See The Ad Spend vs. MCP for the full division of labor.

FAQ

How do I connect Claude to Meta Ads?

Add https://mcp.facebook.com/ads as a custom connector in Claude's settings (claude.ai web or Claude Desktop, on a paid plan), then authorize with your Meta login. No API keys or developer setup required — but your ad account must be inside Meta's gradual rollout.

Why does the connection fail in Claude Code?

Meta's OAuth client doesn't accept the localhost redirect URIs Claude Code's CLI uses, producing "The provided redirect_uris are not registered for this client." Connect from claude.ai web or Claude Desktop instead; there's no CLI workaround as of July 2026.

Can Claude launch campaigns on Meta?

It can build them — campaigns, ad sets, and ads created through the MCP all land paused and require manual activation in Ads Manager. Edits to existing objects, however, apply immediately.

Is connecting Claude to Meta Ads safe?

The official connector is a supported Meta product and using it as intended doesn't violate ad policies. The documented risks involve third-party servers on shared developer apps and unattended autonomous agents — start read-only, restrict write tools, and keep a human approval step.

Will Claude alert me if something breaks in my Meta account?

No. The MCP has no background process, alerts, or schedules — Claude only sees the account during an active chat. Continuous detection and Slack alerts require a persistent monitoring layer running between sessions.