Meta just did something big: it opened its ad accounts directly to Claude and ChatGPT. You no longer need Ads Manager to check metrics, nor a developer to read data via API. You ask for what you want in natural language and the AI operates your account. This is called Meta Ads AI Connectors and it has been in global open beta since April 2026.
What it is exactly
Meta Ads AI Connectors are two official pieces published by Meta:
- Ads MCP server — an MCP (Model Context Protocol) server managed by Meta. You add it to Claude or ChatGPT as a Connector and it gets plugged into your ad account. No tokens, no developer credentials, no code.
- Ads CLI — a command-line tool for those who prefer to operate from the terminal or automate with scripts.
This guide focuses on the MCP server because it is the one you will use if your preferred interface is a chat with Claude or ChatGPT.
Why it matters for your business
Before the Connectors, you had three options to operate Meta Ads with AI:
- Paste screenshots into the chat and have the AI “reason” over pixels. Slow and inaccurate.
- Connect via API yourself (Marketing API), generate system tokens and maintain them. Requires a developer.
- Pay a third-party MCP (Pipeboard, Ryze, Adzviser, etc.) that sits between Meta and your AI. It works, but there is an extra provider in the middle.
Meta’s official connector removes those three points: you authorize once with your Meta account, and from then on the AI operates with real data (not estimated, not sampled).
The right architecture — Claude never touches the platform
This is the part that 90% of YouTube tutorials skip and the reason many people end up with banned accounts: Claude should not touch the Ads Manager interface directly. No pasting your credentials into a tool that “automates clicks” in the browser. No scrapers reading your screen. That violates Meta’s terms and is a near-guaranteed ban.
The correct integration is the one set up by the official connector: Claude talks to Meta’s official Marketing API through the MCP server, authenticated with your verified Business Manager. Claude lives in your internal stack (chat, CRM, automations). Not in the feed.Any action it executes is recorded in Meta’s activity log as a legitimate API call, not as suspicious behavior.
What you can do once connected
The capabilities Meta confirms at launch:
- Create and edit campaigns, ad sets and ads with conversational prompts — including budgets, targeting, placements and creative.
- Reports and insights with real data from your account. The AI pulls figures directly, it does not model them.
- Catalog management — create catalogs, upload products and identify feed issues.
- Signal diagnostics — review the health of your pixel and CAPI for tracking and optimization.
- General troubleshooting — the AI can read the account state and propose fixes for delivery errors, ad rejections, etc.
Prerequisites
- A Facebook account with access to the ad account(s) you are going to manage (Business Manager or a personal account with assigned Ad Accounts).
- A role with management permissions over those accounts (Admin, Advertiser or equivalent). If you are only an Analyst, you can read but not create/edit.
- An AI client compatible with MCP. Today: Claude (web or desktop, Pro/Max/Team/Enterprise plan; Free allows 1 custom connector) and ChatGPT. More will join.
Setup in 4 steps
Add the custom connector in Claude
In Claude.ai, go to your account menu → Settings → Connectors. At the bottom of the list there is an “Add custom connector” button. Click it and paste the official URL of Meta’s MCP server:
https://mcp.facebook.com/adsClick “Add”. The connector appears in your list as “Meta ADs” with the CUSTOM label.
Click 'Connect' and authorize with Facebook
In the row of the connector you just added, click Connect. Claude takes you to the Facebook login. Sign in with the account that has access to your Ad Accounts.
Select the ad accounts to manage
After login, Facebook asks you to choose which ad accounts Claude will be able to read and operate. Check only the ones you want to connect — start with one to test and then scale.
Confirm. You return to Claude with the connector already authenticated and ready.
Activate it in your chat
Connectors in Claude are not activated globally. In each new conversation, click the “+” button at the bottom left → Connectors and turn on the toggle for Meta ADs for that session.
From there, you can ask it for reports, campaign edits, etc. Always start with something read-only to validate that it is properly plugged in.
Example prompts
Start with something read-only to validate that it is properly plugged in:
Summarize the last 14 days of performance for the account
[ACCOUNT NAME]:
- ROAS by campaign
- 3 ad sets whose CTR dropped the most
- Best ad by purchases
- A concrete recommendation to reallocate 10% of the budget
Return it as a table + a closing paragraph.Claude invokes the MCP tools, pulls the real data, and returns the table. If all goes well, you can move on to editing:
In the campaign "September — Bookings":
- Raise the daily budget of the ad set "Lookalike 2% women NJ"
from $30 to $45.
- Pause the ad set "Open broad" if its CPA exceeded $40 over
the last 7 days.
- Create a new version of the top ad with fresh copy
focused on urgency.
Before applying anything, tell me exactly what you are going to change
and wait for my confirmation.For any action that changesyour account (raise budget, pause, create), ask Claude to tell you exactly what it is going to do before executing. This avoids “error amplifiers” where the AI applies five changes and you notice one was wrong too late.
6 cases that will NOT get you banned
These are the 6 patterns we have seen work well with real clients without creating friction with Meta. They all follow the same rule: Claude suggests or reads, the human (or a controlled external system) decides and executes the sensitive part.
Ad copy — Claude drafts, you publish manually
You use Claude to generate headlines, primary text, descriptions and CTAs based on your ICP, tone and offer. The final publishing you do yourself in Ads Manager. Zero risk, maximum time savings on the creative side.
Campaign analysis — reading via the official API
You ask for reports and diagnostics. Claude queries the Marketing API through the MCP, pulls real data and returns actionable insights. It is read-only — it does not modify anything in your account.
Audience segmentation — suggests targets, does not touch Ads Manager
“Give me 5 candidate cold audiences for my product X in NJ”. Claude proposes interests, behaviors and lookalikes based on your data. You create the audience in Ads Manager with that proposal. No autonomous action on the account.
Automated reports — export to your internal CRM
Claude reads Meta metrics and pushes them to Notion, Google Sheets, your BI or your CRM. Stakeholders see the dashboard without needing access to Ads Manager. All the logic lives outside Meta.
Copy A/B testing — variants generated, human decides which goes live
You ask for 5 variants of the top performer, changing the hook, social proof and CTA. Claude prepares them. You review, pick 2 and upload them to a manual A/B test. The creative decision remains yours.
Lead follow-up — outside Meta, in your own system
You connect Meta Leads → CRM → Claude. When a lead comes in, Claude drafts a personalized follow-up message (email, WhatsApp, SMS) based on the campaign source and the lead data.The entire follow-up lives outside Meta, in your stack — Claude does not send messages from Facebook or Instagram directly.
What it does NOT solve (yet)
- Strategy. The connector executes what you ask. Strategy (offer, angles, scaling criteria) is still yours.
- Deep creative. It generates variants and copy, but the real video work or the actual shoot is still done by your team or dedicated tools.
- Cross-platform. Meta only. TikTok, Google and LinkedIn require their own MCPs (some already exist, others are on the way).
Security — what to do and what to avoid
Do
- Use only the official connector (
https://mcp.facebook.com/ads) or a recognized third-party MCP. Never tools that automate clicks in the browser. - Create a dedicated system user in Business Manager with permissions only to the necessary ad accounts. Do not use your global admin personal account.
- Ask for a preview before executing. For any action that changes campaigns, ask Claude to list what it is going to do and confirm manually.
- Review Meta’s activity log weekly during the first weeks. You will see every executed action with a timestamp and origin.
Do NOT
- Do not paste your Facebook password into any tool that is not facebook.com directly. The official MCP uses OAuth — it never asks for credentials in plain text.
- Do not use scrapers or “browser automation” to operate Ads Manager. That is a direct terms violation and Meta detects it quickly.
- Do not let Claude publish/edit without approval in production during the first month. Keep a human in the loop for any action that moves money until you trust its judgment.
- Do not send messages to leads from the Meta feed automatically. Follow-up lives in your CRM/email/WhatsApp, not in automated Instagram or Messenger messages.
If you want this operating in your business
Setting up the connector on your account is trivial. What is not trivial is building the flow: the well-assembled Project, the prompts that produce repeatable audits, the rules for when Claude executes on its own and when it asks for confirmation, and the integration with your internal reporting. That is what we do. The audit is free: in 30 min we look at your accounts and tell you what makes sense to automate first.