What should I ask Codex first after setup?

Start with a data-grounded audit, then move to a reviewable write: ask Codex to rank fixes by impact, find search terms to add as negatives while showing the diff first, or draft a new RSA for an ad group and wait for approval.

Setup guide · OpenAI Codex CLI

Google Ads Codex MCP

Add NotFair to OpenAI's Codex CLI in under a minute. One terminal command wires up the MCP server and walks you through OAuth — Codex then has live access to diagnose and operate your Google Ads account.

Looking for the full product overview? Start with Codex Google Ads agent, then come back here for the install command.

Free · No credit card · 1-minute setup

Terminal

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

How to install

Add NotFair to Codex in 3 steps

Install the Codex CLI

Open a terminal and install OpenAI Codex if you do not have it already. Follow the official install guide for your platform.

Add the NotFair MCP

Run this one-liner. Codex will walk you through the OAuth flow and register the NotFair MCP server automatically.

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

Ask Codex about your ads

Try a prompt like:

“Audit my connected Google Ads account and prioritize the 3 changes most likely to improve performance. For every recommendation, you must pull actual data to prove or disprove your hypothesis before suggesting it. Then, show the hard evidence, expected upside, and the exact change you recommend I approve, and create a live dashboard for me for ongoing monitoring”

Codex will call NotFair tools to read your account and respond with specific, data-backed insights.

First prompts

Move from setup to approved writes

After the MCP is connected, start with a read-only diagnosis, then ask Codex to draft a specific change and show the diff before writing.

Audit my Google Ads account and rank fixes by impact.

Find search terms I should add as negatives, but show me the diff before writing.

Draft a new RSA for this ad group and wait for approval.

Explain what changed before CPA spiked this week.

Ready to wire up Codex?

Or use Claude Code instead

FAQ — NotFair for Codex

Everything you need to know about installing and using the NotFair MCP inside OpenAI's Codex CLI.

What does the NotFair Codex MCP do once installed?

It exposes a set of MCP tools to Codex that let it read your Google Ads campaigns, search terms, and spend, and propose write actions you approve in chat. For the full capability overview see the Google Ads × Codex landing page at /google-ads-codex.

How long does setup take?

Under a minute. Run a single `codex mcp add NotFair-GoogleAds --url https://notfair.co/api/mcp/google_ads` command in your terminal — Codex walks you through the OAuth flow and registers the MCP automatically.

Do I need to write any code?

No. One terminal command sets everything up. There are no JSON config edits, no environment variables, and no scripts to run.

Which terminals and shells does it work in?

Any shell that can run Node.js — bash, zsh, fish, PowerShell, and others. The Codex CLI itself is a Node.js process, so the NotFair MCP inherits full shell compatibility. If Codex runs, NotFair runs.

Does it work with WSL on Windows?

Yes. Install the Codex CLI inside your WSL environment and run the same one-liner. The MCP server and OAuth flow work identically on WSL 1 and WSL 2. Native Windows (outside WSL) depends on Codex CLI's Windows support status.

Can I use it inside an IDE like VS Code?

Codex is a terminal-first tool, but you can run it in any integrated terminal — VS Code's built-in terminal, JetBrains terminals, or any other IDE that embeds a shell. The NotFair MCP works wherever the Codex CLI runs.

Related guides

Explore the rest of the NotFair setup options.