Facebook Ads MCP

What the Facebook Ads MCP can do

An MCP server gives your AI client a set of tools. Ad Uploader's tools cover the whole launch:

import_media pulls images and videos from Google Drive, Dropbox or direct links, up to 50 files at a time.
preview_launch shows every ad set, ad, budget and name before anything is created.
launch creates the ad sets and ads as one job, and get_job reports progress.
duplicate_ad_set copies targeting, budget and optimisation into a new paused ad set.
set_status pauses or activates a campaign, ad set or ad.
get_insights reports spend, CTR, CPC, ROAS, purchases and leads when you ask.

Connect with Facebook sign-in, no API keys

There's no developer app to register and no token to paste. In Claude, open Settings → Connectors → Add custom connector, name it "Ad Uploader" and paste the URL. Click Connect, then Continue with Facebook, then Allow.

It's Meta's own login screen, so we never see your password.

Made for launching, not just reading data

Many Facebook Ads MCP servers focus on reporting: they read campaigns and answer questions. That's useful, but the slow part of paid social is getting 40 new creatives live with the right names, placements and settings. This server is built for that job.

Safe for a live ad account

Everything is created paused, so nothing spends until you activate it.
Activating always needs an explicit yes in the chat.
Ad set budgets above your saved cap are refused until you raise the cap.
Errors from Meta come back in plain language.

Common questions

What is a Facebook Ads MCP server?

It's a connector that lets an AI client like Claude use Facebook Ads tools through the Model Context Protocol. You describe what you want in chat, and the client calls the tools.

Does it work on Claude's Free plan?

Yes. Claude's Free plan allows one custom connector, and Pro removes the limit.

Do I need a Meta developer account?

No. You sign in with Facebook and choose which access to allow.