NotFairNotFair
Start now

Setup guide · OpenAI Codex CLI

WordPress Codex MCP

Add NotFair's WordPressMCP to OpenAI's Codex CLI in under a minute. One terminal command wires up WordPress access.

Free · No credit card · 1-minute setup

How to install

Add NotFair WordPress to Codex in 3 steps

1

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.

2

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-WordPress --url https://notfair.co/api/mcp/notfair
3

Ask Codex about your ads

Try a prompt like:

List connected WordPress sites and their siteIds. Read the homepage including its version before proposing an edit.

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

Ready to wire up Codex for WordPress?

NotFair uses the installed WordPress plugin and a workspace integration token. There is no user-facing token rotation. Then run the one-liner in your terminal.

FAQ — NotFair WordPress for Codex

Installing and using the NotFair WordPress MCP inside OpenAI's Codex CLI.

It's an MCP integration for OpenAI's Codex CLI. Once added, Codex can use NotFair's 86 WordPress tools against live WordPress data. Updates use expectedVersion. Writes wait for workspace-role permission and a stable requestId. restoreChange reverses a supported mutation when getChange says the resource is unchanged.

Same backend, different client. The Codex CLI calls the NotFair MCP server using OpenAI's MCP support. Claude's connector and Claude Code call the same server from Anthropic's clients. Capabilities are identical.

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

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

Updates use expectedVersion. Writes wait for workspace-role permission and a stable requestId. restoreChange reverses a supported mutation when getChange says the resource is unchanged.