The official Meta MCP for ads is Meta's Ads MCP, a hosted server at mcp.facebook.com/ads, in open beta since April 29, 2026. To use it in Claude, in order: open Settings, then Connectors, add https://mcp.facebook.com/ads as a remote MCP server, complete the Meta Business OAuth dialog and pick your ad account and scope tier; Claude then gets 29 tools to read, create and edit Meta ads, and new campaigns land paused until a human activates them.
This guide covers setup in Claude, what the 29 tools do, the July 16, 2026 update that added developer-app connections and server rules, where the single-platform boundary sits, and how PaidSync, with 92 Meta tools inside a 630+ tool catalog across 14 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.
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.
The launch date is April 29. The server did not launch in July, but it did grow. On July 16, 2026 Meta added two capabilities, per the Meta for Business announcement. First, developer-app connections. Any AI application can now connect to Meta ads through your own Meta developer app, which Meta describes as the path to "deeper, more customizable integrations". The no-app OAuth flow from April still works and is still the simplest route for a Claude user. Second, ads MCP server rules. Anyone with full control of a business portfolio can now set what AI agents may do on an ad account, "from budget changes to catalog updates" in Meta's words. That is governance at the platform edge. It pairs well with an approval step on the client side, and it is the first time a first-party ads MCP has shipped one.
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.
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.
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.
Meta has kept adding to the server since launch. Its own overview page, updated July 14, 2026 and checked September 23, 2026, now groups the tools into seven categories: reporting, ad creation and management, catalogs, signals and datasets, Help Center search, A/B tests and conversion lift studies, and activity logs. The launch split above is still a fair guide to where the weight sits.
The write posture is the most interesting design choice, and Meta got it right.
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 92 Meta tools including bulk operations. Free tier, 15 tasks a month, no card.
Get started for free Meta bulk operations docsThe official server is excellent at being exactly one thing, a Meta connector. Three boundaries follow from that.
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.
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.
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.
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.
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 630+ tools across 14 platforms. On Meta specifically it ships 92 tools, full write coverage including campaign creation and bulk operations across many entities at once; the full list is on the Meta Ads MCP page. Google Ads gets 158 tools, LinkedIn 34 and ChatGPT Ads 28, all with campaign creation. Microsoft, TikTok, Snapchat, Reddit, Pinterest and X are manage-and-optimize coverage, no campaign creation on those six today. The measurement layer is the part no single-platform server offers: 26 GA4 tools including conversion event creation, 39 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. Google Ads creates and most other creates run as a dry run first, and deletes, pauses and budget changes need an explicit confirm_destructive flag. From Claude, the person's check is Claude's own confirmation prompt. In the PaidSync workspace, every write waits as an approval card, and an applied card offers Undo when the change has a safe inverse. Sessions can be revoked at any time.
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, 630+ tools, and a single reporting view across all 14 platforms. Pricing starts free, Pro from $99 per month for 600 tasks.
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.
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 Microsoft, TikTok, Snapchat, Reddit, Pinterest and X is not there yet; those platforms are manage-and-optimize today. Search Console is read-only. And the free tier's 15 tasks a month is enough to evaluate, not to operate; real workloads need Pro at $99 per month.
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.
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.
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.
On July 16, 2026 Meta added developer-app connections, so any AI application can connect to Meta ads through your own Meta developer app, and ads MCP server rules, which let anyone with full control of a business portfolio govern what AI agents can do on an ad account, from budget changes to catalog updates. The server itself launched in open beta on April 29, 2026.
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.
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 14 platforms through one endpoint, including 92 Meta tools.
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.
The official MCP is first-party, free in beta, and Meta-only. PaidSync is third-party, with 92 Meta tools including bulk operations inside a 630+ tool catalog across 14 platforms, plus 26 GA4 tools and 39 GTM tools for measurement, dry-run previews on creates and an explicit confirmation on destructive changes. 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 tasks a month; Pro starts at $99 per month.
Meta's official Ads MCP documentation is on Meta for Developers, under Ads AI Connectors, at the Ads MCP server overview. Meta announced the connectors on its business news page. This guide's facts about Meta's server were checked on September 2, 2026. For Meta next to Google Ads, LinkedIn and other channels in one connection, see the Meta Ads MCP from PaidSync.ai.
Yes. Meta's official Ads MCP at mcp.facebook.com/ads connects Meta ad accounts, which run Facebook and Instagram ads, to an AI client like Claude through Meta Business OAuth, with 29 tools to read, create and edit ads. PaidSync.ai is a third-party option with 92 Meta tools in the same connection as 13 more platforms.
It depends on your channels. If Meta is your only paid channel, the official server covers it with 29 tools and new campaigns paused by default. If you run Meta next to Google Ads, LinkedIn, TikTok and more, PaidSync.ai puts 92 Meta tools inside a 630+ tool catalog across 14 platforms. The best MCP for Meta Ads guide compares the options.
See every platform from one endpoint. 630+ tools, 14 platforms, dry runs before creates.
Get started for free See pricing