Released April 29, 2026
Meta Ads AI Connectors — Official MCP + CLI Explained
Meta launched Meta Ads AI Connectors on April 29, 2026 — two interfaces (MCP + CLI) to the Marketing API, free during open beta. Here's what's included, what's not, and what to pair with it for cross-channel paid media work.
Used by paid media teams at
What Meta Ads AI Connectors actually are
On April 29, 2026, Meta opened its advertising ecosystem to third-party AI assistants. The result is Meta Ads AI Connectors — an umbrella product covering two interfaces:
- 1.MCP Server — hosted at
https://mcp.facebook.com/ads. Add as a custom connector in Claude Desktop, ChatGPT, or any MCP-compatible client, then sign in with Facebook Business. - 2.CLI — terminal binary installed via
npm install -g @meta/ads-cli. Designed for Claude Code and shell-driven workflows.
Both interfaces expose the same 29 tools across five capability areas: reporting and insights, campaign management, catalog operations, account diagnostics, and dataset operations. Both are read + write. Both authenticate via Meta Business OAuth — no Developer App registration, no app review wait, no tokens to copy or rotate.
The pricing? Free during open beta. Meta hasn't announced long-term pricing.
The 29 tools — what they cover
Reporting & insights
Performance data by campaign / ad set / ad. ROAS, CTR, CPM, frequency, conversion attribution by window.
Campaign management
Create, update, pause, duplicate campaigns / ad sets / ads. Budget changes. Status transitions.
Catalog operations
Product catalogs, feed rules, product sets, diagnostics. For DPA/Advantage+ Shopping campaigns.
Account diagnostics
Errors, opportunity scores, learning phase status, auction ranking benchmarks, industry benchmarks.
Dataset operations
Pixels, conversion events, custom audiences. Dataset quality and stats.
Auth model
Meta Business OAuth. Same login as Meta Ads Manager. No app review wait.
What Meta Ads AI Connectors don't cover
Five gaps that matter for full-stack paid media work — and where GoMarble's hosted MCP picks up.
Google, TikTok, LinkedIn, Bing
Meta-only. Cross-platform analyses require a separate connection per platform.
Competitor research
No access to the Meta Ad Library API for competitor brand discovery, ad analysis, or scaling-signal detection.
Shopify reconciliation
Can't compare Meta-reported ROAS against actual Shopify revenue.
Klaviyo + lifecycle
No connection to email or SMS — can't trace paid traffic to LTV cohorts.
GA4 + Search Console
No web analytics or organic data in the same prompt.
Scheduled jobs / dashboards
Conversational only. No automated Monday-morning briefs, no non-technical UI.
Pair with GoMarble's hosted MCP
The cleanest way to use Meta Ads AI Connectors is alongside GoMarble's hosted MCP. Both connect in Claude — Meta-only and free vs cross-platform and paid (see public tiers). Together they cover the full paid media surface: Meta's 29 tools for Meta-specific depth, GoMarble for everything else (Google + TikTok + LinkedIn + Bing + Shopify + Klaviyo + competitor research + scheduled jobs).
Setup is one custom connector in claude.ai/settings/integrations with URL https://apps.gomarble.ai/mcp-api/sse. Most GoMarble customers end up dropping the Meta connector after a few weeks because GoMarble already covers the Meta surface they actually use day-to-day.
Frequently asked
What are Meta Ads AI Connectors?
Are they free?
How many tools do they expose?
What's the difference between the MCP and the CLI?
What do they NOT cover?
Can I use Meta AI Connectors with GoMarble at the same time?
Meta’s connectors handle Meta. GoMarble handles everything else.
Add GoMarble's hosted MCP in Claude alongside Meta's. Get cross-platform context, competitor research, Shopify reconciliation, and scheduled reports in the same Claude session.