NotFairNotFair
Start now

Integration · Windsurf × WordPress

Run WordPress inside Windsurf

NotFair connects Windsurf to live WordPress through the same hosted MCP endpoint used across the product. Connected sites, posts, pages, media, settings, and change receipts.

Supported
Hosted MCP URL https://notfair.co/api/mcp/notfair — the same endpoint as every other NotFair platform
86 WordPress tools
Writes follow this platform's real lifecycle — not Google Ads undo copied onto WordPress

Connect your WordPress account

Authorize once at notfair.co — then open Windsurf and start asking real questions about your account.

Connect WordPress

Setup

Connect Windsurf in three steps

Windsurf uses NotFair's hosted Streamable HTTP endpoint. NotFair uses the installed WordPress plugin and a workspace integration token. There is no user-facing token rotation.

  1. 1. Open Windsurf's MCP config

    Open the Windsurf command palette and run "Open MCP Config", or edit ~/.codeium/windsurf/mcp_config.json.

  2. 2. Add NotFair

    Add the hosted server under mcpServers.

    {
      "mcpServers": {
        "NotFair-WordPress": {
          "url": "https://notfair.co/api/mcp/notfair"
        }
      }
    }
  3. 3. Authorize WordPress

    Open /manage-ads-accounts/wordpress on notfair.co, complete the hosted connection, and select the accounts or properties Windsurf may use.

Capabilities

What Windsurf can do with NotFair

Read live WordPress data

Connected sites, posts, pages, media, settings, and change receipts.

Counted tool surface

86 WordPress tools, measured from the production registrar and guarded by a drift test.

Hosted credentials

NotFair uses the installed WordPress plugin and a workspace integration token. There is no user-facing token rotation.

Platform-true writes

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. HTML is sanitized and does not execute scripts. restoreChange does not undo external hook side effects. MCP and SEO tokens can be removed independently.

Example workflows

Prompts that lead to real account work

Site inventory

List connected WordPress sites and their siteIds.

Explicit routing before any publish.

Read before edit

Read the homepage page, including its version, before proposing an edit.

expectedVersion in hand.

Publish preview

Preview publishing sanitized HTML at /test/t1.html. Do not execute until I approve.

A staged publishHtml. restoreChange only works while the resource is unchanged.

Why NotFair for Windsurf + WordPress

The hosted MCP endpoint is the same. The WordPress contract is not. NotFair keeps tool counts, OAuth, and write limits honest for this platform.

  • 86 WordPress tools — not a vendor-wide total reused as a WordPress count
  • NotFair uses the installed WordPress plugin and a workspace integration token. There is no user-facing token rotation.
  • 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 remote endpoint in Claude, Codex, Cursor, Windsurf, Gemini CLI, and OpenClaw

FAQ

Common questions about using Windsurf with Google Ads through NotFair.

Yes. NotFair's hosted MCP endpoint is the same across clients. Windsurf speaks MCP and can call the same tools. WordPress.com documents a hosted MCP for paid plans / Jetpack AI or Complete. Automattic also publishes remote MCP repositories.

restoreChange works when the resource is still unchanged. That is not Google Ads impact review.

NotFair advertises 86 WordPress tools.