How to Run Your Meta Ad Campaigns From a Claude Chat (Meta's Official MCP)

If you run Meta ads for clients, you already know the tax that comes with it: Ads Manager open in one tab, a report you're rebuilding from scratch in another, a client thread asking why cost per lead moved this week. None of that busywork was ever the actual skill. The skill was knowing what to change and why. In 2026, Meta finally shipped a way to skip straight to that part.

On April 29, 2026, Meta launched an official AI Connector for Claude — a hosted MCP (Model Context Protocol) server at mcp.facebook.com/ads that gives Claude direct, authenticated access to a connected ad account. Set it up once through Meta's own Business login, and every chat after that can read the account and act on it, no CSV export and no copy-pasted number in sight.

What actually changes once it's connected

For an agency running Meta ads for real estate clients, the shift shows up in three places.

1. Reporting. "Pull this week's spend, CPL, and lead volume for the Joka project, by ad set" returns an answer built from the live account, not a screenshot from three days ago.

2. Building campaigns. Hand Claude a creative and a brief — "spin up a campaign for this carousel, targeting homebuyers within 15km of the site" — and it assembles the campaign, ad set, and ad using the account's own targeting and placement options.

3. Shifting budget. Once a split test has a clear winner, "move the budget to the winner ad" is one instruction instead of a manual pause-and-edit pass across ad sets.

The part that actually matters: everything lands paused

This is the detail that makes the rest of it usable instead of terrifying. Every campaign, ad set, and ad Claude creates through the Meta MCP is built in a paused state by default. Nothing spends until a human opens the account and switches it on. Claude can also flag setup errors and delivery issues before that happens, so the review step catches real problems, not just typos.

That one default is doing more work than any prompt ever could. It means the AI can build the account. It doesn't get to spend the account's money. That decision stays with whoever's name is on the client contract.

Setting it up

None of this requires an engineer.

1. Connect the account. Add Meta's connector from Claude's connector settings, or as a custom connector using the server address mcp.facebook.com/ads if it isn't in your directory yet.

2. Grant access. Sign in through Meta's own Business login and choose which Business Portfolio Claude can see — the same permission screen you'd use for any ad partner integration.

3. Confirm the connection. Ask Claude to list your active campaigns. If it comes back with real account data, the connector is live.

4. Start small. Before handing over a campaign build, ask Claude to pull last week's numbers first. It's the fastest way to confirm it's reading the right ad account before you trust it with anything that touches spend.

What this is actually worth to an agency

The honest version of this isn't "AI replaces the media buyer." It's that the parts of the job that were never really strategy — exporting numbers, rebuilding the same report template, pausing a losing ad set at 11pm — stop eating the week. Testing structure, naming conventions, audience overlap, budget pacing: still worth knowing. What doesn't need to keep taking a Tuesday afternoon is the mechanical half of running it.

For agencies specifically, that's margin. The setup that saves your own team hours is also the operational backbone of a retainer you're already charging for.

Where to still keep your hands on the wheel

The MCP gives Claude the tools to act on an account. It doesn't give it your read on a client's market, budget ceiling, or brand risk tolerance. Treat every AI-built campaign the way you'd treat a junior media buyer's first draft — reviewed by someone who owns the outcome, every time. And because this connects to a live ad account, keep the same access hygiene you'd use for any integration: know which Business Portfolio is connected, and disconnect it the moment a client relationship ends.

The agencies getting the most out of this in 2026 aren't the ones who stopped watching their accounts. They're the ones who stopped doing the part of the job that never needed a human in the first place.