Meta quietly shipped something significant at the end of April 2026: an official MCP (Model Context Protocol) server for Meta Ads. What that means in plain English — you can now connect Claude or ChatGPT directly to your ad account and have a conversation with it. Not to get advice about your ads, but to actually run actions on them.
Instead of clicking through Ads Manager for an hour to pull a performance report, find underperforming ad sets, or create a new campaign — you type what you want in plain English and it happens. This is a meaningful shift for anyone running Meta ads, and it takes about five minutes to set up.
Meta Ads MCP is currently in open beta. Things may change. It has write access to your account — meaning it can create and modify campaigns — but every action requires your explicit confirmation before it executes. Nothing happens behind your back.
What You Can Actually Do From a Chat Window
Before getting into setup, it's worth being specific about what this unlocks. This isn't a chatbot that tells you what to do — it's a direct connection that does it for you:
What You'll Need Before You Start
- A Facebook account with admin access to your Meta Business Portfolio
- An active Meta ad account inside that portfolio
- Either a Claude account (Pro, Max, Team, or Enterprise) or a ChatGPT account (Plus, Pro, Business, or Enterprise)
- About five minutes
Note: Claude Free works but is limited to one custom connector. ChatGPT Free does not support custom connectors at all — you'll need at least the Plus plan.
Step 1 — Get the MCP URL
There's nothing to download or install. Meta's MCP is a remote server they host. Your AI tool connects to it over the internet using a single URL. Copy this:
That's the only technical piece. Everything else is just clicking through settings in your AI tool of choice.
Step 2A — Setup in Claude (2 Minutes)
1. Open Claude Settings
- 01Click your profile picture in the bottom-left corner of Claude
- 02Select Settings → Connectors
2. Add the Custom Connector
- 01Scroll to the bottom of the Connectors list
- 02Click Add custom connector
- 03Name it Meta Ads and paste the URL:
https://mcp.facebook.com/ads - 04Click Add
3. Connect Your Meta Account
- 01Click Connect next to Meta Ads in the list
- 02A Facebook OAuth window opens — log in
- 03Pick the Business Portfolio and ad accounts you want Claude to access
- 04Approve. You'll see a green Connected badge when done
4. Turn It On in Your Chat
- 01Open a new chat in Claude
- 02Click the + button → Connectors
- 03Toggle Meta Ads on
- 04Start prompting
Only Owners can add custom connectors to the organisation. Once the owner adds it, each member connects individually with their own Facebook login. No shared credentials — each person's access is scoped to what their Facebook account can see.
Step 2B — Setup in ChatGPT (4 Minutes)
ChatGPT needs one extra step — enabling Developer Mode — before it can use custom connectors.
1. Turn On Developer Mode
- 01Open chatgpt.com and click your profile picture → Settings
- 02Go to Connectors
- 03Scroll down and click Advanced settings
- 04Toggle Developer mode on. Read and accept the warning
2. Create the Connector
- 01Back in Settings → Connectors, click Add custom connector
- 02Name: Meta Ads
- 03Server URL:
https://mcp.facebook.com/ads - 04Authentication: OAuth
- 05Click Create. The connector saves as a draft
3. Authenticate
- 01Allow popups for chatgpt.com — or the OAuth window won't open
- 02Log into Facebook with your admin account
- 03Pick the ad accounts you want to connect
- 04Approve the permissions
4. Turn It On in Your Chat
- 01Open a new chat
- 02Click + → hover More → toggle Developer Mode on
- 03Select Meta Ads from the tools menu
First: ChatGPT auto-disables memory when Developer Mode is on — that's normal, it protects your other chats from the connector. Second: you have to be explicit in your prompts. Say "Use the Meta Ads MCP to..." or ChatGPT might ignore the connector entirely.
Your First Prompts — Start Here
Start with read-only actions to confirm the connection is working, then move to the more powerful stuff. These are copy-paste ready:
Why This Actually Matters for Your Brand
The value here isn't novelty — it's time. The average consumer brand owner or media buyer spends 3–5 hours per week inside Ads Manager doing things that are now conversational: pulling reports, cross-referencing performance, spotting outliers, building campaign structures. That time compresses dramatically when you can describe what you want in plain English and get back a structured answer with the data already pulled.
The audit prompt above — the one that finds frequency-fatigued ad sets, low-CTR ads, and budget-burning campaigns — would take 20–30 minutes to run manually inside Ads Manager. As a prompt, it takes 30 seconds and returns a prioritised fix list.
The more interesting use is the Pixel health check. Most consumer brands have attribution gaps they don't know about — events firing incorrectly, event match quality scores quietly declining — that directly affect how well Meta's algorithm can find buyers. Getting a clear signal quality report used to require navigating several different sections of Events Manager. Now it's one prompt.
One important thing to keep in mind: the connector has write access, but it doesn't act without your confirmation. Every campaign it creates starts paused. Every change it proposes appears in the chat before it executes. You're still in control — you're just spending less time doing the manual parts.
This is early-stage infrastructure, and it will get more capable quickly. Setting it up now means you're building familiarity with the workflow before it becomes standard practice.