Google Ads MCP server

Hosted Google Ads MCP server

NotFair ships a hosted Model Context Protocol server at https://notfair.co/api/mcp. Drop the generic config below into any MCP-compatible client — auth via OAuth or Bearer token.

Free · OAuth 2.0 · No credit card

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

Generic MCP config

Two configs that work in any MCP client

For client-specific walkthroughs (Claude.ai, Claude Code, Codex), see the per-client setup guides linked below.

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": {
      "url": "https://notfair.co/api/mcp"
    }
  }
}

Bearer token (for clients without OAuth)

Pass an Authorization header instead. The token below is your personal API key.

Get your API key

Sign in with Google to generate your personal API key. We'll substitute it into the Bearer config below automatically.

json
{
  "mcpServers": {
    "notfair": {
      "url": "https://notfair.co/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ADSAGENT_API_KEY"
      }
    }
  }
}
Treat the API key like a password — don't commit it to source control.

Tools exposed

What your AI client can read and change

Read tools provide live account context. Write tools propose changes — every write requires explicit human approval before it hits the Google Ads API.

ToolType
runScriptRead
getRecommendationsRead
getKeywordIdeasRead
getChangesRead
reviewChangeImpactRead
getResourceMetadataRead
and 60+ more

Ready to wire up your client?

Sign in with Google to generate your credentials, then paste a config above into your MCP 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's a hosted Model Context Protocol server that exposes your Google Ads account to MCP-compatible AI clients. Read tools provide live campaign context; write tools propose changes that you approve in chat.

Which MCP clients are supported?

Any client 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 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. 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.