Meta Ads MCP
by Ads UploaderLet Your Agent Build the Campaign. You Press Create Ads.
Connect Claude, ChatGPT, or any MCP client to Ads Uploader, and your agent works directly on the campaign build you have open in the web app. It fills ad text from a launch sheet, arranges media into ad sets, and drafts copy, and your open uploader tab picks up every change in seconds. You proof everything in the interface you know, and Create Ads is still your click.
Every edit lands in the same build your uploader tab has open, within seconds
Describe what you want in plain language from Claude or ChatGPT, no terminal required
Proof the campaign in the web app and press Create Ads yourself
Paste the Launch Sheet. It Does the Rest.
Your client approves a sheet of creative file names, primary texts, headlines, and destinations, and someone has to move it all across without a mistake. Paste the rows into the chat and your agent keys every line to the right creative by file name, then writes it straight into your build.
- Headlines, primary texts, descriptions, CTAs, and destination URLs, patched per ad
- File names are the join key, so copy lands on the right creative every time
- Everything else in your build stays exactly as you configured it
- Ten ads filled in about a minute, with no cell-by-cell pasting
Claude · ads-uploader MCPWatch It Land in Your Open Tab
The MCP edits the same build your uploader tab has open. Make a change in chat, and the tab picks it up seconds later, with a banner and one-click apply if you were mid-edit. The Claude and ChatGPT buttons in Edit Text open a chat with your build reference already filled in.
- Your open uploader tab picks up agent edits automatically
- Mid-edit? A banner shows the external update and applies it in one click
- Claude and ChatGPT buttons in Edit Text hand over the build reference
- No export, no import, no sync step, it is one build
Arrange Ad Sets Exactly How You Want
Some launches don't fit a template. Tell your agent to put the three UGC videos in one ad set and the statics in another, five ads per ad set, named your way. Think of it as a campaign surgeon: precise structural work inside your build that would otherwise be a lot of clicking.
- Describe which media goes in which ad set, in plain language
- Auto-divide into ad sets of five, or a fully bespoke arrangement
- Per-ad-set text, naming patterns, and scheduling included
- It reaches the entire build, right down to enhancement toggles
Arranging your ad setsOr Let It Write the Ads
A launch sheet is one avenue, not the point. Your agent can work from whatever you give it: a connected Google Sheet, a PDF brief, or the creatives themselves. Show it your statics and it drafts headlines and primary text to match what is actually on screen, straight into the build.
- Draft copy from the creative, your landing page, or a brief
- Iterate in chat, shorter, harder CTA, more social proof, then save again
- Connect Google Sheets to your agent and skip pasting entirely
- Copy lands in the build, not in a doc you still have to transfer
ChatGPT · drafting copy from your creativesCreate Ads Is Still Your Click
This is the middle ground between clicking everything by hand and handing your ad account to a pipeline. The agent does the heavy lifting, you proof media, text, enhancements, and scheduling in the uploader, then press Create Ads yourself. The launch runs through the web app exactly as it always does.
- Proof the whole campaign in the interface you already trust
- Nothing goes to Meta until you press the button
- Want chat-driven launches too? ads_preview dry-runs and ads_create publishes
- AI speed without handing over end-to-end control
Web, MCP, and CLI. One Circuit.
Builds are the common thread. Start a campaign in the web app, patch it from chat, fork a variant, and finish it on whichever surface suits the job, the same build reference opens everywhere. For end-to-end agentic launches from a folder of files, our CLI is the stronger tool. The MCP shines when you are working with the web app.
- The same build opens in the web app, the CLI, and your agent
- Fork a build for a variant without touching the original
- CLI for file-native end-to-end launches, MCP for chat alongside the app
- Move a launch between surfaces mid-flight, nothing is locked in
Upload media, apply a preset, start the build
Connect Once, From Any Client
Add Ads Uploader as a custom connector in Claude or ChatGPT, sign in with your account, and 24 tools show up in your agent. Working in Claude Code or Cursor? Install the local server with npm and run ads login instead. Either way, your accounts, presets, and builds are already there.
- Custom connector for Claude and ChatGPT, sign in through your browser
- Local stdio server for Claude Code, Cursor, and any MCP client
- Same login as the web app, nothing new to manage
- Your accounts, presets, and saved builds carry over automatically
Ads Uploader MCP vs. Meta's Official Connector
In April 2026, Meta shipped its own AI connectors, an MCP endpoint that exposes Marketing API operations to AI clients. It hands you the raw API one object at a time.
Getting Connected
- •Authorize against Meta's Business login
- •Work directly against the raw Marketing API
- •Wire up each client to Meta's endpoint
- Install the server and run ads login once
- Drop in one config block, or use a connector URL
- Sign in through your browser, nothing to paste
Workflow and Guardrails
- •Raw API operations, one object at a time
- •No batch upload of a creative folder
- •No dry-run preview step
- •Creates live by default
- •Edge cases surface in production
- Upload, preview, and create as guided steps
- Whole creative folders in one call
- Dry-run preview before any spend
- Retries and readable errors built in
- Production-tested at scale
Reuse and Inheritance
- •Define every campaign field
- •Define every ad set field
- •Re-specify each launch from scratch
- Reference any existing ad to copy from
- Reuse presets and saved builds
- Override only what changed
- Builds shared across web, CLI, and MCP
Launching ads is all we do. We've shaped our tooling to be the best at it, tested against millions of dollars in ad spend on our own brands and businesses.
Chris Pollard Founder of Ads Uploader
A new connector is only as good as the workflow behind it. Meta's endpoint hands you the raw API, but format coverage, retry logic, valid configs, and inheriting from existing ads still land on you. We've spent years encoding all of that into the Ads Uploader workflow, and the MCP hands it straight to your agent.
MCP is the right interface for an agent the same way a visual UI is for clicks. Same marketers, different context. Meta shipping their own connector is welcome validation that this is where ad launching is headed.
The Agent Does the Typing. You Make the Call.
Connect Claude or ChatGPT and turn your next launch sheet into a finished build.
Start 7-Day Free TrialFree 7-day trial
•No credit card required
•Cancel anytime