Turning Claude Into a Meta Ads Manager With the Official MCP Connector

TLDR: In April 2026 Meta released an official Ads MCP connector that plugs an ad account straight into Claude. It handles reporting, ad and campaign creation, catalogue fixes, signal diagnostics, and Help Centre lookups, all through conversation instead of the Ads Manager dashboard. It is free during the open beta and every account-changing action still needs your explicit approval inside Claude.

Summary: The pitch here is blunt, almost to a fault. The author opens by declaring that Claude just killed Meta ads agencies and that your four-thousand-dollar monthly retainer is now optional. Strip away the salesmanship and there is a genuinely interesting piece of plumbing underneath. Meta has published an official MCP server at a single endpoint, and the whole tutorial is really about connecting that one URL to Claude and then talking to your ad account the way you would talk to a junior media buyer.

The connector covers five jobs straight from Meta's own documentation. There is reporting, which pulls detailed performance and insights. There is ad creation and management, which can build and edit ads, ad sets, and full campaigns. There is catalogue management for building product feeds and fixing visibility problems. There is signal diagnostics, which checks tracking health and tells you where the data is leaking. And there is help and troubleshooting, where Claude searches Meta's Help Centre on your behalf so you stop hunting through support pages for the rule that got your ad rejected. The author's framing is that instead of clicking through Ads Manager you have a conversation, and a task that used to eat an afternoon now takes a few minutes.

Setup is genuinely simple, which is the part that matters for anyone evaluating MCP as a pattern rather than a marketing account. You need a Meta Business account with access to your ad account and a paid Claude plan, because custom connectors are a Pro, Max, or Team feature. Inside Claude you open Customize, then Connectors, then Add custom connector, and paste the Meta ads endpoint into the remote MCP server URL field. You sign in with Facebook, complete two-factor if you use it, choose which ad accounts and Pages to authorize, and approve. The smoke test is asking Claude to show your Meta ad accounts. If it lists them, you are connected.

Two details are worth holding onto because they are the actually load-bearing parts of the story. First, it is free during the open beta with no charge from Meta's side. Second, and more important from a trust standpoint, authentication runs directly between you and Meta with no third party in the middle, and any action that changes your account requires your authorization through Claude first. Nothing ships without an explicit yes. That is the right default for an agent that can spend money, and it is the design choice I would scrutinize first before letting a model anywhere near a billing-attached account.

The tutorial then walks the campaign lifecycle one prompt at a time, starting with a read-only audit. The recommended first move is to get an honest snapshot before changing anything: headline numbers across the whole account, best and worst performers ranked, and a quick read on what is healthy versus what is off. It is positioned as a replacement for the weekly ritual of opening Ads Manager and squinting at charts. The scraped content cuts off at the first prompt, so the deeper build, optimize, and fix sections live on the original page, but the architecture is clear from the setup alone.

Key takeaways:

Meta now ships an official MCP server for its Ads platform, exposing reporting, campaign management, catalogue fixes, signal diagnostics, and Help Centre search through a single connector URL.
Connecting it to Claude is a one-time custom-connector setup and requires a paid Claude plan, since custom connectors are gated to Pro, Max, and Team tiers.
Authentication is direct between the user and Meta with no intermediary, and every account-mutating action needs explicit per-action approval inside Claude.
The connector is free during its open beta, with the obvious caveat that beta terms and pricing can change.

Why do I care: This is mostly a marketing and operations story, so as a frontend engineer I would not pretend the ads workflow itself is my problem. What I do care about is the pattern. A first-party MCP server from a platform the size of Meta, with direct OAuth and a hard human-approval gate on any write, is exactly the integration shape we should expect to copy when we wire agents into our own products. The interesting architectural lesson is the separation: read operations flow freely, but anything that mutates state pauses for explicit consent. If you are building agent-facing surfaces, that consent boundary is the thing to design first, not bolt on later. I would treat the agency-killing hype with heavy skepticism, since the connector still needs someone who understands media buying to ask the right questions, but the connector itself is a clean reference implementation of MCP done by a major vendor.

Tutorial: How To Turn Claude Into Your Meta Ads Manager