NotFairNot Fair
MCPGoogle Ads Claude Connector Setup Guide

More NotFair Setup Guides

Access Google Ads and Meta Ads from any AI client via NotFair MCP.

Google Ads

  • Claude Cowork, Desktop, WebInstall NotFair as a custom MCP connector inside Claude.ai.
  • Claude CodeInstall via Claude plugin.
  • CodexAdd the NotFair MCP to OpenAI's Codex CLI with one command.
  • Any other client via MCPGeneric MCP config — works with Cursor, Cline, or any MCP-compatible client.

Meta Ads

  • Claude Cowork, Desktop, WebInstall the NotFair Meta connector inside Claude.ai for Facebook + Instagram ads.
  • Claude CodeInstall via Claude plugin for Meta (Facebook + Instagram).
  • CodexAdd the NotFair Meta MCP to OpenAI's Codex CLI with one command.
  • Any other client via MCPGeneric MCP config for Meta — works with Cursor, Cline, or any MCP-compatible client.
PricingBook a Demo
NotFairNot Fair

AI-powered Google Ads diagnosis and execution for Claude. Find issues, draft fixes, and approve every write.

Articles

Google Ads Claude Connector Setup GuideGoogle Ads Claude Code Plugin Setup GuideGoogle Ads Codex MCP Setup GuideGoogle Ads MCP Server (any client)Meta Ads Claude Connector Setup GuideMeta Ads Claude Code Plugin Setup GuideMeta Ads Codex MCP Setup GuideMeta Ads MCP Server (any client)

Company

Privacy PolicyTerms of ServiceJoin Discord

© 2026 NotFair. All rights reserved.

Turn Claude Into Your Marketing Engine

Connect NotFair to Claude, OpenClaw, Codex, Cursor, or Hermes and operate Google Ads + Meta Ads from a chat — diagnose, draft fixes, and approve every write.

1

Open Claude settings

Open the Claude connectors page directly:Customize → Connectors
2

Add a custom connector

Paste in to the modal:

Name

NotFair-GoogleAds

Remote MCP server URL

https://notfair.co/api/mcp/google_ads
3

Sign in and start asking

After clicking Add, Claude opens a sign-in flow. Sign in with NotFair and you're all set. Try: Audit my Google Ads account and rank fixes by impact.

A Complete Marketing Engine Inside Your Agent

Diagnostics, audits, writes, and undo — all driven by one MCP connection per ad account.

Why did our cost-per-lead spike this week?
!FNotFair

CPL up 42% WoW. Three campaigns drove it:

  • Brand-Search+$1,820 spend · 0 conversions
  • PMax-US+$940 · CPA $38 → $89
  • LeadGen-Q4search terms drifted to "free"

Want me to draft 14 negatives + pause Brand-Search?

Diagnose

Live context. Not yesterday's report.

Your agent reads the same numbers you'd open in the platform UI: cost, conversions, impression share, learning phase, frequency, quality score. No CSV exports, no stale dashboards.

Audit my Google Ads account and rank fixes by impact.
!FNotFair

Ran 20 reads across spend, search terms, quality scores, and assets. Top issues by spend at risk:

  1. 01Loose-match keywords burning $2.4k/wk$2,400/wk
  2. 02Missing negatives on LeadGen-Q4$1,180/wk
  3. 03PMax with no asset coverage$640/wk
  4. 043 ads disapproved (silent)$310/wk

Total recoverable: $4,530/wk. Open the fix list?

Audit

Audits that already know what to fix.

One prompt fans out 20 GAQL or Graph API reads in a single pass, scores findings by spend at risk, and returns a prioritized fix list. The audit ends with a button, not a PDF.

Pause everything below 1.5 ROAS in the last 14 days.
!FNotFair

Found 6 ad sets matching. Diff before I apply:

Ad set14d spendROAS
− Retarget-Cart-V3$1,2400.8
− Cold-Lookalike-IG$8901.1
− Broad-Interest-FB$6101.3
− Influencer-Test-A$4200.4
awaiting approval
Operate

Pause, shift, rename, rewrite — from chat.

Not a read-only audit tool. Every entity an account manager touches is exposed as a write tool, with a diff-and-approve gate before anything hits the ad platform.

Undo what you did at 14:32.
!FNotFair

Found change chg_8f21 — paused Brand-Search at 14:32 today.

BeforePAUSED
After undoENABLED

Reverted. Anything else to roll back?

1 change reverted
Approve & undo

Every write is reviewed. Every write is reversible.

Reads are unrestricted. Writes show you a diff before they land, and NotFair logs every change to its own history — one call rolls anything back.

How is Meta doing this week vs Google?
!FNotFair

Pulled both accounts. Last 7 days:

Google Ads

$8,420

spend · 2.3x ROAS

Meta Ads

$5,140

spend · 1.4x ROAS

Meta ROAS dropped from 2.1 → 1.4. Want me to investigate which ad sets cooled off?

Two platforms

Google Ads and Meta Ads. One MCP per account.

Symmetric servers, symmetric setup. Connect Google to operate Search and Performance Max; connect Meta to operate Facebook and Instagram. Same client, same flow.

Built for the people
spending the budget.

SMB founders

Self-doers running their own Google or Meta spend. Replace the agency review call with a Claude conversation.

Performance agencies

Onboard a new account, audit it, and ship the fix list before the kickoff call ends.

E-commerce ops

Daily search-term sweeps, negative-list maintenance, and budget reshuffles run from a single agent prompt.

Lead-gen teams

Match search terms to MQL quality, tighten match types, and route budget toward the geos and keywords that close.

Solo consultants

Manage ten accounts the way you used to manage one. One MCP endpoint per client, one chat per question.

Wire it up.
Operate from chat.

Connect Meta Ads

Free · OAuth 2.0 · No credit card

FAQ — NotFair MCP

Common questions about authenticating, configuring, and operating the NotFair MCP servers.

What is NotFair MCP?

Two hosted Model Context Protocol servers — one for Google Ads, one for Meta Ads — that expose your accounts to MCP-compatible AI clients. Reads stream live campaign data; writes are proposed in chat and require explicit approval before they hit the ad platform.

Which AI clients can I use?

Anything that speaks the MCP Streamable HTTP transport: Claude.ai (Web, Desktop, Cowork), Claude Code, OpenAI Codex CLI, Cursor, Cline, and custom MCP clients. The server URL stays the same — only the client-side config differs.

Do I need to self-host anything?

No. Both servers are hosted by NotFair at https://notfair.co/api/mcp/google_ads and https://notfair.co/api/mcp/meta_ads. You connect the underlying ad account once via OAuth and point your client at the URL.

How does authentication work?

OAuth 2.0 with PKCE is the default — Claude.ai and Codex run it automatically. For clients that don't support OAuth, you can use a Bearer token via the Authorization header. Generate either at notfair.co/connect or notfair.co/connect/meta-ads.

Can the AI write to my ad accounts?

Only with explicit approval. Write tools propose changes, the client surfaces the diff, and you confirm before anything hits the Google Ads or Meta Marketing API. Read access is unrestricted; every write is gated.

What does it cost?

Connecting and running audits is free with no credit card. Paid plans unlock higher usage limits and team features.

Where do I find platform-specific configs?

The /google-ads-mcp and /meta-ads-mcp pages have generic JSON snippets that work in any MCP client. The per-client setup guides walk through Claude.ai, Claude Code, and Codex specifically.

Server configs and per-client guides

Platform-specific configs and step-by-step setup walkthroughs for each supported client.

Google Ads MCP server

Generic MCP config and tool list for NotFair-GoogleAds.

Meta Ads MCP server

Generic MCP config and tool list for NotFair-MetaAds.

Claude Connector setup guide

Install NotFair as a custom MCP connector inside Claude.ai Web, Desktop, or Cowork.

Claude Code plugin setup guide

Install NotFair in Claude Code via the toprank plugin marketplace.

Codex MCP setup guide

One-line install of the NotFair MCP for OpenAI's Codex CLI.

Pricing

Free to connect. Paid plans for higher usage and team features.