Vendor-authored, source-reviewed comparison · 2026
NotFair is the best Claude connector for Meta Ads in 2026 when you need hosted OAuth and approval-gated writes inside Claude.ai, Claude Desktop, Claude Code, and Cowork. Install the published Notfair listing from Claude’s directory, or the Claude Code plugin, then connect Facebook assets in NotFair. Meta’s official Ads MCP is a first-party remote server at mcp.facebook.com/ads whose write tools create entities paused until activation. Ryze AI and PaidSync publish hosted MCP connections with counted Meta Ads writes and different approval models. Reporting connectors such as Adzviser analyze Meta spend in Claude without campaign writes. Windsor.ai and Supermetrics document directory installs plus optional campaign writes with different confirmation models. This review does not claim Google Ads-style impact snapshots or undo on Meta.
Our verdict
NotFair. It is a published Claude directory connector with hosted OAuth, counted Meta Ads tools, and in-chat approval before writes, with honest documentation of what Meta supports versus Google Ads impact/undo. Meta’s official Ads MCP is a first-party surface with paused-by-default creates. Other hosts and reporting layers are described factually below—they are not the recommendation in this review.
Comparison matrix
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.
| Connector | Claude install | Meta Ads tools | Writes from Claude | Safety model | Claude surfaces |
|---|---|---|---|---|---|
NotFair Our verdict | Published Notfair listing at https://claude.ai/directory/notfair for Claude.ai, Desktop, and Cowork. Claude Code uses the NotFair plugin marketplace. No custom MCP URL, Client ID, or Secret for the directory path. | 40 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 | Exact proposal, explicit approval, and operation provenance. NotFair does not expose Google Ads-style impact snapshots or undo for this platform. | Claude.ai, Claude Desktop, Claude Cowork, and Claude Code |
Meta official Ads 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 documented as the published Notfair-style directory listing used in this review.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. 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 |
Pipeboard | 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). | A tool-by-tool inventory is not published on the hosted landing page fetched for this row. Pipeboard’s GitHub repository describes a Meta Ads MCP covering campaigns, ad sets, ads, and insights. | Public positioning includes Facebook/Instagram ads management. Exact write-tool names and approval UX are those documented in Pipeboard’s public repo and host, not inferred here.Capability source | Public host docs describe hosted MCP; NotFair-style approval, provenance, and undo are not assumed. | Claude, ChatGPT, Cursor, or any MCP client that can add the remote URL |
Ryze AI | Custom Claude connector (Settings → Connectors → add URL). Ryze’s Claude help states a paid Claude plan (Pro, Team, or Max) is required because the free plan does not support custom connectors.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 | Claude directory: search PaidSync under Connectors, or add https://mcp.paidsync.ai/mcp as a custom remote connector. PaidSync’s docs state this works on every Claude plan, including Free.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 |
Supermetrics | Published Claude directory listing. Campaign management is documented as early access on an AI-chats destination; MCP server access is a separate subscription entitlement.Usage source | Claude directory listing currently exposes discovery, query, dashboard, and campaign tools. 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 (and other listed ad platforms). 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 |
Windsor.ai | Claude directory install (search Windsor). Windsor documents a Claude Code plugin as well as the directory listing.Usage source | Meta-specific MCP tool count is not published as a registrar list. Windsor’s write-actions catalog lists 18 Meta Ads actions (create/pause/enable/update campaigns, ad sets, and ads, set budgets, boost posts, and related). | Yes — the Meta-to-Claude page documents create, pause, and re-budget from chat with confirmation before every change.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.ai, Claude Desktop, and Claude Code |
Porter Metrics | 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 |
Coupler.io | Create a data flow with Claude as the destination, then install the Coupler.io connector in Claude. Team/Enterprise may need an admin.Usage source | Meta-specific MCP tool count is not published. Coupler documents 400+ sources, including Facebook Ads, feeding Claude. | Public Claude destination docs describe conversational analysis, not Meta Marketing API writes. | No Meta Ads write lifecycle is published on the pages used here. Scheduled refreshes keep the data flow current. | Claude Web, Desktop, mobile, Cowork, and Claude Code with a single web connector, per Coupler’s Claude destination docs |
Adzviser | Open Adzviser in Claude’s Connector Directory and connect. Adzviser documents a $0.99 14-day trial; MCP is included on standard plans after trial.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 |
Composio | Custom connector: paste the Composio MCP URL in Claude Customize → Connectors. Hobby plan documents 100,000 tool calls/month with up to 20,000 through Composio-managed apps on the Google Ads toolkit FAQ; Meta uses the same Composio plans. | 50 Meta Ads tools on the current toolkit page, including Create Campaign, Create Ad Set, Create Ad, Create Ad Creative, Delete Campaign, Get Insights, and Get Ad Accounts. | Yes — create, update, and delete campaign objects are listed. Composio’s Google Ads FAQ (same product family) tells operators to keep an approval step in the prompt for side-effecting actions. | 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
| 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 | Hosted remote MCP; published Claude directory listing plus Claude Code plugin | Hosted OAuth; no customer Meta developer app required | Exact proposal, explicit approval, and operation provenance. NotFair does not expose Google Ads-style impact snapshots or undo for this platform. | Connected-account selection with explicit per-call account routing | Claude.ai, Claude Desktop, Claude Cowork, and Claude Code |
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. Claude.com currently annotates the Windsor connector capabilities as Read. | 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’s directory | Hosted remote MCP; published 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) | Prompt-level approval guidance; Delete Campaign is a published tool. Not a NotFair-style server-side Meta approval gate. | 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
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 6 October 2026.
01
Is the connector a published Claude directory listing, a custom remote MCP URL, a local stdio/Cloud Run server, or a plugin?
02
Does the same connection work in Claude.ai, Claude Desktop, Claude Cowork, and Claude Code?
03
How many tools are Meta Ads-specific rather than a cross-platform reporting total?
04
Can Claude change live campaigns from chat, or is the connector reporting-only?
05
Are writes previewed with a diff, bound to explicit approval, logged with provenance, and reversible where the platform supports it?
06
Can a non-developer connect with hosted OAuth, or must they supply Cloud/API credentials and operate the runtime?
07
Can the agent discover and explicitly target the intended ad account?
08
What monthly operation or plan limits are published?
09
Does the vendor document a write lifecycle, or only analysis of synced reports?
Test boundary
NotFair was verified against its production Meta Ads registrar, hosted OAuth, published Claude directory listing, and Claude Code plugin path. 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
You want Claude.ai, Desktop, Cowork, or Code 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.
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.
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.
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.
NotFair production path
Remote endpoint
https://notfair.co/api/mcp/notfairPublic verification prompts
List every Meta Ads-specific tool in this Claude connection and say which ones can write.
Which Claude surfaces is this connector installed on: claude.ai, Desktop, Cowork, and Code?
Show the exact install path. Is it a published Claude directory listing, a custom MCP URL, or a self-hosted server?
Show my plan, monthly operation limit, operations used, and operations remaining.
List every accessible Meta Ads account and identify how targeting works.
Audit the last 30 days and show the evidence behind the three highest-impact problems. Do not change anything.
Propose one reversible improvement with current versus proposed values. Do not execute until I approve.
Show the exact preview or diff before changing a budget.
After a write, return the operation ID, author, timestamp, and the supported reversal. Do not claim undo unless this platform provides it.
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.
NotFair is the best Claude connector for Meta Ads when the job is hosted OAuth and approval-gated writes in Claude.ai, Desktop, Code, and Cowork. 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.
Yes. Claude.ai, Claude Desktop, and Cowork install the published Notfair connector from Claude’s directory. Claude Code uses the NotFair plugin marketplace. Both paths share the same NotFair workspace and Meta ad accounts after you connect.
Meta hosts a remote Ads MCP at https://mcp.facebook.com/ads. Public docs show adding that URL as a custom connector or `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 (Meta documents a setup path without one). Write tools create campaigns, ad sets, and ads paused; ads_activate_entity changes a paused entity to active and starts spending. That is not the same as NotFair’s in-chat approval gate.
Not according to the public docs used for this review. Adzviser describes a hosted, read-only reporting MCP and states campaign edits are not included. Coupler.io’s Claude destination docs describe pulling business data into Claude for analysis. Use NotFair when Claude must stage live Meta writes.
Windsor’s Meta-to-Claude page documents directory install plus write actions (create, pause, re-budget) with confirmation. Its write-actions catalog lists 18 Meta Ads actions. Supermetrics documents Facebook Ads campaign create/update through Claude after Hub write access, with paused-first creates and Hub campaign history. NotFair is a counted Meta Ads tool surface with a server-side in-chat approval gate and provenance—and it does not claim Google Ads-style undo on Meta.
Open the published Notfair listing at https://claude.ai/directory/notfair, choose Connect, and complete NotFair sign-in plus Meta OAuth. No MCP URL, Client ID, or Secret is required for that path. Claude Code users follow the Meta Ads plugin setup guide instead.
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’s own subscription is separate.
No. This review combines public documentation with live production verification of NotFair. Competitor behavior is labeled from vendor documentation or public listings.
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.
Answer-first landing for connecting Claude to Facebook and Instagram ads.
Install the published Notfair connector in Claude.ai, Desktop, and Cowork.
Install NotFair in Claude Code for Meta Ads.
Tool counts, image/video upload, and approval-gated writes.
All NotFair comparison pages.
One hosted connector across ads, analytics, CRM, and websites.
Parallel sourced comparison for Google Ads in Claude.
From comparison to first write
The free plan includes seven days of unlimited access, then 300 MCP operations each month. No credit card.