NotFair

A Google Ads connector for the AI clients your team already uses

NotFair gives Claude, Codex, Cursor, Cline, and custom MCP clients one hosted Google Ads connector with OAuth, live campaign reads, and approval-gated writes.

Use one hosted connector URL instead of building Google Ads API auth yourself

Support Claude, Codex, Cursor, Cline, and any client that speaks MCP Streamable HTTP

Connect once, then ask your agent to inspect campaigns and prepare reviewed fixes

Ready to connect your Google Ads account?

Start with the main product flow, then use your preferred AI client to inspect campaigns and review optimization ideas.

Connect Google Ads

Connector vs MCP server vs plugin

The connector is the user-facing install path. The MCP server is the protocol endpoint behind it. Plugins and setup guides help specific clients discover the same NotFair tools faster.

The shortest path to a useful first run

Connect Google Ads, open your AI client, and ask for a read-only diagnosis before approving any edits. The first successful write should usually be narrow: a negative keyword, a bid adjustment, or a campaign-state change you can review.

What the connector actually does

The NotFair connector is the hosted bridge between your Google Ads account and an AI client. You authorize with Google OAuth, NotFair handles the Google Ads API side, and your client gets a structured tool surface for account reads and approved writes. The goal is to avoid the slow custom path of creating a Google Cloud project, applying for a developer token, mapping Google Ads resources, and maintaining a private MCP server.

OAuth connection for the Google account that can access the ad accounts
Account discovery across accessible customer IDs and manager accounts
Structured read tools for campaigns, ad groups, keywords, search terms, metrics, and changes
Approval-gated write tools for optimization actions

Which client should use it

Use the connector when you want the same Google Ads account available inside different AI clients. Claude is the clearest starting point, Codex is useful for code-heavy workflows, Cursor and Cline fit IDE-native work, and custom MCP clients can call the same hosted endpoint. The connector page is about that practical setup path, not a general definition of MCP.

Claude and Claude Code for account diagnosis and operator workflows
Codex CLI for scripted analysis, local reports, and repeatable account tasks
Cursor, Cline, and custom MCP clients for developer-led integrations

First-run checklist

A useful connector setup is not done when OAuth succeeds. It is done when the client can list accounts, inspect a real campaign, produce a diagnosis, and prepare one reviewable action. This page should help a user get to that point without wandering through generic docs.

Confirm the expected Google Ads customer ID appears
Run a read-only campaign performance query for the last 30 days
Ask for one optimization recommendation with the evidence attached
Approve only a narrow, reversible first write after reviewing the draft

Troubleshooting the common failure modes

Connector failures are usually not strategy problems. They are setup problems: the wrong Google account was authorized, the user has access to a manager account but not the client account they expected, the AI client has not refreshed its tool list, or the client is configured for a different MCP transport. The page should make those checks explicit because they are the difference between a visit and a successful activation.

If no accounts appear, check Google Ads access and manager account permissions
If tools do not appear, refresh or restart the AI client after adding the connector
If writes fail, verify the account role and start with a read-only prompt
If the client rejects the URL, confirm it supports remote MCP Streamable HTTP

Example workflows

Prompts that lead to real account work

Account discovery

“List the Google Ads accounts I can access, show customer IDs, and identify which accounts had spend in the last 30 days.”

Proof that OAuth and account access are working before any optimization begins.

Connector smoke test

“Pull campaign spend, conversions, CPA, and status for the last 30 days. Keep this read-only and summarize the highest-risk campaign.”

A real campaign diagnosis that confirms the connector is useful, not merely installed.

First reviewed write

“Find one low-risk negative keyword candidate from recent search terms and draft the exact change for approval. Do not apply it until I confirm.”

A narrow activation path from connector setup to a reviewable optimization write.

FAQ

Short answers to the most common questions around this workflow.

What is the NotFair Google Ads connector?

It is the hosted MCP connection between your Google Ads account and AI clients like Claude, Codex, Cursor, and Cline.

Do I need a Google Ads developer token?

No. NotFair handles the Google Ads API developer-token side. You authorize access with the Google account that can see your ad accounts.

Can the connector make campaign changes?

Yes, but writes are designed to be reviewable. The agent can draft changes and you approve them before they are sent to Google Ads.

Use these pages to move from the exact search intent into the broader NotFair workflow.