Meta Ads AI Connectors
by Meta· vopen-beta-2026-05-20proprietary

Morning Meta Ads health check in one prompt — free, 30 seconds to connect.

Hosted by Meta. Connect once in Claude.ai — anomaly alerts, opportunity scores, auction-rank benchmarks land in your chat. Works in Claude Desktop, ChatGPT, Cursor too. Free during open beta.

Time from intent to first prompt
30 min setup1 click
When you manage multiple ad accounts
1 by 1All at once
Daily account audit
Ads Manager1 prompt

Who this is for

Meaningful time-saver and would unlock scale, giving teams the ability to rapidly test and iterate creative, deliver real-time personalization, and maintain stronger oversight and QA.

Abby Doeden, Performance Marketing Director at Broadhead

How this changes your work

Daily account health diagnostic

Today

Open Ads Manager. Click into each campaign. Look at yesterday's spend, ROAS, CTR. Note anything weird. Toggle to ad-set level. Repeat across 12 campaigns. 25 minutes — every morning before strategy.

With Meta Ads AI Connectors
You ask

Run my morning Meta Ads diagnostic — opportunity score, anomalies, auction-rank vs peers.

Claude

Today's Meta Ads health (act_4827)

Opportunity score 67/100. 3 anomalies: Q4-Holiday daily spend +42% vs 7-day avg; AS_412 CTR drop 31%; conversion lag on Acme-launch (3.2x baseline). Auction rank declining on 2 campaigns: down to 6th vs 3rd last week. Top recommendation: consolidate audience-fragmented ad sets (estimated +18% efficiency).

All three signals (opportunity_score, anomaly_signal, auction_ranking_benchmarks) come from Meta's own ML — not third-party heuristics.

25 min → 30 sec

Operator-reported time at getpassionfruit.com / leadsync.me — confirmed on the official tool surface

Launch a campaign end-to-end from a brief

Today

Open Ads Manager. Create campaign. Set objective. Create ad set: budget, audience, placement, schedule. Create creative: copy, image, CTA. Create ad linking it all. Activate each level individually. 45 minutes per launch.

With Meta Ads AI Connectors
You ask

Launch a Spring Sale campaign for act_4827 — $80/day, US 25–45 interested in fitness, lead-gen objective, page @brandPage, message 'Free trial Apr–Jun'.

Claude

Spring Sale campaign created (status: paused)

Campaign + 1 ad set + 1 ad live in act_4827. Objective: OUTCOME_LEADS. Targeting: US 25–45, Fitness/Wellness flex. Daily budget: $80. Creative attached. All entities paused — confirm to activate.

ads_create_campaign → ads_create_ad_set → ads_create_creative → ads_create_ad → ads_activate_entity (only after you confirm).

45 min → 4 min

Tool chain executes in seconds; you spend the rest naming and reviewing

Set up a product catalog for Dynamic Ads

Today

Sign in to Commerce Manager. Create catalog. Upload CSV or paste feed URL. Wait for ingestion. Check diagnostics for errors. Create product set with filter. Use it in Dynamic Ads — if it works.

With Meta Ads AI Connectors
You ask

Create a Spring Apparel catalog for business 184729, upload my feed at https://shop.example.com/feed.csv, then a product set for in-stock items sized M/L under $80.

Claude

Catalog + product set created

Catalog 'Spring Apparel' created. Feed imported (847 products, 12 with warnings — see diagnostics). Product set 'Spring M-L sub-$80' matches 312 items.

ads_catalog_create → ads_catalog_get_diagnostics → ads_catalog_create_product_set chained in one prompt.

20 min → 60 sec

Commerce Manager UI requires 4 separate flows; tools chain in one call

Audit underperformers and apply Meta's own recommendations

Today

Pull insights from each campaign. Compare to last week. Open the recommendation panel. Filter to the 2 underperformers. Look at audience-overlap diagnostics. Decide what to pause and what to scale.

With Meta Ads AI Connectors
You ask

Show last 14 days performance trend for Q4-Holiday and Acme-launch in act_4827, plus Meta's opportunity recommendations for both.

Claude

Performance trend + recommendations for 2 campaigns

Q4-Holiday: ROAS down 23% (3.4 → 2.6), CPM up 18%. Recommendation: consolidate 4 fragmented ad sets, raise budget cap to test scaling. Acme-launch: stable ROAS 2.8 but CPA 30% above industry benchmark. Recommendation: refresh creative (frequency 4.7 — fatigue territory).

ads_insights_performance_trend + ads_get_opportunity_score in one query.

30 min → 90 sec

Two API calls, one prompt — eliminates the spreadsheet step

Works with

Proof

25 min → 30 sec

morning health check across active campaigns

Operator-reported pain on Ads Manager click-through (getpassionfruit + leadsync research)

Free

during the open beta — no cost to test it

Meta launch announcement, 2026-04-29

0

developer apps, tokens, or servers to manage

Sign-in handles auth — no Meta Business app, no Railway box, no .env

1 sign-in

covers every ad account you can access

Single consent covers every advertiser under your Meta user

3 signals

spend spikes, CTR drops, conversion lag — caught before Monday's review

Meta's own ML behind opportunity score, anomaly signal, auction-rank benchmarks

Use it with

Meta Ads AI Connectors works with Claude Desktop, Claude Code, Cursor, Codex, Gemini, Windsurf, OpenClaw, and Hermes — any MCP-compatible AI client. Get it running in seconds.

Compatible withChatGPTClaudeClaude CodeClaude DesktopCursor
Install on ElasticFlow
One click. Managed auth.

Pre-configured environment, OAuth handled for you. No command-line work.

Install on ElasticFlow →

Managed auth · No laptop setup.

OAuth — authorise in one click

Install on your AI client
Claude.ai web (primary) · Claude Desktop · ChatGPT (Plus) · Cursor (Pro)

Copy a config snippet into your AI client and restart.

  • One sign-in. No JSON, no terminal, no token.
  • All 5 Meta permissions auto-attach on the consent screen.
  • Tools appear in the next chat — 'Connectors' panel lists what's available.
# No JSON config. Just:
# 1. Open https://claude.ai/customize/connectors
# 2. Find 'Meta Ads' in the connector list
# 3. Click 'Connect'
# 4. Meta consent screen → accept → done

Phased rollout — US and high-spend ad accounts get access first. If 'Meta Ads' isn't visible, your account is not yet enabled.

Authentication

Steps

  1. Open Claude.ai Connectors

    Go to https://claude.ai/customize/connectors. Find 'Meta Ads' in the list. If you don't see it, your account is in Meta's phased rollout queue — check back in 1-2 weeks or contact your Meta Business rep.

  2. Click 'Connect Meta Ads'

    Claude.ai opens Meta's consent screen. You'll see the 5 scopes the MCP needs — these auto-attach, no scope-picking required.

  3. Accept the 5 Marketing API scopes

    Review the scopes (ads_management, ads_read, catalog_management, business_management, pages_show_list) and click Accept. Meta sends you back to Claude.ai, the connector now reads 'Connected'.

  4. Tools appear in chat

    Open a new Claude.ai chat with the Meta Ads connector toggled on (or invoke any tool in Claude Code — federation propagates). 44 tools are live.

  5. Switch ad accounts via prompt

    If you have multiple ad accounts, ask Claude to switch — `ads_get_ad_accounts` lists them, then operate on any by ID. One sign-in covers every account you can access.

Scopes explained

ScopeWhy this MCP needs it
ads_managementRequired — create, modify, pause campaigns / ad sets / ads / creatives. Without this, every write call fails.
ads_readRequired — pull insights, performance trend, anomaly signals, opportunity score, auction benchmarks.
catalog_managementRequired — manage product catalogs, feeds, product sets for Dynamic Ads.
business_managementRequired — list ad accounts under your business, access dataset / Pixel diagnostics.
pages_show_listRequired — discover Facebook Pages you can promote as ad page actors in creatives.

Troubleshooting

~7 min first time

PROPRIETARY · vopen-beta-2026-05-20 · last release 22 days ago

What Claude can do

All 44 tools cover the Meta Marketing API surface for AI assistants. These groupings are by user job — diagnose, launch, read, manage catalogs, audiences, signal health — not by API namespace.

Three of these tools (opportunity_score, anomaly_signal, auction_ranking_benchmarks) are surfaces Meta runs internally and exposes natively here. Community wrappers do not implement them.

Pull account-level opportunity score (0–100) with ranked recommendations

Returns Meta's own optimization score for an ad account plus actionable recommendations sorted by estimated points-impact. Used as the first step of a daily account audit.

Detect statistical anomalies in spend, CTR, conversions

Flags deviations that warrant review — sudden CTR drops, spend overshoots, conversion lag. Distinguishes anomalies from causally-linked optimization recommendations.

See where you sit versus competitors in the auction

Reports auction competitiveness, ad-quality factors that can be optimized, and overlap signals. Surfaces when audience fragmentation is hurting delivery.

Compare CTR/CPC/CVR against industry benchmarks

Aggregated benchmarks from similar advertisers in the same vertical. Focused on business-outcome metrics, not surface metrics.

Account-level marketing-funnel overview to pick the right optimization goal

Helps Claude pick the most relevant optimization goal and approach for a campaign based on your current funnel state.

Show the 5 underlying tools

ads_get_opportunity_score · ads_insights_anomaly_signal · ads_insights_auction_ranking_benchmarks · ads_insights_industry_benchmark · ads_insights_advertiser_context

Common questions

I'm a developer — does this work in Claude Code or via `claude mcp add`?

Yes in Claude Code, no via `claude mcp add`. Meta only allows a few AI products to connect directly, and the sign-in path in Claude.ai is on that list. Once you sign in via Claude.ai (or Claude Desktop with the same account), the tools become available in Claude Code automatically — no `claude mcp add` and no config file required.

Will this AI MCP get my Meta ad account banned?

No. The risk was specific to third-party automation MCPs that sit between you and Meta — operators reported account restrictions for using them. Here, authentication runs directly between you and Meta, no third party in the middle.

Pasquale Pillitteri — analyst breakdown of Meta's MCP versus third-party wrappers
Do I need a Meta Developer App or System User token?

No to both. The sign-in flow handles auth at the user level — the 5 Meta permissions (manage ads, read ads, manage catalog, manage business, read Pages list) auto-attach. Community wrappers need a Meta Business app + System User token + .env + Railway deploy; this needs one click.

Luke Moulton, LeadSync — 'No API setup. No developer credentials. No code.'
Is this really free?

Yes — free during the open beta launched 2026-04-29. Meta has not announced post-beta pricing. Getting started takes minutes, not days.

Meta launch announcement, 2026-04-29
What if my account doesn't see the Meta Ads connector yet?

Meta is rolling out access in phases — US and high-spend ad accounts first per the launch announcement. If 'Meta Ads' isn't visible in your Claude.ai connectors list, your account is not yet enabled; check back in 1-2 weeks or contact your Meta Business rep to request enablement.

Should I use this one or serkanhaslak/meta-mcp?

Use this one for diagnostics, performance audits, and zero-friction onboarding — especially the AI-native recommendations (opportunity score, anomaly signal, auction-rank benchmarks) that community wrappers don't expose. Use serkanhaslak for the longer tail — 77 tools including batch operations, automated rules, Lead Gen forms — if you have the time to self-host on Railway and want full surface area. Both work — some operators went back to community wrappers for one-click setup and autonomous overnight actions.

Yael S., Head of Performance — honest comparison
Can the MCP execute changes overnight without me in the chat?

No autonomous actions. Every prompt-driven action requires you to be in the conversation. For overnight automation, Meta's own Advantage+ campaigns and automated rules (configured in Ads Manager) handle the autonomous loop, or third-party stacks like Ryze layer agentic behavior on top.

Is my ad-spend data shared with Anthropic?

Your sign-in token lives on Anthropic's backend — that's how the connection propagates between Claude apps. When you invoke a tool, Anthropic relays the call to Meta and returns the response. Raw ad-spend data is relayed, not stored. ElasticFlow itself does not proxy or store any of it — the connection happens between your AI client, Anthropic, and Meta.

What's new

  • vopen-beta-launch29-04-2026

    Meta launches Ads AI Connectors with 29 tools — first Meta-hosted AI-tooling endpoint for the Marketing API. Hosted at mcp.facebook.com/ads. Open beta, free during beta period. Phased rollout starting with US and high-spend ad accounts.

  • vopen-beta-2026-05-2020-05-2026

    44 tools observed in production (+15 since launch — 52% growth in 3 weeks). New surfaces: 3 AI-native recommendation tools (opportunity_score, anomaly_signal, auction_ranking_benchmarks) not present in community wrappers. Federation path through claude.ai connector → Claude Code verified.