AI Agent for Meta Ads That Can Make Changes

An MCP server turns an ad platform's API into typed tools an AI assistant can call. Connect one to Claude or ChatGPT and "pause every ad set with a cost per purchase above $60 this week" becomes something the assistant can check, propose, and, once you approve, run. This page covers PaidSync's Meta surface in full. What the tools do, how writes are checked, what the server deliberately does not do, how it compares with Meta's own ads MCP, and how to connect it to each AI client.

It is written for both halves of that audience. Marketers who want to run Meta Ads from a chat window, and agent builders who want to know exactly what the protocol surface looks like before wiring it into a workflow. Each section is labeled.

How PaidSync.ai keeps you in control

• Preview first. Meta create tools run as a dry run by default and change nothing until a second, explicit call.
• New campaigns start paused. A new Meta campaign is created paused unless the request says otherwise.
• Approval before each change. In the PaidSync.ai workspace, every change waits as an approval card until a person approves it. From Claude or ChatGPT, your assistant's own approval setting decides whether it asks first.
• A confirm for risky moves. Pauses and deletions refuse to run without an explicit confirm, and a Meta campaign budget change of more than 50 percent needs a second one.
• A change log. Each live change is recorded with the user, the ad account, the tool and a before-and-after outcome.
• Your access stays yours. PaidSync.ai never asks for a Facebook password. Tokens are encrypted at rest with AES-256-GCM, and disconnecting deletes them.

Every control, and what is not built yet, is on the security page.

What an AI agent for Meta Ads does

Three things, in practice. It reads, so the assistant can pull spend, results, cost per result, and breakdowns by placement, device, age, gender, country, and time without you exporting from Ads Manager. It writes, so campaigns, ad sets, ads, creatives, audiences, pixels, lead forms, budget schedules, and automated rules can be created or changed from conversation. And it gates, so writes preview as a dry run by default and destructive changes need an explicit confirm.

Reading is table stakes across every Meta Ads MCP available in 2026, including Meta's own. The depth of the write surface, whether the server works on your account today, whether it also sees the rest of your stack, and how honest the gating is are where they differ. Those four points are the spine of this page.

Meta's Marketing API is object-heavy. A single ad is a campaign, an ad set, a creative, and an ad object, each with its own status, budget, and targeting fields. A useful Meta MCP has to model all four layers as tools, not just the campaign layer, or the assistant ends up able to read a problem it cannot fix. PaidSync's set covers all four, plus the objects around them.

Why PaidSync.ai instead of the official connector

Meta runs its own ads MCP server. Meta's developer documentation, checked on 16 October 2026, describes it as "a Meta-hosted Model Context Protocol server that lets you manage Meta ads directly from an AI agent", gives the address https://mcp.facebook.com/ads, and says it "works with any MCP-compatible AI agent". If you only advertise on Meta, start there.

PaidSync.ai fits when Meta is one of several channels. What you can check:

• Meta plus 13 more platforms in one connection. Meta tools that read and make changes, inside a server with 630+ tools across 14 platforms, so your assistant can put Meta next to Google Ads, LinkedIn, Microsoft Ads, TikTok and GA4 in one answer.
• It builds and changes. Campaigns, ad sets, ads, creatives and audiences, plus budgets and status on what already runs.
• Checks before changes. Meta writes run as a dry-run preview by default, and destructive changes need an explicit confirmation.
• No developer setup. You sign in to PaidSync.ai and connect Meta on Meta's own Facebook sign-in screen. There is no API key and no Meta developer app to create.
• Price. PaidSync.ai is free for 15 tasks a month with no credit card and no time limit. Pro is $99 a month for 600 tasks, or $75 a month billed yearly, and Team is $249 a month for 5 seats and 6,000 shared tasks (pricing).

Using Meta's Muse agent? You can connect Google Ads, LinkedIn and TikTok to Meta Muse through PaidSync.ai. Full head-to-head: PaidSync.ai vs Meta's ads MCP.

Using Claude? See how to connect Meta Ads to Claude, step by step.

Every Meta Ads tool, by category

PaidSync.ai's live server exposes the Meta tools below, by category (server total 630+ across 14 platforms). 46 of them read, 34 write, and 3 handle the connection itself. Five of the writes build from scratch. The table below names every tool by category, so the count is checkable. The same catalog is discoverable live from any session via paidsync_context with the Meta group selected, described in the agent-builder section.

Four groups carry most of the operational weight. Creative production is the one Meta advertisers ask about first. upload_fb_ad_image and upload_fb_ad_video put media into the account, validate_fb_ad_assets checks image accessibility, Page access, the Instagram link, and placement compatibility before anything is published, create_fb_creative assembles single-image, single-video, and carousel creatives, and create_fb_dco_ad builds a dynamic creative ad set where Meta tests every combination of bodies, titles, and images. Audiences go the full distance, from a customer list upload through upload_customer_list_to_fb_audience to a lookalike built on top of it, and the four search tools let the assistant find interest, behaviour, location, and demographic IDs instead of guessing. Pixels and lead forms mean the measurement and the lead capture live in the same session as the campaigns. configure_fb_pixel sets up the pixel, get_fb_pixel_events shows what it is receiving, and create_fb_lead_form builds an instant form that attaches to an ad. Reporting has eight breakdowns and a trend tool, and get_delivery_issues lists every ad and ad set with a delivery problem, with Meta's error code and message, before you go looking.

The five build tools are create_fb_campaign, create_fb_adset, create_fb_ad, create_fb_creative, and create_fb_dco_ad. That is the full campaign object chain, so an assistant can go from "nothing" to a live ad without a single Ads Manager click. It still cannot switch that ad on without you, which is the next section.

One detail worth knowing. create_fb_campaign discloses Meta's own bid strategy default when you set a campaign budget and leave the strategy blank, and it sends that default explicitly so the applied value is visible in the result. Small, but it is the kind of thing a hosted server should do for you and a raw API call does not.

Run Meta Ads from a chat window

The practical shape of a week on PaidSync's Meta stack looks like three kinds of prompt. A report prompt, a build prompt, and a cleanup prompt. Here is one of each, with the tools that run underneath.

"Show me the last 7 days by campaign, then by placement, and tell me which ad sets are pacing under budget." The assistant calls get_fb_performance for the campaign view, get_fb_performance_by_placement to split Instagram Reels from Facebook Feed, and get_fb_budget_pacing for the ad sets that are behind. Three reads, no confirmation needed, one answer in plain numbers.

"Duplicate the Spring Sale campaign for the UK, point the ad set at a 1% lookalike of last quarter's buyers, and keep everything paused." The assistant proposes duplicate_fb_campaign, then create_fb_lookalike_audience from your existing purchasers audience, then update_fb_adset with the new audience and UK geography. Each write shows up as a preview first, because the Meta create, update, and pause tools default to dry_run true. You approve each one. The campaign lands paused because create_fb_campaign creates campaigns paused unless the request asks for them live.

"Find every ad whose CTR fell by half since launch and pause it." get_fb_ad_performance and get_performance_trend find the candidates, the assistant lists them with the numbers, and pause_fb_ad runs once per ad after you confirm the list. If you want this to run every Monday without asking, create_fb_automated_rule hands the schedule to Meta and the rule shows up in Ads Manager like any other.

Because the same server carries Google Ads (158 tools), LinkedIn (34), TikTok (24), GA4 (26), GTM (39), Search Console (6, read only), and Merchant Center (16), the follow-up "did the Meta budget shift move GA4 purchases, and is Google Shopping now overspending on the same products" is answered in the same session, not in another tab. That cross-platform session is the practical difference between a Meta connector and a paid-media server. For prompt ideas, 15 Meta Ads prompts for Claude is a working list, and the Meta Ads audit guide shows the deeper account-review workflow.

Trust is the honest concern with write access, and the answer is procedural, not promissory. Previews show the exact planned change first. Destructive operations need a second, explicit step. Over MCP, PaidSync writes no card, so the human check is your assistant's own confirmation prompt. In the PaidSync workspace every write is an approval card by default, and an applied card offers Undo when the change has a safe inverse, so a change you regret on Thursday can often be undone. On both paths an applied change is logged, on a best-effort basis, with a 7-day before and after. If you would rather have a specialist watch the account for you, the workspace ships a Creative Fatigue Watcher, a Budget Pacer, a ROAS Guardian, and a Wasted Spend Hunter that run on the same gated tools.

The protocol surface behind the tools

PaidSync is one MCP endpoint covering 14 platforms, https://mcp.paidsync.ai/mcp, over Streamable HTTP. Details on the MCP server page. Authentication is OAuth 2.0 with dynamic client registration and PKCE, so a client that speaks the current MCP authorization flow signs in with the PaidSync login and never sees a long-lived token. An API key also works, sent in an Authorization: Bearer or x-api-key header. Never put the key in a URL; query strings end up in logs. Applying a change to Google Ads still requires the OAuth sign-in. On Meta Ads and the other platforms a key can apply changes too, so treat it like a password and prefer OAuth.

To keep client context small, tools/list returns a lean starter set. The full catalog is discovered at runtime through paidsync_context, which returns the active ad account, connected platforms, and the grouped tool catalog, and executed through paidsync_exec. That two-call pattern means an agent can enumerate and invoke every Meta tool without a 630+-tool schema payload sitting in every conversation. Account context is explicit. list_fb_ad_accounts walks the accounts the Meta login can see, set_fb_ad_account binds one, and every Meta call after that carries the bound account, so an agent working across a Business Manager with several ad accounts never guesses which one it is writing to.

The server-side checks run whatever the client. The Meta create, update, and pause tools carry a dry_run argument that defaults to true, so a naive agent that forgets to preview still gets a preview. Destructive operations require confirm_destructive. The approval step itself sits in the client: over MCP, PaidSync writes no card. Sessions can be revoked at any time, and platform tokens are encrypted at rest with AES-256-GCM. Repeatable work can be saved as a workflow with paidsync_workflows_save and run with paidsync_workflows_run; workflows are TypeScript compositions of the same tools, so they carry the same dry-run and confirm checks.

For discovery and verification, the domain publishes OAuth authorization-server and protected-resource metadata (RFC 8414 and RFC 9728), an MCP server card, agent-auth.json, security.txt, and a Content-Signal directive, so an agent can establish what this server is and how to authenticate against it before the first task. The Meta bulk operations reference documents the argument shapes for the write tools.

What this does not do

Stated plainly, because scoping a tool accurately beats overselling it.

• One object per call. Each create or update acts on one campaign, ad set, ad, or audience. A change across forty ad sets is forty approved tasks or one create_fb_automated_rule that Meta runs on a schedule. Spreadsheet-style bulk import is not the shape of this tool set.
• Advantage+ creative enhancements are not exposed. Advantage+ audience expansion is a parameter on the ad set tools, on by default. The automatic text, music, and template enhancements Meta applies to creatives are not switches in create_fb_creative.
• Catalogs are read, not built. list_fb_catalogs and get_fb_catalog show what is there. Catalog sales campaigns and collection creatives are not created by this tool set. Product and feed writes live on the Merchant Center side of the server, for Google.
• No organic. No posting, no Page management, no comment moderation. This is an ads server.
• No approval card over MCP. In the PaidSync workspace every write waits as an approval card by default, and autonomy is opt-in per agent, inside budget guardrails you set. When your own assistant calls PaidSync over MCP, the human check is that assistant's confirmation prompt, so keep it on for write tools. A Meta automated rule you create through PaidSync is then Meta's rule, visible and editable in Ads Manager.

Connect it to your AI client

The server URL is the same everywhere, https://mcp.paidsync.ai/mcp, and the transport is Streamable HTTP everywhere. What differs is where each client hides the "add a server" screen. The summaries below are taken from PaidSync's client setup registry, verified in September 2026. Each Meta guide walks the full flow with screenshots.

Prefer an API key? A client that lets you set a header, such as Claude Code, can send it to the same URL as Authorization: Bearer ps_... or x-api-key. Never put the key in a URL; query strings end up in logs. Applying a change to Google Ads still requires the OAuth sign-in. On Meta Ads and the other platforms a key can apply changes too, so treat it like a password and prefer OAuth. GitHub Copilot in VS Code is a different product from Microsoft 365 Copilot; there, run MCP: Add Server, choose HTTP, paste the same URL, and sign in when prompted.

Pricing

Every plan includes all 14 platforms and every ad account you connect; there is no per-account or per-platform charge. Every tool call counts as one task, whether it reads a report or drafts a change. A dry-run preview and the live write are two tasks. Full detail at paidsync.ai/pricing.

Connect Meta Ads to your AI

One setup per client, same endpoint and sign-in everywhere.

• Meta Ads to Claude
• Meta Ads to Claude Code
• Meta Ads to ChatGPT
• Meta Ads to Gemini
• Meta Ads to Microsoft Copilot Studio
• Meta Ads to Perplexity
• Meta Ads to Cursor
• Meta Ads to Codex

Frequently asked questions