For years, a thick layer of SaaS tools (Madgicx, Revealbot, Adriel, Smartly, and others) charged $300–500/month just to wrap the Meta Ads API in a friendlier interface. The official MCP exposes all 29 ad operations as native tools Claude can call through plain language. This guide shows you how to set it up and what you can do with it.
Step 1: Connect Your Meta Account via OAuth
Open Claude (or your MCP-compatible agent). Navigate to the MCP server settings and add Meta's official MCP connector. You will be prompted to complete a standard OAuth flow — log in with the Meta Business account that owns your ad accounts. Grant the requested permissions. This is a one-time step; Claude stores the token and reuses it across sessions.
Pro tip: Use a Business Manager admin account so Claude has access to all ad accounts, catalogs, and pixels under that umbrella from day one.
Step 2: Verify the 29 Ad Operations Are Available
After OAuth completes, ask Claude: "What Meta Ads tools do you have access to?" Claude will list the callable operations. Confirm you can see tools covering campaigns, ad sets, creatives, catalogs, and signals diagnostics. If any are missing, re-check the permissions scope granted during OAuth.
Step 3: Create or Edit a Campaign with Natural Language
Type a plain-language instruction such as: "Create a Traffic campaign targeting US women 25–44 interested in skincare, with a $50/day budget, starting tomorrow." Claude translates this into the correct API calls, sets the campaign objective, defines the audience, and returns a confirmation with the campaign ID. To edit an existing campaign, reference it by name or ID: "Pause the Summer Sale campaign and duplicate it with a 20% higher budget."
Step 4: Diagnose Tracking Signals
If your pixel or Conversions API is misfiring, ask: "Check the signal quality for pixel [ID] and tell me what events are missing or duplicated." Claude pulls the diagnostics endpoint and surfaces the specific events that are underreporting, along with the recommended fix — no Ads Manager tab-switching required.
Step 5: Manage Catalogs and Pull Benchmarks
For e-commerce accounts, instruct Claude to update product catalog metadata, pause out-of-stock items, or sync a new feed URL. For performance context, ask Claude to pull account-level benchmarks (CPM, CTR, ROAS by placement) and compare them against your last 30-day averages in the same prompt.
Why This Works
Meta's MCP server exposes the same underlying Graph API that third-party SaaS tools have always used, but removes the intermediary entirely. Because the connection is OAuth-authenticated directly between Claude and Meta, there is no third-party app in the chain that Meta could suspend for policy violations. The natural-language interface also collapses the gap between intent and execution — a single sentence can trigger a sequence of API calls that previously required navigating multiple Ads Manager screens.
Pro Tips
- Stay in beta early. The connector is free during the beta period. Establish your workflows now before any pricing is introduced.
- Chain operations in one prompt. Claude can create a campaign, build the ad set, attach a creative, and enable it in a single conversation turn — ask for the full sequence upfront.
- Use benchmarks before scaling. Pull CPM and ROAS benchmarks for the specific placement and audience before increasing budgets; Claude can do both in one response.
- Audit with natural language. At the end of each week, ask Claude for a plain-English summary of which ad sets overspent, underdelivered, or hit frequency caps — faster than any dashboard export.
The official MCP connector does not replace creative strategy or media buying judgment, but it eliminates the operational overhead that a layer of $300–500/month tools was built to absorb. If you manage Meta Ads, authenticating once and building Claude-based workflows is now the lowest-friction path to the same API access.
Want a hand?
Book a 30-min call.
Walk through your stack with us. We'll find the bottleneck and map out the exact wiring you need — free.