
November 16, 2026
Hook Claude to Meta Ads in 10 minutes, compare the 7 MCP servers, and sidestep the mistakes that get accounts banned.
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.
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.
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.
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.
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.
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.
https://mcp.facebook.com/ads. Claude detects an OAuth server and shows a Sign in with Meta button.ads_read and, if you want write access, ads_management. Confirm.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.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.
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.
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.
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.
mcp.facebook.com/ads or on a Meta Tech Partner platform such as AdKit.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 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 |
|---|---|---|
| Hosting | Remote, hosted by Meta | Local or self-hosted (Google Cloud Run) |
| Access | Read + write | Read-only |
| Setup | Add a connector, sign in | Cloud project, OAuth or service account, run your own server |
| Compatible clients | Claude Desktop, Claude Code, ChatGPT, Codex, Cursor, Perplexity | Any MCP client you configure |
| Blast radius | Campaign creation, budget spend | Read-only, zero writes |
| Required discipline | Dedicated Business Manager, drafts, rate-limit | Read 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.
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.
mcp.facebook.com/ads, in public beta since April 29, 2026.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.
Lorem ipsum
Can't find what you're looking for ? Contact us here
jordan@bulldozer-collective.comGet access to playbooks and feedback from those who are shaping the next wave of marketing and AI.
