Meta's Official Ads MCP, a Practical Guide

Q: What is Meta's official Ads MCP?

Meta's official Ads MCP is a hosted Model Context Protocol server at mcp.facebook.com/ads, released in open beta on April 29, 2026 as part of Meta's Ads AI Connectors. It gives AI assistants like Claude 29 tools for Meta ads work: campaign management, account and Page reads, product catalog management, dataset quality checks, and insights. It authenticates with Meta Business OAuth and needs no developer app.

Q: How do I connect Meta's Ads MCP to Claude?

In Claude, open Settings, then Connectors, and add https://mcp.facebook.com/ads as a remote MCP server. Complete the Meta Business OAuth dialog, pick your ad account, and choose a scope tier (read-only, read and write, or read, write and financial). Test with a read request such as last week's campaign performance. Writes require the ads_management scope. Most practitioners report 5 to 15 minutes from start to first query.

Q: Can Meta's official Ads MCP create and edit campaigns?

Yes. The official MCP is write-capable when you grant a write scope. The safety posture matters: every campaign, ad set, or ad an AI creates lands in paused status by default, and a human must activate it. Edits to already-live entities, like budget changes, take effect immediately with no draft mode, so grant write scopes deliberately.

Q: Does Meta's Ads MCP cover Google Ads or other ad platforms?

No. It covers Meta only: Facebook and Instagram ads plus Meta product catalogs. Google ships a separate open-source Google Ads API MCP server (announced October 7, 2025, read-only at launch). Running a cross-platform account list through official servers means juggling one connector per platform with no shared reporting layer. A multi-platform server like PaidSync covers 13 platforms through one endpoint, including 69 Meta tools.

Published August 1, 2026 by Ahmed Ashraf · Founder, PaidSync.ai

Facts checked against live sources, August 1, 2026

Meta's official Ads MCP went live in open beta on April 29, 2026 at mcp.facebook.com/ads. It exposes 29 tools behind Meta Business OAuth, it can write, and every campaign an AI creates lands paused until a human switches it on. This guide covers setup in Claude, what the 29 tools do, where the single-platform boundary sits, and how a multi-platform server like PaidSync, with 69 Meta tools inside a 430+ tool catalog across 13 platforms, fits alongside it.

One honesty note up front. PaidSync is a third-party competitor to parts of this product. Where the official server is the better pick, this guide says so.

What Meta Shipped on April 29, 2026

Meta released the Ads AI Connectors in open beta on April 29, 2026: a hosted MCP server at mcp.facebook.com/ads plus a CLI for developers. No developer app, no long-lived tokens to store or rotate. Authentication runs through a Meta Business OAuth dialog with three scope tiers, read-only, read and write, and read, write and financial, granted per user and per ad account. Details are in Meta's official Ads AI Connectors documentation, with a good independent teardown at mcp.directory.

This is a real shift. Meta historically kept Marketing API access behind app review, which pushed agencies toward Ads Manager or unofficial connectors. The official server removes that friction for Meta-only work.

Setup in Claude in About Ten Minutes

The flow below is for Claude. Cursor uses mcp.json, and other clients follow the same remote-server pattern. Steps per AdAdvisor's setup walkthrough, checked August 1, 2026.

Open Claude Settings, then Connectors.
Add https://mcp.facebook.com/ads as a remote MCP server.
Complete the Meta Business OAuth dialog and select your ad account.
Pick a scope tier. Start read-only. You can re-authorize with write scopes later.
Test with a read: ask for campaign performance over the last 7 days.
For writes, confirm the ads_management scope was actually granted.

Practitioner estimates put the whole thing at 5 to 15 minutes. If the server errors with is_ads_mcp_enabled: false, your account is not in the rollout yet. More on that below.

What the 29 Tools Cover

The 29 tools group into five buckets. The split, per the mcp.directory teardown:

Category	Tools	What you can do
Campaign management	5	Create and update campaigns, ad sets, ads. Activate entities.
Accounts and Pages	3	Retrieve ad accounts, entities, business Pages.
Product catalog	10	Feeds, products, product sets, catalog diagnostics.
Dataset quality	4	Feed and signal health, error tracking.
Insights	7	Performance trends, benchmarks, anomaly detection, opportunity scoring.

Read the split for a minute and the design intent shows. Ten of 29 tools are product catalog. Four more are dataset quality. Meta built this heavily for commerce advertisers, feed health, catalog hygiene, and signal diagnostics, with campaign management as a smaller slice. If your Meta problem is a broken feed or a product set that will not populate, the official server is genuinely strong.

Paused by Default and Other Guardrails

The write posture is the most interesting design choice, and Meta got it right.

Creations land paused. Every campaign, ad set, or ad an AI creates arrives in paused status. A human must activate it. Even the CLI's --no-input and --force flags do not override this.
Writes need explicit scope. Budget changes and pauses require the ads_management grant. Read-only sessions cannot mutate anything.
But live edits are immediate. Updates to entities that are already running, a budget raise on an active campaign for example, take effect right away. There is no draft mode for edits. Grant write scopes deliberately.
Rate limits apply. Standard Marketing API throttling is in force.
Reporting lags. Attribution and conversion numbers settle over hours to days, same as Ads Manager. Do not let an agent react to an hour-old dip.

One boundary worth naming: the connectors expose Marketing API operations, not Meta's bidding internals or Advantage+ optimization logic. As mcp.directory put it, this is "plumbing, not a new brain."

PaidSync runs Meta writes the same careful way. Dry-run previews, a confirm step on destructive calls, and 69 Meta tools including bulk operations. Free tier, 15 calls a month, no card.

Get started for free Meta bulk operations docs

Where the Single-Platform Boundary Bites

The official server is excellent at being exactly one thing, a Meta connector. Three boundaries follow from that.

1. Meta only, by design

No Google, no LinkedIn, no TikTok, no Microsoft. Each platform is shipping its own official connector on its own terms. Google's official Google Ads API MCP server arrived October 7, 2025 as an open-source project, read-only at launch. A team spending across four platforms ends up managing four connectors with four auth flows and no shared reporting layer.

2. Phased rollout gating

Accounts not yet in the beta see is_ads_mcp_enabled: false errors, with US and higher-spend accounts reportedly first in line, as of August 2026 (rollout field notes). There is no published waitlist. If your account is not enabled, you wait.

3. No measurement layer

The 29 tools stop at Meta's edge. No GA4 reads, no Tag Manager, no Search Console, no cross-platform attribution view. Dataset quality tools tell you whether Meta receives your signals, not whether your GA4 property and tag setup are producing the right ones.

What the official MCP does not do

It does not touch anything outside Meta. It does not give a cross-platform budget or performance view. It does not read GA4 or manage GTM. It is not available on every ad account yet. And it does not expose Meta's bidding or Advantage+ internals. None of these are flaws. They are the shape of a first-party, single-platform tool.

Running Meta Alongside Twelve Other Platforms

If Meta is your only paid channel, stop here, connect the official server, and enjoy it. If you run cross-platform, the picture changes, and this is where PaidSync fits.

PaidSync is one MCP endpoint carrying 430+ tools across 13 platforms. On Meta specifically it ships 69 tools, full write coverage including campaign creation and bulk operations across many entities at once. Google Ads gets 140+ tools and LinkedIn 25, both full write. TikTok, Microsoft, Snapchat, Reddit, and Pinterest are manage-and-optimize coverage, no campaign creation on those five today. The OpenAI Ads connector covers connect and reporting. The measurement layer is the part no single-platform server offers: 28 GA4 tools including conversion event creation, 37 Tag Manager tools with the full tag, trigger, and variable lifecycle plus publish, and read-only Search Console. Details on the MCP server page.

The write posture mirrors Meta's thinking. Risky mutations run through an approval gate with dry-run previews and an explicit confirm on destructive calls, and sessions can be revoked at any time. When PaidSync opened paid signups in May 2026, six agencies became paying customers in the first four days, and cross-platform reporting through one endpoint was the reason they gave most.

Which Setup Fits Your Situation

Meta is your only paid channel: use the official server. First-party, no separate charge in beta, and the paused-by-default posture is exactly right.

Heavy catalog and feed work on Meta: the official server. Ten catalog tools plus four dataset quality tools is the deepest first-party coverage available.

You spend across two or more platforms: PaidSync. One endpoint, one auth model, 430+ tools, and a single reporting view across all 13 platforms. Pricing starts free, Pro from $99 per month for 600 calls.

Your measurement is the problem, not the ads: PaidSync. GA4 and GTM tools live next to the ad platform tools, so one session can audit the tag, fix the conversion event, and check the campaign.

Your account is not in Meta's rollout yet: PaidSync works today on any Meta ad account you authorize, through the standard Marketing API.

You want both: run both. They coexist in the same Claude connector list, and the official server plus a cross-platform layer is a sensible pairing.

What PaidSync does not do

PaidSync is not first-party. It calls the same Marketing API Meta's own server calls, but Meta will always ship Meta features first. Campaign creation on TikTok, Microsoft, Snapchat, Reddit, and Pinterest is not there yet, those platforms are manage-and-optimize today. The OpenAI Ads connector is connect and reporting, not campaign management. Search Console is read-only. And the free tier's 15 calls a month is enough to evaluate, not to operate; real workloads need Pro at $99 per month.

Frequently Asked Questions

What is Meta's official Ads MCP?

A hosted Model Context Protocol server at mcp.facebook.com/ads, released in open beta on April 29, 2026 as part of Meta's Ads AI Connectors. It gives AI assistants like Claude 29 tools for Meta ads work: campaign management, account and Page reads, product catalog management, dataset quality checks, and insights. It authenticates with Meta Business OAuth and needs no developer app.

How do I connect Meta's Ads MCP to Claude?

Open Settings, then Connectors, and add https://mcp.facebook.com/ads as a remote MCP server. Complete the Meta Business OAuth dialog, pick your ad account, and choose a scope tier (read-only, read and write, or read, write and financial). Test with a read request such as last week's campaign performance. Writes require the ads_management scope. Most practitioners report 5 to 15 minutes from start to first query.

Can Meta's official Ads MCP create and edit campaigns?

Yes, with a write scope granted. Every campaign, ad set, or ad an AI creates lands in paused status by default, and a human must activate it. Edits to already-live entities, like budget changes, take effect immediately with no draft mode, so grant write scopes deliberately.

Why does the Meta Ads MCP return an is_ads_mcp_enabled error?

The beta is a phased rollout. Accounts not yet included see is_ads_mcp_enabled: false errors, with US and higher-spend accounts reportedly prioritized first, as of August 2026. There is no published waitlist. If your account is not enabled yet, a third-party server that uses the standard Marketing API, such as PaidSync, works today on any ad account you authorize.

Does Meta's Ads MCP cover Google Ads or other ad platforms?

No. It covers Meta only. Google ships a separate open-source Google Ads API MCP server, announced October 7, 2025, read-only at launch. Cross-platform work through official servers means one connector per platform and no shared reporting layer. PaidSync covers 13 platforms through one endpoint, including 69 Meta tools.

Does the Meta Ads MCP cost anything?

Meta announced no separate charge for the connector at launch, and the open beta requires no developer app or paid subscription, as of August 2026. You pay for your ad spend as normal. Check Meta's official documentation for current terms.

How does PaidSync compare to Meta's official 29-tool MCP?

The official MCP is first-party, free in beta, and Meta-only. PaidSync is third-party, with 69 Meta tools including bulk operations inside a 430+ tool catalog across 13 platforms, plus 28 GA4 tools and 37 GTM tools for measurement, and approval-gated writes with dry-run previews. They coexist happily in one Claude connector list. Meta-only advertisers should start with the official server. Cross-platform teams get more from one endpoint. PaidSync is free to try at 15 calls a month; Pro starts at $99 per month.