Meta Ads MCP Server with Full Write Access

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 83 tools do, how the approval gate works, 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.

What a Meta Ads MCP server 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 nothing the AI proposes runs until a human confirms it.

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.

All 83 Meta Ads tools by category

PaidSync's live server exposes 83 Meta tools (server total 500+ 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 you said so, not because the tool decided.

"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 (149 tools), LinkedIn (34), TikTok (13), 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. Nothing applies without your confirmation. Previews show the exact planned change first. Destructive operations need a second, explicit step. Approval cards carry one-tap undo and a 7-day outcome check, so a change you regret on Thursday is reversible and a change you approved on Monday reports back on what it did. 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 83 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 for read-only use as https://mcp.paidsync.ai/mcp?api_key=ps_your_key_here. Applying a change requires the OAuth sign-in, by design.

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 all 83 Meta tools without a 500+-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.

Safety is enforced server-side, not left to the client. Every write is held for approval. 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. 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 inherit the same approval gate.

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.

Meta's official ads MCP, compared honestly

Meta runs its own ads MCP server at mcp.facebook.com/ads. It went into open beta on April 29, 2026, and it reads and writes, which puts it alongside TikTok's official Ads MCP as one of the two first-party ads servers that can change an account, not just report on it. Two facts matter before you rely on it. Access is gated per ad account with an is_ads_mcp_enabled flag, and US and higher-spend accounts were enabled first. Accounts outside the rollout get an error rather than a waitlist. On July 16, 2026 Meta added developer-app connections and server rules, which is the point at which agencies with their own Meta developer app could route through it. Meta's documentation lives at developers.facebook.com, and our walkthrough of setup, tool coverage, and guardrails is Meta's official ads MCP, a practical guide.

Meta's server is a good product for a Meta-only advertiser whose account is in the rollout. It is first party, it needs no third-party trust decision, and there was no separate charge for it in beta. The honest comparison is about scope, not quality. PaidSync's Meta surface sits inside a server that also runs 13 other platforms, it works on any ad account you can authorise today, every write is held for approval, and a question that spans Meta, Google, and GA4 is answered in one prompt. The table uses Meta's public documentation and our own registry as of September 2026. Full head-to-head at PaidSync vs Meta MCP.

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.
• Nothing spends without a human decision. Every write waits for your confirmation. Autonomy is opt-in per agent, inside budget guardrails you set, and can be switched off at any time. 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 for read-only reports? Use https://mcp.paidsync.ai/mcp?api_key=ps_your_key_here as the URL in any of these clients. Applying a change still requires the OAuth sign-in. 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 approved 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 (full guide)
• Meta Ads to ChatGPT (full guide)
• Meta Ads to Gemini (full guide)
• Meta Ads to Microsoft Copilot (full guide)
• Meta Ads to Perplexity (full guide)
• Facebook Ads to Claude
• Instagram Ads to Microsoft Copilot

Frequently asked questions