NotFairNotFair
Start now

Co-founders

Does Claude Work With Meta Ads?

Yes. Claude can use Meta Ads through MCP. NotFair is a hosted option with 40 Meta Ads tools, OAuth setup, and approval-gated writes that match this platform's real lifecycle.

Tong Chen and Yuting Zhong|

Yes — Claude can work with Meta Ads through an MCP (Model Context Protocol) server. Anthropic does not publish a first-party Meta Ads connector. Meta publishes an official Ads MCP with paused-by-default writes. NotFair provides a hosted Streamable HTTP server so Claude Desktop, Claude Code, Claude Cowork, and other MCP-compatible Claude surfaces can use the accounts you authorize.

Which Claude products work with Meta Ads?

  • Claude.ai, Claude Desktop, and Claude Coworkinstall the published Notfair connector and complete NotFair OAuth.
  • Claude Codeadd the hosted MCP URL (`https://notfair.co/api/mcp/notfair`) with HTTP transport.
  • Confirm the particular Claude surface and plan you use supports remote MCP before troubleshooting the account connection.

What you need to make it work

  • A Meta Ads account Claude is allowed to see.
  • NotFair hosts the Meta Marketing API app. You authorize existing ad accounts through OAuth; you do not create a Meta developer app.
  • A Claude surface that supports the MCP transport you selected.
  • About five minutes for the NotFair connection. NotFair advertises 40 Meta Ads tools, measured from the production registrar and guarded by a drift test.

What safety looks like when Claude can write

Read access and write access are not the same. Preview the target and intended change, wait for explicit approval, then record operation provenance. NotFair does not expose Google Ads-style impact snapshots or undo on Meta. createAdImage uploads supplied PNG/JPEG assets. uploadAdVideo exists but production availability is gated behind a Graph API version and test-account canary. Claude does not receive your platform password or raw refresh token.

What does not work

  • Claude cannot read Meta Ads by URL or screenshot. Pasting a dashboard URL does nothing without an MCP connection.
  • A Claude surface that does not support the selected MCP transport cannot connect through that server.
  • Do not assume Google Ads impact snapshots or undo exist on this platform. NotFair only claims the lifecycle documented above.

How does Claude actually talk to Meta Ads?

Claude does not call the Meta Ads API directly. It calls the MCP server you configured, which calls Meta Ads on your behalf. With NotFair that server is hosted: NotFair hosts the Meta Marketing API app. You authorize existing ad accounts through OAuth; you do not create a Meta developer app. In every case the server—not Claude itself—owns the provider API interaction.

FAQ

Move from article to live account work

Connect your account first, then use an MCP client to turn the article workflow into a reviewed account action.

FAQ

Common questions about Model Context Protocol.

Anthropic does not publish a Meta Ads server. Meta publishes an official Ads MCP with paused-by-default writes. Claude uses whichever compatible MCP server you configure, including NotFair.

NotFair advertises 40 Meta Ads tools, measured from the production registrar and guarded by a drift test.

Supported writes exist. Preview the target and intended change, wait for explicit approval, then record operation provenance. NotFair does not expose Google Ads-style impact snapshots or undo on Meta. createAdImage uploads supplied PNG/JPEG assets. uploadAdVideo exists but production availability is gated behind a Graph API version and test-account canary.

Tool call inputs and outputs flow through Claude the same way any conversation does. Anthropic's data retention policies apply. NotFair only sends the records Claude requests via tool calls — not a full account dump.