Best Claude Connectors for Meta Ads (2026): Compared
The best Claude connector for Meta Ads in 2026 is NotFair: hosted OAuth with no customer Meta developer app, live reads, and approval-gated writes in Claude, ChatGPT, and Cursor. A Claude connector is a remote MCP server you add in Claude’s Connectors settings. Meta’s official Ads MCP at mcp.facebook.com/ads is a first-party remote server whose write tools create entities paused until activation; this review does not claim Google Ads-style impact snapshots or undo on Meta.
Published
· October 5, 2026
Last verified
· October 16, 2026
Products reviewed
· 11
Author
· Tong Chen and Yuting Zhong
Our verdict
What is the best Claude connector for Meta Ads in 2026?
NotFair. It is a hosted remote MCP server with in-chat approval before every write. It states plainly that Meta changes have no impact review or undo, which NotFair offers for Google Ads only. Claude, ChatGPT, and Cursor share the same NotFair workspace after you connect. Meta’s official Ads MCP is a first-party surface with paused-by-default creates. Other hosts and reporting layers are compared in the tables below.
Install path, Meta Ads tools, and whether Claude can write
A “Claude connector for Meta Ads” may be Meta’s own remote MCP, a published directory listing, a custom MCP URL, or a reporting layer over synced Facebook data. Write contracts differ: paused-first creates, in-chat approval gates, prompt-level confirmation, or no writes at all. “Not published” means the vendor’s public documentation does not support a more specific claim.
Published Notfair listing at https://claude.ai/directory/notfair for Claude.ai, Desktop, and Cowork. Claude Code uses the NotFair plugin marketplace. ChatGPT and Codex: the published NotFair Ads plugin (https://chatgpt.com/plugins/plugin_asdk_app_6a2c658f0d108191b84fb507cb10bb84?open_in_app). Cursor and other MCP clients can add https://notfair.co/api/mcp/notfair as a remote MCP fallback. No customer developer token, Client ID, or Secret.
45 Meta Ads tools
Yes — campaigns, ad sets, ads, creatives, budgets, and more, with dry-run/validate-only on writes and explicit in-chat approval.Capability source
Every change is proposed exactly, waits for explicit approval, and is recorded with who approved it. There is no impact snapshot or undo for this platform; NotFair offers those for Google Ads only.
Claude (web, Desktop, Cowork, Code), ChatGPT (NotFair Ads plugin), and Cursor (hosted MCP)
Custom connector: paste https://mcp.facebook.com/ads. Claude Code: `claude mcp add --transport http --client-id <META_APP_ID> meta-ads https://mcp.facebook.com/ads`. Not a Claude directory listing.Usage source
Seven public tool categories. 65 named tools counted on Meta’s ad-creation (28), catalog (29), experiment (7), and activity-log (1) pages on 6 October 2026. The same developers.facebook.com URLs returned 403 on 16 October 2026, so that counted inventory is retained. Reporting, signals, and help category pages also exist; the overview does not publish one integer.
Yes — create campaign/ad set/ad (paused), update entities, upload creatives, and ads_activate_entity to start spending.Capability source
Write tools create entities in a paused state; the AI client is described as asking for confirmation before activation. Additional NotFair-style approval UX, impact snapshots, and undo are not claimed.
MCP-compatible agents; Meta lists Claude Desktop and Claude Code among validated clients
Add https://meta-ads.mcp.pipeboard.co/ as a connector in Claude, ChatGPT, Cursor, or any MCP client. The host page states it speaks JSON-RPC over MCP (POST).
Pipeboard’s GitHub family table lists 42 Meta Ads tools (campaigns, ad sets, ads, creatives including dynamic creative testing, image upload, insights, targeting, page management). The hosted landing page itself does not publish a tool-by-tool inventory.
Pipeboard’s GitHub README positions end-to-end Meta Ads management (campaigns, creatives, budgets, insights) on the hosted URL. Exact write-tool names are those in the public repo, not inferred here.Capability source
The README documents explicit confirmation on every write and paused-first creates where the platform supports it. NotFair-style in-chat diffs, provenance, and undo are not assumed. This review does not recommend Pipeboard.
Claude, ChatGPT, Cursor, or any MCP client that can add the remote URL
Custom Claude connector (Settings → Connectors → add URL). Ryze’s Claude help (checked 16 October 2026) says any Claude plan works, with Free limited to one custom connector. Ryze’s Meta Ads product page still says Claude Pro, Team, or Max is required because custom connectors are not on the free plan.Usage source
12 Meta Ads tools (9 read including Insights, Graph reads, creatives, leads, Ad Library; 3 approval-gated writes: runGraphWrite, runGraphDelete, uploadImageFromUrl). Same endpoint carries 150+ tools across other platforms.
Yes — three documented writes, each approval-gated. Archives via runGraphDelete are described as cascading and irreversible.Capability source
Vendor documents approval-gated writes. NotFair-style Meta impact snapshots and undo are not claimed. This review does not treat Ryze as a recommended alternative to NotFair.
claude.ai (custom connector), Claude Desktop, Claude Code, ChatGPT, Cursor, and other MCP clients
PaidSync’s docs say search PaidSync under Claude Connectors, or add https://mcp.paidsync.ai/mcp as a custom remote connector, and that this works on every Claude plan including Free. Claude’s public marketplace search for “paidsync” returned no listing on 16 October 2026.Usage source
83 Meta Ads tools. Docs also list Google Ads (152 tools) and other platforms on the same login.
Yes — docs describe creating campaigns and ad sets, creating ads with images, managing creatives with validation before publishing, audiences, and reporting.Capability source
Docs say the AI assistant confirms actions before executing them. NotFair-style Meta impact snapshots and undo are not claimed.
Claude.ai (directory or custom URL), Claude Desktop, Claude Code, ChatGPT, Cursor, Windsurf, and other MCP clients PaidSync lists
Published Claude marketplace listing (Anthropic verified on claude.com/connectors/supermetrics, checked 16 October 2026). Campaign management is documented as early access on an AI-chats destination; MCP server access is a separate subscription entitlement.Usage source
Claude marketplace listing currently exposes data_source_discovery, accounts_discovery, field_discovery, data_query, get_async_query_results, get_today, contact_supermetrics, manage_user_and_team, campaign_and_resource_get, resources_manage, manage_dashboards, supermetrics_guide, manage_campaign, and manage_business_context. A Meta Ads-only tool count is not published separately from the 200+ source suite.
Yes, after Hub write access: view, create, and update campaigns on Facebook Ads, Google Ads, Microsoft Advertising, TikTok Ads, ChatGPT Ads, LinkedIn Ads, and Snapchat Marketing (docs updated 15 October 2026). New campaigns are created paused.Capability source
Hub write settings include options from no human approval through all live changes. Campaign history on the Hub documents revert. This is not NotFair’s in-chat Meta approval-plus-provenance contract.
Claude (directory), Gemini, and the Supermetrics MCP server as documented
Published Claude marketplace listing (Anthropic verified on claude.com/connectors/windsor-ai, checked 16 October 2026). Search Windsor. Windsor documents a Claude Code plugin as well as the directory listing.Usage source
Claude’s public Windsor listing currently exposes five get_* tools. Windsor’s write-actions catalog lists 20 Meta Ads actions (create/pause/enable campaigns, ad sets, and ads, set budgets, boost posts, image/video upload, and related; checked 16 October 2026).
Yes — Windsor’s write-actions catalog documents create, pause, enable, budget, boost-post, and creative-upload actions with confirmation. Windsor’s facebook-ads-to-claude-integration marketing page returned 403 on 16 October 2026, so this row uses the write-actions catalog and Claude marketplace listing instead.Capability source
Windsor states explicit confirmation before changes. NotFair-style operation provenance and Google Ads-style undo are not documented for Meta on the pages used here.
Claude plugin from Connectors, or paste https://mcp.portermetrics.com/mcp as a custom connector. Porter states MCP is included in the Porter plan with no extra MCP fee.Usage source
MCP server docs list 28 tools plus an action catalog of 750+ operations. A Meta Ads-only tool count is not published.
Porter’s Claude help article describes the Claude connection as read-only. The MCP server documentation also exposes execute_action against a catalog that includes Meta ad-platform management. This review does not treat those two pages as the same Claude write contract.
execute_action is annotated destructive so the client can prompt. NotFair-style Meta undo is not documented.
Claude Desktop, Claude Web, Claude Code, ChatGPT/Codex, Gemini
Adzviser documents opening Adzviser in Claude’s Connector Directory and connecting, with a $0.99 14-day trial and MCP included on standard plans after trial. Claude’s public marketplace search for “adzviser” returned no listing on 16 October 2026.Usage source
Meta-specific MCP tool count is not published. Adzviser documents 54 reporting connectors, including Meta Ads campaigns, spend, conversions, ROAS, and audiences.
No — Adzviser documents read-only reporting. Campaign edits and write-backs are explicitly not included.
No mutation surface. Analysis only.
Claude directory; other clients via https://mcp.adzviser.com/http
Custom connector: paste https://connect.composio.dev/mcp in Claude Customize → Connectors. Hobby plan documents 100,000 tool calls/month with up to 20,000 through Composio-managed apps (composio.dev/pricing, checked 16 October 2026).Usage source
70 Meta Ads tools on the current toolkit page (checked 16 October 2026), including Create Campaign, Create Ad Set, Create Ad, Create Ad Creative, Create Ad Video, Delete Campaign, Get Insights, and Get Ad Accounts.
Yes — create, update, and delete campaign objects are listed, along with creatives and video upload.
Managed auth is documented. In-chat diffs, Meta impact review, and undo are not documented as a NotFair-style safety lifecycle. Delete Campaign is listed as a tool.
Claude, ChatGPT, Cursor, and other agent frameworks listed on the Metaads toolkit page
NotFair can upload supplied PNG/JPEG with createAdImage and supplied MP4 with uploadAdVideo. Asset support means working with supplied advertising assets, not generating the underlying image or video. Competitor creative claims are taken only from the linked public docs.
Operating model
Operating model: credentials, routing, and Meta versus Google Ads recovery
Server
Best for
Delivery
Credentials
Safety lifecycle
Multi-account
Clients
NotFair
Our verdict
Operators who want hosted OAuth and approval-gated Meta Ads writes in Claude, ChatGPT, and Cursor
Hosted remote MCP; published Claude directory listing, Claude Code plugin, ChatGPT plugin, Cursor MCP fallback
Hosted OAuth; no customer Meta developer app required
Every change is proposed exactly, waits for explicit approval, and is recorded with who approved it. There is no impact snapshot or undo for this platform; NotFair offers those for Google Ads only.
Connected-account selection with explicit per-call account routing
Claude (web, Desktop, Cowork, Code), ChatGPT (NotFair Ads plugin), and Cursor (hosted MCP)
Meta official Ads MCP
Teams that want Meta’s first-party remote Ads MCP
Meta-hosted remote MCP at https://mcp.facebook.com/ads
Facebook Login for Business / Meta authentication. Meta documents a path without owning a Meta app, and a developer path that adds the Ads MCP use case on a Meta app.
First-party paused-by-default create contract; activation is a separate tool
ads_get_ad_accounts lists accessible ad accounts
Claude Desktop, Claude Code, ChatGPT, Codex, Cursor, and other MCP clients Meta documents
Pipeboard
Teams adding Pipeboard’s hosted Meta Ads MCP URL in Claude
Hosted remote MCP at https://meta-ads.mcp.pipeboard.co/
Hosted connection through Pipeboard’s Meta Ads MCP host
NotFair-style in-chat approval/provenance is not documented on the hosted landing page used here
Hosted Meta ad-account connection as described by Pipeboard
Claude, ChatGPT, Cursor, and other MCP clients named on the host page
Ryze AI
Teams adding a custom remote MCP URL for Meta Ads plus other marketing tools
Hosted remote MCP at connector.get-ryze.ai/mcp
Hosted Facebook sign-in; Ryze documents no customer Meta developer app, access token, or app review
Approval-gated writes; deletions called out as irreversible
Workspace selection during OAuth; listAdAccounts is documented
Claude, ChatGPT, Claude Code, Cursor, Windsurf, VS Code, and other MCP clients
PaidSync
Teams adding a hosted Meta Ads MCP from Claude’s connector directory or a custom URL
Hosted remote MCP at https://mcp.paidsync.ai/mcp
Hosted Facebook sign-in from PaidSync’s Connections page. Docs do not require a customer Meta developer app. Free 15 tasks/month; Pro from $99/month for 600 tasks. Every plan includes Google Ads and Meta Ads.
Prompt-level confirmation; not a NotFair-style server-side Meta approval gate with impact/undo
Multiple Meta ad accounts, including Business Manager accounts, under one PaidSync account are documented
Claude Desktop, claude.ai, ChatGPT, Perplexity, Cursor, Windsurf, Claude Code
Supermetrics
Teams that already use Supermetrics reporting and want Claude to query or manage Facebook Ads through that layer
Claude directory connector plus a separate Supermetrics MCP server for technical hosts
Supermetrics account/team OAuth; Facebook Ads connected as a data source. Write access is granted in the Supermetrics Hub.
Paused-first creates; Hub-configurable approval; Campaign history on the Hub
Account selection in chat; write access only on data-source connections you own
Claude, ChatGPT, Gemini, Microsoft Copilot, and MCP hosts documented by Supermetrics
Windsor.ai
Teams blending Meta Ads with many other sources in Claude, with optional write actions
Hosted MCP; published Claude directory listing
Windsor account plus Meta/Facebook Ads OAuth at onboard.windsor.ai
Confirmation before writes; paused-first creates. Claude’s public listing currently shows read/get tools; write actions are documented on Windsor’s write-actions catalog.
Meta ad accounts connected in Windsor; 350+ other sources available on the same connector
Claude Web, Desktop, Code, ChatGPT, Copilot, and other MCP clients per Windsor MCP docs
Porter Metrics
Teams querying Meta and other marketing data in Claude through a Porter workspace
Remote MCP at mcp.portermetrics.com/mcp; Claude plugin or custom connector
Porter account (Google SSO documented) plus connected Meta/Facebook Ads in Porter
Claude help: read-only. MCP server: client confirmation on destructive execute_action.
list_accounts over Porter-connected sources; Facebook Ads is one of 32 connectors
Claude Desktop/Web/Code, ChatGPT, Gemini, MCP Inspector
Coupler.io
Teams that want Claude to query a Coupler data flow that includes Meta/Facebook Ads
Managed MCP via Coupler data flows with Claude as a destination
Coupler.io account; Facebook Ads (or other sources) connected in a data flow
Reporting/analysis layer; no published Meta Ads mutation gate
Multiple Coupler sources in one conversation
Claude, ChatGPT, and other Coupler AI destinations
Adzviser
Teams that want hosted, read-only Meta Ads reporting in Claude
Hosted remote MCP; vendor documents a Claude directory listing
Adzviser workspace OAuth; Meta Ads connected inside Adzviser
Read-only by design
Per-workspace connected sources
Claude, ChatGPT, Gemini, OpenClaw, n8n, and other MCP clients Adzviser lists
Composio
Builders connecting many app toolkits, including Meta Ads, through Composio MCP
Hosted MCP / Tool Router; custom Claude connector URL from Composio Connect
Composio-managed Meta OAuth (API key also listed on the toolkit page)
Not a NotFair-style server-side Meta approval gate. Delete Campaign is a published tool.
Get Ad Accounts retrieves accessible ad account IDs
Claude, ChatGPT, Cursor, and the other agent frameworks listed on composio.dev/toolkits/metaads
NotFair publishes this comparison and is therefore not a neutral party. Source links are public so every row can be challenged. Cross-platform connector totals are not treated as Meta Ads-specific tool counts. Other hosted MCP products exist; they are covered on the Meta Ads MCP servers comparison and are not recommended here.
Testing method
A benchmark that can be rerun
We review the Claude install path, Meta Ads tool surface, write contract, approval/recovery path, and account routing. Google Ads-style impact snapshots are not assumed for Meta. Competitor rows were checked against live public docs on 16 October 2026. Meta’s developers.facebook.com host returned 403 on this date, so official tool-inventory counts from 6 October 2026 are retained and dated.
Is the connector a published Claude directory listing, a custom remote MCP URL, a local stdio/Cloud Run server, or a plugin?
02
Claude surfaces
Does the same connection work in Claude.ai, Claude Desktop, Claude Cowork, and Claude Code?
03
Tool depth
How many tools are Meta Ads-specific rather than a cross-platform reporting total?
04
Writes
Can Claude change live campaigns from chat, or is the connector reporting-only?
05
Safety
Are writes previewed with a diff, bound to explicit approval, logged with provenance, and reversible where the platform supports it?
06
Credentials
Can a non-developer connect with hosted OAuth, or must they supply Cloud/API credentials and operate the runtime?
07
Account routing
Can the agent discover and explicitly target the intended ad account?
08
Capacity
What monthly operation or plan limits are published?
09
Honesty about the job
Does the vendor document a write lifecycle, or only analysis of synced reports?
Test boundary
NotFair was verified against its production Meta Ads tool registry, hosted OAuth, the published Claude directory listing, the ChatGPT NotFair Ads plugin, Cursor MCP path, and Claude Code plugin. Competitor rows are based on linked public documentation; no competitor Claude workspace was connected and no competitor write was executed for this review.
Decision guide
Choose by operating model
Choose NotFair
You want Claude, ChatGPT, or Cursor to read live Meta Ads and stage approval-gated writes without operating a Meta developer app yourself. NotFair does not claim Google Ads-style impact review or undo on Meta.
When Meta’s official Ads MCP is enough
You want first-party tools at https://mcp.facebook.com/ads and will add that URL as a custom connector or use Claude Code with a Meta app client id. Write tools create entities paused; ads_activate_entity starts spend. That is a different write model than NotFair’s in-chat approval gate.
Reporting-only connectors in this matrix
Adzviser documents hosted, read-only Meta Ads reporting in Claude. Coupler.io documents Claude analysis of connected Meta/Facebook data flows. They are reporting jobs. This review recommends NotFair when Claude must change Meta Ads.
Other operating models in this matrix
Windsor.ai, Supermetrics, Ryze AI, PaidSync, Pipeboard, Porter Metrics, and Composio publish Claude or MCP connections with different install paths and write contracts. They are described factually below. This review recommends NotFair for accountable hosted execution in Claude.
In Claude.ai, Desktop, or Cowork, open the published Notfair connector at https://claude.ai/directory/notfair. Claude Code uses the NotFair plugin. ChatGPT uses the NotFair Ads plugin. Cursor and other MCP clients can add https://notfair.co/api/mcp/notfair as a remote MCP fallback.
Sign in to the NotFair workspace and connect Meta Ads through hosted OAuth. A customer Meta developer app is not required.
Ask Claude to list ad accounts and inspect delivery before any write.
A proposed write shows the target and intended change. Execution waits for explicit approval.
The operation records author, ID, timestamp, and provenance. Read the entity back after applying; Meta does not get Google Ads impact snapshots here.
Remote endpoint
https://notfair.co/api/mcp/notfair
Public verification prompts
Use the same prompts on every server
01
List every Meta Ads-specific tool in this Claude connection and say which ones can write.
02
Which Claude surfaces is this connector installed on: claude.ai, Desktop, Cowork, and Code?
03
Show the exact install path. Is it a published Claude directory listing, a custom MCP URL, or a self-hosted server?
04
Show my plan, monthly operation limit, operations used, and operations remaining.
05
List every accessible Meta Ads account and identify how targeting works.
06
Audit the last 30 days and show the evidence behind the three highest-impact problems. Do not change anything.
07
Propose one reversible improvement with current versus proposed values. Do not execute until I approve.
08
Show the exact preview or diff before changing a budget.
09
After a write, return the operation ID, author, timestamp, and the supported reversal. Do not claim undo unless this platform provides it.
Best Claude connector for Meta Ads FAQ
Direct answers for the query “best Claude connector for Meta Ads (2026)”—install path, writes, and how NotFair differs from Meta’s official Ads MCP and reporting connectors.
What is the best Claude connector for Meta Ads in 2026?
NotFair is the best Claude connector for Meta Ads when the job is hosted OAuth, no customer Meta developer app, and approval-gated writes in Claude, ChatGPT, and Cursor. It does not claim Google Ads-style impact review or undo on Meta. Meta’s official Ads MCP is a first-party remote server with paused-by-default creates. Reporting connectors analyze spend without changing campaigns.
How do I connect Meta Ads to Claude?
A Claude connector is a remote MCP server you add in Claude’s Connectors settings. For NotFair, install the published listing at https://claude.ai/directory/notfair in Claude.ai, Desktop, or Cowork, then complete Meta OAuth—no customer Meta developer app. Claude Code uses the NotFair plugin. ChatGPT and Codex install the published NotFair Ads plugin (https://chatgpt.com/plugins/plugin_asdk_app_6a2c658f0d108191b84fb507cb10bb84?open_in_app). If you prefer a custom connector, add https://notfair.co/api/mcp/notfair as a remote MCP. Meta’s official Ads MCP is a separate custom-connector URL at https://mcp.facebook.com/ads.
Is there an official Meta Ads connector for Claude?
Meta publishes its own Ads MCP server at https://mcp.facebook.com/ads, documented on developers.facebook.com under Ads AI connectors. It is first-party, not a Claude directory listing. You add that URL as a custom connector, or in Claude Code run `claude mcp add --transport http --client-id <META_APP_ID> meta-ads https://mcp.facebook.com/ads`. Owning a Meta app is not always required. Write tools create campaigns, ad sets, and ads paused; ads_activate_entity changes a paused entity to active and starts spending. That is a different write model than NotFair’s in-chat approval gate. Meta’s developers.facebook.com host returned 403 on 16 October 2026; the paused-create / ads_activate_entity contract is retained from Meta’s public tool pages last successfully fetched 6 October 2026, and the server URL plus auth model were re-confirmed from Meta’s get-started documentation.
Do I need a Meta developer app?
Not for NotFair: hosted OAuth is enough, and a customer Meta developer app is not required. Meta’s official Ads MCP documents a path without owning a Meta app, and a developer path that adds the Ads MCP use case on a Meta app (permissions include ads_read, ads_management, ads_mcp_management, catalog_management, business_management, pages_show_list, and instagram_basic).
Can Claude make changes, or only read?
It depends on the connector. NotFair reads live Meta Ads and stages writes behind explicit in-chat approval, with provenance—and it does not claim Google Ads-style impact snapshots or undo on Meta. Meta’s official Ads MCP can write, but creates stay paused until ads_activate_entity. Adzviser and Coupler.io document reporting only. Windsor, Supermetrics, Ryze AI, PaidSync, and Composio document some Meta writes with different confirmation models—none of those are this review’s recommendation.
Does NotFair work in Claude, ChatGPT, and Cursor?
Yes. Claude.ai, Desktop, and Cowork install the published Notfair connector from https://claude.ai/directory/notfair. Claude Code uses the plugin marketplace. ChatGPT and Codex install the published NotFair Ads plugin (https://chatgpt.com/plugins/plugin_asdk_app_6a2c658f0d108191b84fb507cb10bb84?open_in_app). Cursor can add the same hosted MCP at https://notfair.co/api/mcp/notfair as a fallback. All of those clients share the same NotFair workspace and Meta ad accounts after you connect.
What does NotFair cost for Claude Meta Ads work?
Free includes 7 unlimited days, then 300 MCP operations per month. Growth is $99/mo monthly, or $950/yr (~$79/mo) annually with unlimited operations. No credit card to start. Claude, ChatGPT, and Cursor subscriptions are separate.
Was every competitor tested in a live Claude workspace?
No. This review combines public documentation with live production verification of NotFair. Competitor behavior is labeled from vendor documentation or public listings.
Claude landings, setup, and MCP benchmark
Install NotFair, then use the sourced Meta Ads MCP-server matrix when you need tool-count and creative-upload evidence beyond Claude-specific install paths.