Google Ads MCP server

Google Ads MCP Server for Claude, Codex, Hermes, and OpenClaw

Q: What is the NotFair Google Ads MCP server?

It's a hosted Model Context Protocol server that exposes your Google Ads account to MCP-compatible AI clients. Read tools provide live campaign context for diagnosis; write tools propose fixes that you approve in chat.

NotFair is a hosted Model Context Protocol server at https://notfair.co/api/mcp/google_ads. NotFair connects your own Google Ads account to Claude, Codex, Hermes, OpenClaw, and other MCP clients so they can inspect campaigns, find issues, and prepare approved changes through the Model Context Protocol.

Independent tool · OAuth 2.0 · Read live data, approve every write

New to MCP? Read the spec at modelcontextprotocol.io.

MCP server comparison

Hosted execution layer, not just a read-only wrapper

The official Google Ads MCP is useful for developers who want to self-host read-only access. NotFair is built for operators who want OAuth setup, live diagnosis, and approval-gated writes from their AI client.

Factor

Official / self-hosted MCP

NotFair hosted MCP

Setup

Bring a Google Cloud project, developer token, OAuth credentials, local runtime, and client config.

Use one hosted endpoint, sign in with Google, pick accounts, and add the connector to your AI client.

Actions

Best fit for read-only reporting and custom GAQL exploration.

Read live data, diagnose issues, stage writes, and approve changes such as negatives, bids, budgets, and campaign state.

Control

You own the infrastructure and token setup.

NotFair handles OAuth and API plumbing while keeping account writes explicit, reviewable, and traceable.

Connector setup

One hosted connector, multiple AI clients

Use the same NotFair Google Ads MCP endpoint across Claude.ai, Claude Code, OpenAI Codex CLI, Hermes Agent, OpenClaw, Cursor, Cline, and custom MCP clients.

OAuth 2.0 (recommended)

Drop into ~/.cursor/mcp.json (Cursor), the Cline settings JSON, or any client that takes the standard MCP config schema. The client opens a browser for sign-in.

json

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

Tools exposed

What your AI client can read, diagnose, and stage

Read tools provide live account context. Write tools stage campaign edits for review — every write requires explicit human approval before it hits the Google Ads API.

Tool	Type	What it does
`runScript`	Read	Sandboxed JS with GAQL fan-out — every analytical read goes through this one tool.
`getRecommendations`	Read	Google's optimization suggestions with estimated impact.
`getKeywordIdeas`	Read	Keyword Planner search volume, competition, and CPC estimates.
`getChanges`	Read	NotFair's own change log — undoable with one call.
`reviewChangeImpact`	Read	Before/after impact analysis on recent edits.
`getResourceMetadata`	Read	GAQL schema discovery for custom queries.
and more account, keyword, search-term, ad, and change-history tools

Ready to wire up your client?

Or follow a per-client setup guide

FAQ — NotFair MCP server

Common questions about authenticating, configuring, and using the NotFair Google Ads MCP server.

What is the NotFair Google Ads MCP server?

It is a hosted Model Context Protocol server that exposes your Google Ads account to MCP-compatible AI clients. Read tools provide live campaign context for diagnosis; write tools stage fixes that you approve before they run.

Which MCP clients are supported?

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

Do I need to self-host anything?

No. The server is hosted at https://notfair.co/api/mcp/google_ads. You just point your client at it and authenticate.

How does authentication work?

OAuth 2.0 with PKCE is the recommended flow — 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.

Is the MCP server free?

Yes. Connecting and running a free Google Ads audit is free with no credit card. Paid plans unlock higher usage limits and team features.

Can the AI write to my account through this server?

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

Per-client setup guides

Walkthroughs for each supported client.