Google Ads MCP by NotFair

Find what's wrong. Fix it from your AI agent.

NotFair connects Claude, OpenAI Codex, Cursor, Cline, OpenClaw, Hermes, and other MCP-compatible agents to live Google Ads data. Your agent can diagnose account issues, draft fixes, and execute campaign changes only after you approve.

This repo is the public setup guide for NotFair's hosted Google Ads MCP. You do not need to clone this repo, create Google API credentials, or run a local server.

Claude setup

For Claude users, setup is just one URL:

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

Open Claude settings.
Go to Connectors.
Add a custom connector.
Paste https://notfair.co/api/mcp/google_ads.
If Claude asks for a name, use NotFair-GoogleAds.
Start a new Claude chat and ask your first Google Ads question.
Claude will prompt you to authorize NotFair inside that chat conversation.
Sign in with the Google account that has Google Ads access.

You do not need to create a Google Ads developer token, OAuth app, API key, or local MCP server.

First prompt:

Find keywords that have not been converting.

flowchart LR
  A[You paste the NotFair MCP URL] --> B[Claude]
  B --> C[Start a new chat]
  C --> D[Ask a Google Ads question]
  D --> E[OAuth prompt appears in chat]
  E --> F[Google Ads account access]
  F --> G[Live answer, fix draft, approval request]

Other clients

Codex, Cursor, Cline, OpenClaw, Hermes, and other MCP clients use the same hosted server URL:

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

OpenAI Codex

Run:

codex mcp add NotFair-GoogleAds --url https://notfair.co/api/mcp/google_ads

Then follow the browser sign-in flow.

Cursor, Cline, OpenClaw, Hermes, and other MCP clients

Use this MCP server config anywhere your client accepts MCP JSON:

{
  "mcpServers": {
    "NotFair-GoogleAds": {
      "url": "https://notfair.co/api/mcp/google_ads"
    }
  }
}

If your agent can set up MCP servers from a prompt, use:

Connect to the NotFair Google Ads MCP at https://notfair.co/api/mcp/google_ads. Use OAuth if available. Start with a read-only Google Ads audit and wait for my approval before making any changes.

How it works

flowchart LR
  A[You] --> B[Claude / Codex / Cursor / OpenClaw / Hermes]
  B --> C[NotFair Google Ads MCP]
  C --> D[Google Ads]
  D --> C
  C --> B
  B --> E[Diagnosis, fix draft, approval request]
  E --> A

What users can ask

Use business-language prompts. You do not need to know Google Ads internals before starting.

Find what's wrong with my Google Ads account and rank fixes by wasted spend.

Find irrelevant search terms from the last 30 days. Draft negative keyword changes and wait for approval.

Compare this week to last week. Explain what changed in spend, conversions, CPA, and conversion rate.

Find campaigns where budget changes are justified. Show the math before recommending an increase.

Draft new responsive search ads for the weakest ad group. Do not publish anything until I approve.

More complete examples are in USAGE_EXAMPLES.md.

How writes stay controlled

sequenceDiagram
  participant User
  participant Agent as AI agent
  participant NF as NotFair MCP
  participant GA as Google Ads

  User->>Agent: Find wasted spend
  Agent->>NF: Read campaigns, keywords, search terms
  NF->>GA: Fetch live Google Ads data
  GA-->>NF: Results
  NF-->>Agent: Structured account data
  Agent-->>User: Findings + proposed fix
  User->>Agent: Approve this change
  Agent->>NF: Execute approved write
  NF->>GA: Apply change
  GA-->>NF: Confirmation
  NF-->>Agent: Write result
  Agent-->>User: Change applied + summary

Rules to follow:

Reads can inspect live Google Ads data after authorization.
Writes should be reviewed before they land.
Ask the agent to show the diff, expected impact, and rollback plan before approval.
Reconnect at https://notfair.co/connect if auth expires.

Troubleshooting

| Problem | Fix | | --- | --- | | The client cannot find the server | Check the URL is exactly https://notfair.co/api/mcp/google_ads. | | The agent says auth expired | Reconnect at https://notfair.co/connect, then retry. | | No Google Ads accounts appear | Sign in with the Google account that has access to the Ads customer. | | OAuth opens but setup does not finish | Remove the connector, add it again, then retry the OAuth flow. | | The agent wants to make a change too quickly | Ask it to run read-only diagnosis first and show the proposed diff before writing. |

License

This repository is open source under the MIT License.

Support

For setup help, contact tong@notfair.co.

MCP Servers