META ADS · NEWS
Just Shipped3 ways to connect Meta Ads
to Claude or any AI assistant
How to connect Meta Ads with Claude (and other AI) in 3 clicks. Meta’s official MCP and CLI take ~30 min and a config-file edit; Ryze AI’s hosted connector takes one minute — no terminal, no JSON.
Contents
One-click Meta Connector
2 min, no CLI install
- ✓One-click Meta Business OAuth
- ✓Autonomous-agent layer included
- ✓Business Manager auto-discovery
Two ways to connect Meta MCP to Claude, side-by-side. Manual setup is six steps and around 30 minutes — install the local bridge, copy your API key, edit Claude Desktop’s config, restart. Ryze AI’s hosted connector is three clicks and around one minute, no config edit required.
What Meta actually shipped
Skip the press-release language — here’s what you can now do that you couldn’t do last week. Open Claude (or ChatGPT). Type, in plain English, things like:
- ✓“Show me my top 10 ad sets by spend last 7 days, with frequency and ROAS.”
- ✓“Pause every ad set with frequency over 4 and CPM trending up.”
- ✓“Bump my best-performing campaign’s budget by 20% but cap at $500/day.”
- ✓“Audit my product catalog — flag SKUs with broken images or missing GTINs.”
All of that runs through Meta’s standard Business OAuth — the same one Shopify and Mailchimp use. The big change for marketers: no Meta Developer App, no marketing API approval wait. You can be querying live campaigns within minutes instead of the old 1-3 day wait.
Meta shipped two flavors of this same capability:
- →Meta Ads MCP server — HTTP-based, paste a URL into Claude Desktop or ChatGPT. This is the one most marketers want.
- →Meta CLI — local terminal binary for Claude Code or Codex. This is for developers. If you’ve never opened a terminal, skip it.
There’s also a quieter outcome of this launch worth noting: the long-running worry that “using AI to manage Meta Ads gets your account banned” is now formally retired. This is Meta’s officially blessed automation path. For the wider field of third-party MCPs that existed before this launch, see Best MCP for Meta Ads in 2026.
1,000+ Marketers Use Ryze
Automating hundreds of agencies
★★★★★4.9/5
MCP or CLI — which one is for you?
Same Meta Marketing API underneath. Different way of getting at it. The 10-second answer: if you use Claude Desktop or ChatGPT, you want the MCP. If you live in a terminal with Claude Code, you want the CLI. Most marketers want the MCP. Here’s the side-by-side.
Meta Ads MCP server · Most marketers
For Claude Desktop & ChatGPT
Hosted by Meta. You paste one URL into Claude Desktop’s config and restart. No CLI install. If you don’t know what a terminal is, this is your row.
Best for
- ✓Marketers using Claude Desktop or ChatGPT
- ✓Anyone who edits a config file once and never again
- ✓Solo operators not running multi-account agencies
Setup time
~10 min · paste URL + restart Claude
Meta Ads CLI · Developers only
For Claude Code & Codex
A binary you install on your laptop and run from a terminal. Built for developers writing custom AI agents in Claude Code or Codex. Skip this row if you don’t already use those tools daily.
Best for
- ✓Engineers using Claude Code or OpenAI Codex
- ✓Teams building bespoke automation on top of Meta’s API
- ✓Anyone comfortable running shell commands
Setup time
~15 min · npm install + env vars + auth
Screenshot — the Meta Ads CLI running in a terminal session, ready for Claude Code / Codex.
Installing Meta’s official MCP in Claude Desktop
Three steps, following Meta’s setup docs at facebook.com/business/help/1456422242197840. Honest summary: it works, but you’ll edit a JSON config file and restart Claude. Plan on ~10 minutes the first time, including hunting for where Claude Desktop stores its config. (Or skip the JSON edit entirely — Ryze AI’s one-click connector is at the bottom of the article and takes 2.)
Screenshot — Meta’s official MCP connected to Claude Desktop, with creative-fatigue audit returning a Markdown table.
Step 01 · ~2 min
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 or Mailchimp. Approve the requested scopes (ad accounts, campaign management, signal access). Meta provisions a unique MCP URL for your Business account on the next screen — copy it.
Step 02 · ~6 min (the hard one)
Edit Claude Desktop’s JSON config and restart
Open Claude Desktop → Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default editor. Add the block below (replace <your-business-id>). Save, fully quit Claude (cmd-Q on Mac, not just close window), and reopen. Green “connected” indicator appears within a few seconds. If it doesn’t, your JSON has a syntax error — that’s the most common 5-minute time-sink here.
Step 03 · ~2 min
Run your first prompt
Ask Claude any question about your Meta Ads account in plain English. The MCP exposes campaign listing, ad-set inspection, budget updates, catalog management, and signal diagnostics. Try the prompt below as a smoke test — it confirms read access works and gives you a useful weekly snapshot.
Expected: a Markdown table with 10 rows. If you get an error, recheck your JSON config — trailing commas are the most common culprit.
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
23
Countries
Side-by-side: which path wins on which thing
Six things that actually matter when you’re running real ad budgets. Setup time, whether you have to touch a CLI or config file, multi-account handling for agencies, and what you get done while you sleep. The orange row is the marketer/agency pick.
| Path | Setup time | No CLI / config edit | Agent layer | Multi-account | White-label | Pricing |
|---|---|---|---|---|---|---|
| Ryze AI (one-click) | ~2 min | Yes — pure browser | Yes (24/7) | BM auto-discovery | Built-in | Free trial → spend-based |
| Meta Official MCP | ~10 min | No — JSON config edit | No | Manual switch | DIY | Free (open beta) |
| Meta Official CLI | ~15 min | No — CLI install + auth | No | Manual switch | DIY | Free (open beta) |
| Pivix mads-mcp (legacy) | 25-45 min + Meta App | No — self-host + config | No | Per-account config | DIY | Free + dev time |
Comparison reflects Meta’s open-beta launch on April 29, 2026. Setup times are wall-clock estimates from a fresh laptop — including hunting for Claude Desktop’s config path on first install.
Which one is for you?
Two clean personas cover ~95% of readers. If you’re in a third bucket (scientist, hobbyist, edge case), the side-by-side above has what you need.
✓ Where Meta’s official wins
- ✓Free during open beta — zero subscription
- ✓Officially supported by Meta — no rate-limit or ban risk
- ✓Deepest raw Marketing API surface (it’s Meta’s own)
- ✓No Developer App approval wait
× Where Meta’s official falls short
- ×You edit a JSON config file or install a CLI — no browser-only path
- ×No autonomous agent — tells you ad sets are fatigued, doesn’t pause them
- ×No multi-account auto-discovery — agencies switch by hand
- ×No per-client token isolation — a hard fail for regulated agency work
→ If you’re a developer — pick Meta’s official
- →You’re comfortable editing JSON and restarting Claude
- →You want raw Marketing API access for custom tooling or scripts
- →You’ll wire your own automation (cron jobs, alerts, pause logic)
- →You manage 1-2 accounts — multi-tenancy isn’t your problem
★ If you’re a marketer or agency — pick Ryze
- ★You want to be running queries inside Claude in 2 minutes, not 10
- ★You want fatigued ad sets paused overnight, not just flagged in a report
- ★You manage 5+ Meta accounts and need BM auto-discovery + token isolation
- ★You want white-label client portals to ship reports without engineering
The 2-minute path: Ryze AI’s one-click Meta connector
Three steps. Each one has a concrete outcome so you can tell when it worked. Genuinely one click on the OAuth screen. No Meta CLI install. No JSON config to edit beyond pasting one URL into Claude Desktop.
Screenshot — Ryze AI’s one-click Meta connector running creative-fatigue audit + agent pause inside Claude.
Step 01 · ~30 sec
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 pops up — the same one Shopify uses. One click on Continue. If you have multiple ad accounts under your Business Manager, Ryze auto-discovers them; pick the ones you want to wire up.
Outcome: you land on the Ryze dashboard with your ad accounts listed and a unique MCP URL ready to copy.
Step 02 · ~1 min
Paste MCP URL into Claude Desktop
In your Ryze dashboard, click Copy MCP URL. In Claude Desktop → Settings → Developer → Edit Config, add the block below under mcpServers. Save, fully quit Claude (cmd-Q), reopen. The Ryze tools register automatically — including those for Google Ads, GA4, and any other connectors you’ve enabled.
Outcome: Claude shows a green “ryze-meta-ads” indicator. You can now ask Claude anything about your Meta Ads in plain English.
Step 03 · ~30 sec
Try the agent layer Meta’s official doesn’t have
Type the prompt below into Claude. Ryze’s agent identifies fatigued ad sets across your accounts, drafts pause recommendations, and — with your approval — applies them within per-account guardrails. This is the active automation layer; Meta’s official MCP would just describe the problem in a table.
Outcome: a Markdown table of fatigued ad sets with proposed pauses, total spend impact, and an approval prompt. Click approve and Ryze executes the pauses on Meta. (You can also flip on schedule mode so this runs every night without you.)
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
11
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. As of April 30, 2026, Meta hasn’t committed to long-term pricing — the “free” tag is open-beta-specific and may change.
Q: If Meta’s MCP is free, why pay for Ryze?
Because Meta’s MCP only describes problems — it doesn’t fix them. Ryze adds the autonomous-agent layer that pauses fatigued ad sets while you sleep, plus multi-account auto-discovery, per-client token isolation, and white-label reporting that agencies need. If you’re a solo operator running one account and don’t want automation, Meta’s free MCP is enough. If you’re trying to give back hours each week, Ryze pays for itself in the first ad set it pauses.
Q: Will my agency clients’ data leak between accounts on Ryze?
No. Every Ryze client account gets its own isolated OAuth token; the agent layer can only see and act on the accounts you explicitly wired to that workspace. There’s no shared infrastructure that touches more than one client’s ad data at a time. Meta’s official MCP doesn’t ship per-client isolation — you’d have to build that yourself if you went that route for an agency.
Q: Can my whole team use Ryze on one account?
Yes. Ryze workspaces support unlimited team seats by default — everyone gets their own login, role-based permissions, and audit trail. The agent layer respects per-user spending caps so a junior media buyer can’t accidentally move a $50k budget. White-label client portals are also included if you want clients to see read-only dashboards without Ryze branding.
Q: I’ve never used Claude or AI — is this too much to learn?
No. You type questions in plain English (“show me yesterday’s top ad sets”) and Claude responds with tables, charts, or proposed actions. There’s no syntax to memorize, no formulas, no scripting. If you can write a Slack message to a colleague, you can use this. Ryze ships with a library of starter prompts so you’re productive on day one.
Q: Can I use Meta’s official MCP and Ryze at the same time?
Technically yes, but not recommended. Claude’s tool-selection accuracy drops when overlapping MCPs expose similar tool names — it won’t know whether to call Meta’s native list_campaigns or Ryze’s. Pick one primary. Most teams pick Ryze for the one-click setup + agent layer, and only add Meta’s MCP if they need raw Marketing API access for a one-off edge case.
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
2,000+
Marketers
$500M+
Ad spend
23
Countries
