Integration · Grok Bot × WordPress
Run WordPress inside Grok Bot
NotFair connects Grok Bot to live WordPress through the same hosted MCP endpoint used across the product. Connected sites, posts, pages, media, settings, and change receipts.
Connect your WordPress account
Authorize once at notfair.co — then open Grok Bot and start asking real questions about your account.
Setup
Connect Grok Bot in three steps
Grok Bot 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. Open the Grok Bot marketplace
Open Grok Bot and select Plugins in the sidebar to open the Marketplace. On mobile, tap your avatar and choose Plugins.
2. Search for notfair
Type notfair in the marketplace search box, open the NotFair plugin, then choose Add and complete Authorize or Authenticate in the browser. There is no Grok Bot CLI one-liner.
3. Authorize WordPress
Open /manage-ads-accounts/wordpress on notfair.co, complete the hosted connection, and select the accounts or properties Grok Bot may use.
Capabilities
What Grok Bot 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 Grok Bot + 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, Grok Bot, Cursor, Windsurf, Gemini CLI, and OpenClaw
FAQ
Common questions about using Grok Bot with Google Ads through NotFair.
Yes. NotFair's hosted MCP endpoint is the same across clients. Grok Bot 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.
Other integrations
Switching clients, or curious how this compares?
ChatGPT + Google Ads
NotFair connects ChatGPT to live WordPress through the same hosted MCP endpoint used across the product. Connected sites, posts, pages, media, settings, and change receipts.
Claude Code + Google Ads
NotFair connects Claude Code to live WordPress through the same hosted MCP endpoint used across the product. Connected sites, posts, pages, media, settings, and change receipts.
Cursor + Google Ads
NotFair connects Cursor to live WordPress through the same hosted MCP endpoint used across the product. Connected sites, posts, pages, media, settings, and change receipts.