Free Guide

How to Connect Claude to Meta Ads Without Getting Banned

The official MCP server is here. Paste one URL into Claude and run your account from chat.

Connecting Claude is the first 60 seconds. The prompt library, audit workflow, and weekly classroom drops live inside AI Ads with Roman.

Tools covered

Claude Meta Ads MCP Meta Ads CLI

The official Meta Ads MCP server and CLI are here. That means you can fully manage your accounts with AI without getting banned. The MCP is the fastest path. Paste one URL into Claude and you can talk to your account.

Pick your path

Three options. Find yours and skip to the one you need.

If you live in an AI chat

Meta Ads MCP

Works in Claude Desktop, Claude Code, Cowork, ChatGPT, and Perplexity
Zero code, no developer app
Read and write to ads, campaigns, and catalogs (paused by default)
MCP-only: Signal Diagnostics, Help Center search, catalog troubleshooting

If you live in a terminal

Meta Ads CLI

Same core coverage as the MCP
Runs unattended in cron and CI/CD
JSON, table, and plain output for piping
System-token auth + standard exit codes

If you need CAPI, offline, webhooks, or local geo

Raw Marketing API

Full Marketing API surface
Required for CAPI, offline conversions, webhooks
Required for accurate city/ZIP/radius targeting
Highest setup burden: app, tokens, glue

Connect the MCP in 60 seconds

Five steps. The MCP works the same way in any MCP-aware client.

Open Claude and add a custom connector

Click + in any chat, or go to Customize → Connectors. Then click Add custom connector. Free Claude users only get one custom connector total, so make sure your slot is open.

Paste the Meta MCP URL

Paste https://mcp.facebook.com/ads and click Add.

Sign into Meta and pick your ad account

Authorize through Business OAuth. Pick the ad account you want connected. Read the requested permissions before you approve. You can revoke access in your Meta Business settings any time.

Toggle the connector on in your chat

Open the + menu in your chat, find Meta under Connectors, and toggle it on.

Try a first prompt

Now you can talk to your account in plain English. Try one of these:

"Pull last 7 days of spend, CTR, and CPA by ad set."
"Find my worst-performing ad set in the last 14 days and tell me what to do."
"Draft a new campaign with a $50/day budget. Don't launch it."

Anything you create defaults to PAUSED, so confirm in Ads Manager before flipping it live.

Want to run this from your terminal or in scripts? The Meta Ads CLI is a separate setup (Python install, system user, scoped token). Start with Meta's official CLI getting-started guide.

Watch out for

Free Claude plans cap you at one custom connector total. If you have already used your slot for something else, the Meta MCP will not fit until you remove the existing one or upgrade.

On Team and Enterprise plans, only Owners can add the connector. Members will not see Meta in the connector list until an Owner adds it at the org level.

Custom connectors are still in beta. Tool behavior, OAuth scopes, and permissions can change.

"Allow always" hands the agent autonomous access. Per-action approval is the default safety. If you click Allow always, that tool fires without asking. Read each scope first.

Start here

Open Claude. Hit + in any chat → Add custom connector. Paste https://mcp.facebook.com/ads. Sign into Meta. Toggle it on. Sixty seconds and you are in.

FAQ

Will using the Meta MCP server get my ad account banned?

No. The MCP server is the official Meta-built integration. The accounts that were getting flagged before this were running janky scripts against the Marketing API the wrong way. The MCP is the sanctioned path.

What is the difference between the MCP and the CLI?

The MCP is a remote connector you paste into any MCP-aware AI agent (Claude Desktop, Claude Code, Cowork, ChatGPT, Perplexity). Zero code. Best for chatting with your account. The CLI is a Python tool you install in your terminal. Best for scripts, cron jobs, and CI/CD. Three tools are MCP-only and not in the CLI: Signal Diagnostics (read your Pixel and CAPI signal health and get investment recommendations), Help Center search (the agent searches Meta's official docs inside the chat), and catalog troubleshooting (diagnose feed errors and item visibility for DPA / commerce accounts).

Do I need a developer app or app review to use the Meta MCP?

No. The MCP uses Business OAuth or a token link. No developer app required. The CLI may need a developer app for system-token automation. The raw Marketing API requires a full developer app and tokens.

Can I use the Meta MCP on the free Claude plan?

Yes, but the free plan caps you at one custom connector total. If you have used your one slot, the Meta MCP will not fit until you remove the existing one or upgrade.

Can the Meta MCP send Conversions API events or upload offline conversions?

No. CAPI server events, offline conversions, and webhooks are not in the MCP or CLI tool sets. Use the raw Marketing API for those.

Can I use the Meta MCP for local business targeting (city, ZIP, radius)?

Verify before you trust it. The current public CLI docs show country-level targeting for ad set creation, and the MCP is similar. The underlying Marketing API supports city, ZIP, and radius targeting. Draft paused with the MCP, then patch targeting in Ads Manager or use the raw API before going live.