How to Connect Claude to Your Meta Ads Account (And What It Can’t Do Yet)

Meta launched its official Ads AI Connectors in open beta in April 2026.

Which means you can now connect Claude directly into your ad account and ask it questions, build campaigns, pull performance signals – all without logging into Ads Manager.

I tested it as soon as it dropped.

Here’s the setup, what it actually did, and where it hit a wall.

What Is Meta’s Ads MCP?

MCP stands for Model Context Protocol.

It’s an open standard that lets AI tools like Claude connect securely to external platforms – your ad account in this case – and actually interact with them, not just read about them.

Before this launch, connecting an AI agent to Meta Ads required a developer app, weeks of waiting for API approval, or paying for a third-party connector.

Now it’s standard OAuth and it takes a few minutes.

The connection covers both Facebook and Instagram ads – they run through the same Meta Marketing API, so everything sits under one connector.

Worth knowing: you need a Claude Pro, Max, or Team plan. The free tier doesn’t support MCP connections.

How to Connect Claude to Meta Ads

Step 1 – Open Claude and go to Connectors

Click on Customise, then Connectors, then Create a new custom connector.

Give it a name – anything works, the name doesn’t affect how it functions.

Step 2 – Add the MCP server URL

Paste in Meta’s remote MCP server URL: https://mcp.facebook.com/ads

You can find this in Meta’s official documentation – I’ve linked it here: https://www.facebook.com/business/help/1456422242197840 This is the step that actually creates the bridge between Claude and your ad account.

Step 3 – Authorise the connection

Hit connect and follow the authorisation flow.

It’ll ask you one question: do you want to opt into your current businesses only, or all current and future businesses?

If you manage multiple accounts and don’t want to redo this setup later, select all current and future businesses.

Step 4 – Confirm the connection

Once authorised, you’ll see a confirmation screen saying Claude has been connected to the Ads MCP server.

Head back to Connectors and you’ll see the Meta Ads connector listed as active.

That’s it. Setup done.

What It Can Actually Do

Once it’s connected, you can ask Claude things in plain English and it will query your ad account in real time.

Here’s what I tested – and what actually worked.

Creating campaigns

I asked it to create a new leads campaign at $5 per day.

It asked which ad account to create it in, I selected one, and within a few seconds the campaign existed in Ads Manager – paused, as expected.

It then walked me through the next step unprompted: building the ad set.

Building ad sets

It recommended the optimisation goal, then flagged that my Facebook page hadn’t accepted the lead generation terms of service – which wasn’t true. I’d already accepted them and double-checked.

It couldn’t verify that on its end, so it asked which alternative optimisation goal I’d prefer instead.

We moved to link clicks and it built the ad set. But worth knowing: the MCP can’t always confirm account-level settings correctly. If it tells you something isn’t set up, verify in Ads Manager before taking its word for it.

Updating budgets

I asked it to change the campaign budget from $5 to $25 per day.

Done in seconds. No navigating menus, no clicking through campaign settings.

This is where I can already see the time-saving for anyone managing multiple accounts.

Performance signals

I asked it to pull performance for one account over the last 90 days.

This is where it gets more nuanced.

It pulled trend signals – which creatives were trending up on CTR, which were declining, estimated audience sizes, frequency patterns. It flagged that one retargeting ad set was delivering to an audience of roughly a thousand people and that frequency was climbing fast, which matched the declining CTR I was already seeing.

That’s genuinely useful.

But it can’t give you a clean table of spend, leads, and cost per lead.

It told me clearly: the MCP surfaces trend and anomaly signals, not raw totals. For exact numbers, Ads Manager is still your source.

The Limitations I Actually Hit

This is the part most write-ups skip.

Not all ad accounts have it enabled yet

When I first connected and asked it to list my accounts, it pulled all of them – but flagged that only two had the Ads MCP enabled. The rest were still being rolled out by Meta.

So if you manage multiple accounts, don’t assume it works across all of them straight away. Check which ones are enabled first.

Creative tools aren’t fully rolled out

When I tried to build an actual ad – not just a campaign shell – it hit an error on the creative step.

The MCP’s creative tool hadn’t reached that particular ad account yet. It couldn’t work around it.

The options it gave me: build the creative manually in Ads Manager, or wait and retry once the tool reaches the account.

This isn’t a Claude problem. It’s a Meta rollout problem. But it does mean you can’t run end-to-end campaign builds just yet for every account.

No raw performance data

I asked multiple times for total leads, total spend, and cost per lead figures.

Every time, it came back with the same message: those aren’t available through this connector. It can tell you the shape of performance – things are trending up, things are trending down – but not the actual numbers.

For reporting, you’re still going into Ads Manager.

Benchmark data came back empty

I asked it to pull industry benchmark data for cost per lead on one of the accounts.

Empty. Likely because there wasn’t enough conversion volume in the window, or the benchmark coverage doesn’t extend to that industry or region.

Worth testing on your account, but don’t expect it to work universally.

What Actually Shows Up in Change History

One thing I was curious about: if Claude makes a change to an account, what does Meta record?

I checked the change history after Claude updated the campaign budget.

It logged the change correctly – and when I hovered over the person making the change, it showed that the update was made via an Ads MCP server.

So the audit trail is there. Anyone reviewing change history can see what was done through the integration.

Is This Worth Using Right Now?

For execution tasks – yes.

Creating campaign shells, updating budgets, checking which accounts are enabled, getting a read on trend signals – it handles these well.

The real value right now isn’t replacing Ads Manager. It’s removing the navigation overhead for routine tasks when you already know what you want to do.

Where it doesn’t replace your existing workflow: performance reporting, creative analysis with actual numbers, and anything that requires raw spend or conversion data.

The strategy, the creative decisions, the understanding of what’s actually working – that still sits with you. The MCP just makes the mechanical execution faster.

And this is still an open beta. The capabilities will keep expanding as Meta rolls out more tools to more accounts.

If you run Meta ads at any reasonable volume, it’s worth connecting now and getting familiar with what it can do – because this is the direction everything is heading.

The Bigger Picture

Meta launched this in April 2026.

Google shipped its official Ads MCP in October 2025. Amazon Advertising followed in November 2025.

Every major ad platform is building direct AI connectivity. The workflow shift is already happening. The advertisers getting comfortable with these tools now are going to have a real edge when the capabilities catch up with the promise.

If you want help building a Meta Ads strategy that actually converts – not just the setup, but the structure, the creative, and the targeting – get in touch with the team at Ad Partner.