META ADS · NEWS

Just Shipped

Meta’s Official MCP + CLI Just Shipped
What It Means for Claude Users

On April 29, 2026, Meta opened the beta of two new artifacts: an official Meta Ads MCP server for Claude Desktop / ChatGPT, and a Meta CLI for terminal agents like Claude Code and Codex. Auth is Meta Business OAuth — no Meta Developer App, no marketing API approval wait. Below: what shipped, how to install both, and how they compare to Ryze AI’s one-click hosted Meta connector that already does this without the CLI install.

Ira Bodnar·April 30, 2026·Updated Apr 30, 2026·9 min read

Contents

One-click Meta Connector

2 min, no CLI install

✓One-click Meta Business OAuth
✓Autonomous-agent layer included
✓Business Manager auto-discovery

Process diagram — 3 paths to connect Claude to Meta Ads after Meta's April 29, 2026 launch: Meta Ads MCP server, Meta CLI, or Ryze AI one-click hosted connector

The 3 ways to connect Claude to Meta Ads as of April 30, 2026 — Meta’s official MCP, Meta’s official CLI, or Ryze AI’s one-click hosted connector.

What Meta just shipped

On April 29, 2026, Meta announced the open beta of its Meta Ads AI connectors — a pair of officially-supported integrations that let advertisers “create, manage, and analyze campaigns directly in the AI tools they already use.” Two distinct artifacts shipped:

→Meta Ads MCP server — HTTP-based, for Claude Desktop / ChatGPT and any standards-compliant MCP client.
→Meta CLI — local terminal binary, for Claude Code, OpenAI Codex, and other terminal-based AI agents.
→Same underlying Meta Marketing API; two different transports. Pick by where you actually use Claude.

The headline change for marketers: no Meta Developer App, no marketing API approval wait. Authentication is the standard Meta Business OAuth (same flow Shopify or Mailchimp use), and the official MCP/CLI ship full read + write access:

✓Query campaigns, ad sets, and ads with natural language
✓Create new campaigns and update budgets directly from Claude
✓Manage product catalogs and run signal diagnostics
✓Connector live in minutes — no 1-3 day Developer App review

Meta is also using the launch to retire a persistent misconception. As Thomas Eccel noted in his launch coverage, the worry that “using AI gets your Meta Ads banned” is now formally over — this is the legitimate, Meta-blessed automation path. Digiday framed it as Meta “opening its ad ecosystem to third-party AI tools.” For the broader 7-MCP comparison written before this launch, see Best MCP for Meta Ads in 2026.

1,000+ Marketers Use Ryze

Automating hundreds of agencies

★★★★★4.9/5

Meta CLI vs Meta MCP — which one do you want?

The two artifacts target different AI surfaces. Same Meta Marketing API underneath; different transport. Pick by where you actually use Claude.

Meta Ads MCP server

For HTTP MCP clients

HTTP MCP server you connect to from Claude Desktop, ChatGPT, or any standards-compliant MCP client. No local install — you paste a URL into your client config.

Best for

✓Claude Desktop users
✓ChatGPT desktop / web users
✓Marketers who don’t live in a terminal

Install

paste URL into Claude config

Meta Ads CLI

For terminal AI agents

Local terminal binary that exposes Meta Ads operations to terminal-based AI agents — Claude Code and OpenAI Codex. Install via package manager, authorize via Meta Business OAuth.

Best for

✓Claude Code users
✓OpenAI Codex users
✓Engineers building custom agents

Install

npm install -g @meta/ads-cli

Screenshot — the Meta Ads CLI running in a terminal session, ready for Claude Code / Codex.

Skip the install entirely — Ryze AI’s hosted Meta connector takes 2 minutes via a single OAuth click and works across Claude Desktop, Claude Code, and ChatGPT from one URL. Plus the autonomous-agent layer Meta’s official MCP doesn’t include — creative-fatigue auditing, ad-set pausing, and creative refresh that run 24/7 within your guardrails.

How to install Meta’s official MCP in Claude Desktop

Three steps following Meta’s setup docs at facebook.com/business/help/1456422242197840. Honest summary: works as advertised, takes about 5-7 minutes the first time.

Meta Ads official MCP server connected and active in Claude Desktop — query campaigns, audit creative fatigue, pause ad sets through Claude

Screenshot — Meta’s official MCP connected to Claude Desktop, with creative-fatigue audit returning a Markdown table.

Step 01

Authenticate via Meta Business OAuth

Visit Meta’s AI connectors page and click “Connect to AI tool.” You’ll see the standard Meta Business OAuth screen — same flow that powers Shopify, Mailchimp, or any Meta-connected app. Approve the requested scopes (ad accounts, campaign management, signal access) and Meta provisions an MCP URL for you.

Step 02

Add the MCP URL to Claude Desktop

Copy the unique MCP URL Meta provisions for your Business account. Open Claude Desktop → Settings → MCP Servers → paste the URL. Restart Claude. You’ll see the green “connected” indicator within seconds.

claude_desktop_config.json{ "mcpServers": { "meta-ads-official": { "url": "https://mcp.meta.com/ads/<your-business-id>" } } }

Step 03

Run your first prompt

Ask Claude any question about your Meta Ads account. The MCP exposes campaign listing, ad-set inspection, budget updates, catalog management, and signal diagnostics — all callable from natural language.

First promptShow me my top 10 ad sets by spend last 7 days, with frequency, ROAS, and creative-fatigue trend.

Or skip all of this

Connect Meta to Claude in 2 minutes — one click, no CLI install

✓One-click Meta Business OAuth
✓Autonomous-agent layer pauses fatigued ad sets
✓Business Manager auto-discovery for agencies

2,000+

Marketers

$500M+

Ad spend

Countries

Side-by-side: Meta’s official offering vs Ryze AI vs the legacy paths

Where Meta’s official MCP and CLI shine, where they don’t, and where Ryze AI’s one-click connector + agent layer covers the gap.

Path	Setup	Hosted	Agent layer	BM auto-discovery	White-label	Pricing
Ryze AI (one-click)	2 min OAuth	Yes	Yes (24/7)	Native	Built-in	Free trial → spend-based
Meta Official MCP	5-7 min	Yes (Meta)	No	Manual	DIY	Free (open beta)
Meta Official CLI	10-15 min	Local install	No	Manual	DIY	Free (open beta)
Pivix mads-mcp (legacy)	25-45 min + Meta App	Self-host	No	Per-account config	DIY	Free + dev time

Comparison reflects Meta’s open-beta launch on April 29, 2026. Setup times are independently measured wall-clock estimates from a fresh laptop.

Should you switch from third-party MCPs to Meta’s official one?

✓ What it does well

✓Free during open beta
✓Officially supported — no rate-limit / ban risk
✓Deepest Marketing API surface (it’s Meta’s own)
✓5-7 min setup — no Developer App approval wait

× What it doesn’t include

×No autonomous-agent layer — describes problems, doesn’t fix them
×No Business Manager auto-discovery for multi-account
×No per-client token isolation (hard fail for regulated industries)
×No white-label client reporting

→ Who should switch to Meta’s official MCP

→Solo developers who want raw Marketing API access
→Engineering teams building internal Claude tools
→Anyone previously self-hosting Pivix mads-mcp — collapses the 1-3 day approval wait to zero

★ Who should stay on Ryze AI

★Non-developer marketers who want zero setup friction
★DTC teams who need the agent pausing fatigued ad sets overnight
★Agencies running 5+ Meta clients (BM auto-discovery + isolation)
★Anyone who wants creative-fatigue auditing or white-label reports

For the agency-specific cut, see Best MCP for Meta Ads — Top 5 Picks for Agencies.

Quickstart: Ryze AI’s one-click Meta connector

Three steps. Genuinely one click on the OAuth screen. No Meta CLI install, no JSON config edit beyond pasting one URL.

Ryze AI one-click Meta connector — autonomous Facebook and Instagram campaign management running inside Claude with creative-fatigue audit and ad-set pause within guardrails

Screenshot — Ryze AI’s one-click Meta connector running creative-fatigue audit + agent pause inside Claude.

Step 01

Sign up + one-click Meta OAuth

Visit get-ryze.ai, click “Start free trial” (no card), click “Connect Meta Ads.” Standard Meta Business OAuth screen. One click on Continue. Done.

Step 02

Paste MCP URL into Claude Desktop

Copy the unique MCP URL from your Ryze dashboard. Paste into Claude Desktop config under mcpServers. Restart Claude.

claude_desktop_config.json{ "mcpServers": { "ryze-meta-ads": { "url": "https://mcp.get-ryze.ai/meta-ads/<your-id>" } } }

Step 03

Try the agent layer Meta’s official MCP doesn’t have

Type the prompt below. Ryze’s agent identifies fatigued ad sets, drafts pause recommendations, and (with your approval) applies them within per-account guardrails — the layer the official MCP doesn’t include.

First promptAudit creative fatigue across my Meta Ads account. Pause ad sets with frequency > 4 and rising CPM, within my $500/day change cap.

Yael S.

Head of Performance

DTC apparel, $180K/mo Meta spend

★★★★★

“

The day Meta’s official MCP launched I tested both within an hour. The official one works — props to Meta. But I went straight back to Ryze for two reasons: the one-click OAuth (their setup is six clicks and a config edit), and the agent that paused 11 fatigued ad sets overnight while I slept. Meta’s MCP would have just told me about them.”

2 min

Ryze setup

Ad sets paused overnight

$2,800

/mo wasted spend caught

Frequently asked questions

Q: Is Meta’s official MCP free?

Yes during open beta. The MCP and CLI install free, you still pay your normal Meta Ads spend. Pricing terms could change after open beta — Meta hasn’t committed long-term. As of April 30, 2026, no fee announced.

Q: Do I need to install Meta’s CLI to use Claude with Meta Ads?

No. CLI is only for terminal agents (Claude Code, Codex). For Claude Desktop / ChatGPT, the MCP is HTTP — just paste the URL. To skip install on either path entirely, Ryze AI’s one-click connector covers both surfaces from a single OAuth.

Q: What’s the difference between Meta CLI and Meta MCP?

Same Meta Marketing API; different transport. MCP is HTTP for Claude Desktop / ChatGPT clients. CLI is a local binary for Claude Code / Codex terminal agents. Pick by where you actually use Claude.

Q: Does the Meta CLI work with Codex and Claude Code?

Yes — Meta’s CLI was built specifically for terminal AI agents. It plugs into Claude Code’s skill / hook system and into OpenAI Codex’s tool registration. Authorize via Meta Business OAuth, the agent picks it up.

Q: Can I use Meta’s official MCP and Ryze AI at the same time?

Technically yes, not recommended. Claude’s tool-selection accuracy drops with overlapping MCPs. Pick one primary — most users pick Ryze for one-click + the agent layer, only adding Meta’s MCP if they need raw API for an edge case.

Q: Why use Ryze AI’s one-click connector instead of Meta’s official MCP?

Three reasons. One-click OAuth (no CLI install, no config edit). Autonomous-agent layer that pauses fatigued ad sets (Meta’s MCP describes problems but doesn’t fix). Agency-grade features Meta doesn’t ship: Business Manager auto-discovery, per-client token isolation, white-label client portals.

Skip the CLI

Connect Meta to Claude in one click via Ryze AI

✓Skip the install — one-click OAuth
✓Agent pauses fatigued ad sets while you sleep
✓Business Manager auto-discovery for agencies