Meta Ads MCP: Official Server, Alternatives, and a Real Test

Hook Claude to Meta Ads in 10 minutes, compare the 7 MCP servers, and sidestep the mistakes that get accounts banned.

Table of contents

You run Meta Ads and you want an AI agent to pilot the account without burning it down. The Meta Ads MCP server, hosted by Meta at mcp.facebook.com/ads and opened in public beta on April 29, 2026, hooks Claude Desktop, Claude Code, ChatGPT, Codex, Cursor, or Perplexity directly into your Business Manager, with read and write access. It covers most reporting and campaign management jobs, and it sits next to six third-party alternatives with very different guardrails.

This guide compares the seven Meta Ads MCP servers live in November 2026, shows the official hookup step by step, lists six prompts a B2B lead-gen team actually uses, and names the mistakes that get ad accounts banned. We write from an agency that pilots B2B paid media with Claude on more than twenty Business Managers in parallel.

The 7 Meta Ads MCP servers in November 2026

Seven servers expose a Meta Ads account to an AI agent today: Meta's official server, the open-source brijr/meta-mcp repository, AdKit, Ryze AI, Superads, Pipeboard, and the Zapier Facebook Lead Ads connector. No page in the top SERP compares more than three, and every one except PPC.io is pitching its own. We read them side by side on 2026-11-12.

Server Hosting Read / Write Price Best fit Ban risk
Meta official (mcp.facebook.com/ads) Remote, hosted by Meta Read + write (new ads start paused) Free, public beta In-house teams and agencies that want full control Low: official server, configurable guardrails
brijr/meta-mcp You, on Cloudflare Workers Read + write, 39 tools Free, self-hosted Dev teams that want to own the stack Medium: Meta app shared across users
AdKit (mcp.adkit.so) Remote, hosted by AdKit Read + write, drafts mandatory $29 to $49 per month Multi-platform approvals across Meta, Google, TikTok, LinkedIn, X, Reddit, Microsoft, Pinterest, ChatGPT Ads Low: Meta Tech Partner, drafts, rate limiting
Ryze AI Remote, hosted by Ryze Read + write with autonomous agent Paid, pricing not public Agencies with many clients and white-label reporting Medium: active agent, broad permissions
Superads Remote, hosted by Superads Read-only Paid Reporting and creative analytics with zero write risk None: no write path
Pipeboard Remote, third-party SaaS Read + write, details unverified Not public Niche third-party option, thinly documented Unknown: scope not audited by Meta
Zapier Facebook Lead Ads Remote, hosted by Zapier Reads leads in real time Zapier freemium Lead capture and CRM routing Low: scope limited to lead gen

Dated reads: StoreHero for the official server and the Meta vs Google side-by-side (storehero.ai/meta-ads-mcp/), the GitHub README for brijr/meta-mcp and its 39 tools, the AdKit product page for pricing and the platform list, PPC.io for the three-route framing (ppc.io/blog/facebook-ads-mcp), Superads for ban vectors.

What the Meta Ads MCP server is

The Meta Ads MCP server is a remote endpoint hosted by Meta at mcp.facebook.com/ads that lets an AI agent query and operate a Meta Ads account in natural language. It exposes seven tool categories behind a Meta Business OAuth login, from performance reporting to Business Help Center lookups. Meta opened it in public beta on April 29, 2026, with no fee announced.

The protocol underneath, the Model Context Protocol, standardizes the conversation between an AI client and an external data source. In this case, the source is your ad account, surfaced through the Meta Marketing API. The agent sends a structured request, the server returns data or executes an action, inside an active OAuth session.

Scopes come in two flavors: ads_read for reporting, ads_management for writes, picked at sign-in. You can expose a read-only server to an analyst and a read-write server to a senior media buyer on the same ad account, with different sessions.

What the official server actually does

The official server exposes seven tool categories behind OAuth scopes, from performance reporting to the Business Help Center. Each category maps to a family of actions Claude can trigger, with an in-chat approval required for every call.

  • Performance reporting: spend, impressions, clicks, CTR, CPC, conversions, ROAS, broken out by campaign, ad set, ad, period, and segmentation.
  • Campaign management: create and edit campaigns, ad sets, and ads. New ads default to paused status.
  • Custom audiences and catalogs: read and update product sets, lookalike audiences, and retargeting audiences.
  • Signals and datasets: pixel health, standard events, server-side conversion matching.
  • A/B tests and conversion lift: launch and read budget tests, creative tests, and incrementality studies.
  • Activity log: auditable history of every action taken through the MCP and by whom.
  • Business Help Center: documentation queries, useful to resolve an error or check an ad-policy rule.

Guardrails live in Meta Business Suite, under Settings > Integrations > Ads MCP server. You pick the ad account exposed and block sensitive actions, such as campaign creation or budget increases above a cap. Every call needs in-chat approval before it runs.

How to hook Claude Desktop to the official server

The hookup takes four steps and about ten minutes the first time: turn on the connector in Claude Desktop, point it at mcp.facebook.com/ads, sign in with Meta Business, run a test prompt. The claude_desktop_config.json file only matters if you do a manual install to pin a specific Business Manager.

  1. Add the connector in Claude Desktop. Open Settings, go to Connectors, click Add custom connector, paste https://mcp.facebook.com/ads. Claude detects an OAuth server and shows a Sign in with Meta button.
  2. Approve the Meta Business login. You land in a Meta OAuth window. Pick the Business Manager, then the ad account, then the scopes: ads_read and, if you want write access, ads_management. Confirm.
  3. Check the local config (optional). On a manual install, claude_desktop_config.json must include an mcpServers block with the server URL and the Business Manager id. A trailing comma in the JSON blocks Claude from starting: lint the file before you restart.
  4. Run a test prompt. Ask something like "Show spend, leads, and CPL by campaign for the last 14 days." Claude should return a structured table, not a prose summary. If you get vague prose, the connector is misconfigured.

For the workflow layer sitting on top, see our reference on Claude Skills for B2B paid, which describes the skills we wire behind the MCP to standardize audits, creative briefs, and weekly reporting.

Prompts that return useful answers

A useful prompt gives the agent a scope, a metric, a period, and a threshold, with no interpretation: the model extracts, it does not decide. Six prompts tested on B2B lead-gen accounts, three for analysis and three for pilot moves.

Analysis

  1. "Return a table of spend, leads, CPL, CTR by campaign for the last 30 days, sorted by CPL ascending. Show every campaign, including the ones with zero conversions."
  2. "List ad sets with frequency above 3.5 over the last 7 days and CPL variation greater than +20% over the same period. Include the active creative for each."
  3. "For every ad launched within the last 14 days, return hook rate (video 3s views / impressions) and hold rate (video thruplays / video 3s views). Flag any ad replacing a previous one."

Pilot

  1. "Draft a change that pauses ad sets with CPL above $160 and frequency above 4. Do not push live; return the list and the modification JSON."
  2. "Reallocate 20% of the budget from the three campaigns with the highest CPL to the three with the lowest CPL, capped at $500 per day per campaign. Draft only."
  3. "Draft a lookalike campaign built from MQL leads of the last 90 days exported from the CRM, with $100 per day budget, advantage+ placements, video creative I will provide, paused status."

These prompts hold up because they pin a scope, a period, and a metric. Any vague ask such as "optimize my campaigns" lets the agent invent tactics and you lose control. The Bulldozer Meta Ads cheat sheet documents the B2B lead-gen metrics and thresholds that feed these prompts.

Real risks and how to defuse them

Three ban vectors hit Meta accounts in 2026: rate-limit violations behind the Meta 613 error, unofficial MCP servers that share a common Meta app, and AI-generated ads published without the required label since March 2026. All three are avoidable with five rules.

  1. Official server in production, nothing else. Third-party MCP servers that authenticate through a shared Meta app expose your account to a collective flag. On a production ad account, stay on mcp.facebook.com/ads or on a Meta Tech Partner platform such as AdKit.
  2. Drafts every time. Every write lands as a paused entity or a draft. The official server already defaults new ads to paused; set the same caps in Settings > Integrations > Ads MCP server.
  3. Dedicated Business Manager for AI. Isolate the ad account exposed to Claude in a Business Manager separate from your production Business Manager. You can revoke access in two clicks if a session drifts, without affecting humans.
  4. Rate limits respected. Superads recommends capping consecutive mutations at 5 and backing off at 75% of the usage limit. An agent pushing 30 budget changes per hour triggers the 613 error and an automatic flag.
  5. AI Content Label on every AI-touched ad. Since March 2026, Meta requires the AI Content Label on ads generated or modified by AI. Undisclosed AI content reportedly drives roughly 14% of ad rejections in 2026 (reported by Superads, not confirmed by Meta).

The activity log lists every action the MCP took: read it weekly on accounts where you granted write access. An anomaly shows up there before a Meta flag lands on the account.

Meta Ads MCP vs Google Ads MCP

Meta Ads MCP is read-write and hosted by Meta at mcp.facebook.com/ads; Google Ads MCP is read-only and runs locally on your machine or on Google Cloud Run. The blast radius changes the discipline around it: Google cannot break anything, Meta can spend a budget.

Criterion Meta Ads MCP Google Ads MCP
HostingRemote, hosted by MetaLocal or self-hosted (Google Cloud Run)
AccessRead + writeRead-only
SetupAdd a connector, sign inCloud project, OAuth or service account, run your own server
Compatible clientsClaude Desktop, Claude Code, ChatGPT, Codex, Cursor, PerplexityAny MCP client you configure
Blast radiusCampaign creation, budget spendRead-only, zero writes
Required disciplineDedicated Business Manager, drafts, rate-limitRead scope is enough on its own

For a third angle on an MCP connector that doesn't touch ad spend, see our breakdown of LinkedIn MCP servers and how to install them.

What a US agency setup looks like

A US agency that pilots Meta Ads for ten or more clients wires the MCP once per Business Manager, not once per ad account. The agency's AI Business Manager carries read-only access via ads_read to each client Business Manager, through a seat granted by the client. Write access, when needed, lives on a client-specific Business Manager where a single ad account is exposed, with guardrails set in Business Suite.

Claude pulls the monthly audit, flags the ad sets to pause, and returns draft reallocations. A media buyer reviews, tweaks two creatives, pushes live. Loop duration drops from about two hours of manual exports and pivots to roughly twenty minutes. The Bulldozer Paid Social offer runs this discipline across Meta Ads and other paid channels.

The prompt we use most: "For the last 30 days, return for every active ad set the spend, MQL lead count (CRM `mql_flag` column), MQL CPL, CTR, and frequency. Sort by MQL CPL ascending. Flag ad sets with frequency above 4 and MQL CPL variation of +20% or more. Return the raw table, no prose summary." Claude replies in three to four seconds with the full table and a status column marked cut, watch, or scale. A media buyer validates and hits publish on the drafts that survive the review.

What does not get delegated: offer strategy, creative hooks, and the CRM-side signal reading. An agent reads a CPL; it doesn't know if the MQL became qualified pipeline. That measurement lives in your revenue team, not in your MCP.

Key takeaways

  • The Meta Ads MCP server is free, hosted at mcp.facebook.com/ads, in public beta since April 29, 2026.
  • Seven MCP servers expose a Meta Ads account in November 2026; six are third-party, only one is official.
  • The official hookup takes four steps and about ten minutes the first time, through Meta Business OAuth.
  • The three active ban vectors are rate-limit violations (613 error), unofficial MCP servers, and AI creative without the label required since March 2026.
  • The choice turns on write scope (read-only vs read-write) and the discipline you are willing to enforce around it.

An MCP server does not override ad-policy rules or the structure of a well-built ad account: it accelerates what you already know how to do. Want this setup live on your campaigns without eating a month of onboarding? Talk to the Bulldozer Paid Social team.

Rich Text Attributes - Do not delete
This container will be hidden on the live page

Lorem ipsum

Book a demo
Jordan Chenevier-Truchet
Jordan Chenevier-Truchet
CEO
Last update
November 16, 2026

Co-founder and CEO of Bulldozer, he writes about B2B growth strategy and go-to-market.

Read more from this author

See more

To go further

Meta Ads MCP: Official Server, Alternatives, and a Real Test
November 16, 2026
AI & Marketing Automation
Jordan Chenevier-Truchet
Meta Ads MCP: Official Server, Alternatives, and a Real Test
AI Marketing: How to Transform Your B2B Strategy (Without Losing Control)
December 26, 2025
AI & Marketing Automation
Killian Drecq
AI Marketing: How to Transform Your B2B Strategy (Without Losing Control)
LinkedIn MCP: which server to pick and how to install it in 2026
November 10, 2026
AI & Marketing Automation
Jordan Chenevier-Truchet
LinkedIn MCP: which server to pick and how to install it in 2026

Frequently asked questions

Can't find what you're looking for ? Contact us here

jordan@bulldozer-collective.com
Is the Meta Ads MCP server free?
Yes. Meta opened it in public beta on April 29, 2026, with no fee announced. The only costs are your Claude, ChatGPT, or Cursor subscription and the ad spend on the Meta Ads account you expose. Access to the official server at `mcp.facebook.com/ads` does not add a line to your Meta Business invoice.
Can Claude spend my budget without my approval through the MCP?
Not with read-only scope (`ads_read`). With the `ads_management` scope, any new campaign the agent creates lands in `paused` status by default, but the agent can launch it in the same session if it holds that right. Guardrails sit in Meta Business Suite under `Settings > Integrations > Ads MCP server`.
Can I connect multiple ad accounts to the same MCP server?
Yes. The OAuth flow runs through a Meta Business Manager: every ad account linked to that Business Manager is exposed to Claude, within the scopes you granted. To isolate a single client, create a Business Manager dedicated to AI access or narrow the account selection at sign-in.
What is the difference between Meta Ads MCP and Google Ads MCP?
Google Ads MCP is read-only and runs locally on your machine or on Google Cloud Run. Meta Ads MCP is read-write and runs on Meta's own servers. Google cannot break an ad account; Meta can create campaigns, change budgets, and launch ad sets, so the discipline around it is not the same.
Are third-party MCPs (brijr, AdKit, Ryze) as safe as the official one?
Not for unvetted third parties. Unofficial MCP servers were a ban vector in 2026, especially when they authenticate through a Meta app shared across users or exceed rate limits. AdKit is a Meta Tech Partner and routes every write through drafts, which lowers the risk. `brijr/meta-mcp` is open source on Cloudflare Workers, to use with eyes open.
Does the MCP replace Meta Ads Manager?
No. The MCP cuts repetitive work (reporting, drafts, audits) and speeds up analysis. It does not replace strategic decisions (positioning, offer, creative) or the human QA that happens before publication. An agent reads a CPL; it does not know if that MQL became qualified pipeline in your CRM.
Newsletter

Join those who are redefining AI-driven growth.

Get access to playbooks and feedback from those who are shaping the next wave of marketing and AI.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Let’s grow!

From first pipeline to sustained growth
Leo Lacoste
Léo Lacoste
business partner