Grok Bot · WordPress
Run WordPress inside Grok Bot from the Grok Bot marketplace
Install NotFair from the Grok Bot marketplace, connect WordPress in your NotFair workspace, and Grok Bot can call the same hosted MCP tools as Claude and Codex. 86 WordPress tools. Connected sites, posts, pages, media, settings, and change receipts.
86 WordPress tools
Turn Grok Bot Into Your Marketing Engine
Bring ads, search, analytics, CRM, and WordPress into your AI client. Explore each integration to see its supported actions.
Choose a platform
Choose your AI client
Go to the Grokbot Marketplace
Search for notfair
Add and complete OAuth
How it works
Marketplace install, then an approved WordPress change
Connect WordPress
NotFair uses the installed WordPress plugin and a workspace integration token. There is no user-facing token rotation.
Install NotFair in Grok Bot
Open Grok Bot, choose Plugins to open the Marketplace, search for notfair, then Add and complete Authorize or Authenticate in the browser. Confirm the plugin appears under Installed.
Ask, then approve writes
Grok Bot can inspect Connected sites, posts, pages, media, settings, and change receipts. Writes wait for your confirmation. HTML is sanitized and does not execute scripts. restoreChange does not undo external hook side effects. MCP and SEO tokens can be removed independently.
What the client can do
Posts, pages, media, and exact-path HTML
WordPress.com has an official hosted MCP. NotFair is the plugin-connected option with counted tools, sanitized publishHtml at exact paths, and restoreChange.
Site routing
listSites returns explicit siteIds. Every website operation requires one.
Versioned edits
Read getResource or readFile first and pass expectedVersion on updates.
Exact-path HTML
publishHtml writes sanitized standalone HTML at a path such as test/t1.html (rootId site-pages).
Restore when unchanged
getChange then restoreChange undoes a supported mutation if the resource has not changed since. External hook side effects are not undone.
WordPress tools
86 WordPress tools the client can call
The advertised count is measured from registerWordPressTools() and guarded by a drift test. The table below is a representative subset.
| Tool | Type | Description |
|---|---|---|
listSites | read | Connected WordPress websites and siteIds. |
getResource | read | Read a post, page, or other resource including its version. |
uploadMedia | write | Bounded base64 media upload. |
publishHtml | write | Sanitized HTML at an exact path. Scripts are rejected. |
getChange | read | Change receipt and restore eligibility. |
restoreChange | write | Reverse a supported mutation if the resource is still unchanged. |
Full tool surface: /wordpress-mcp.
WordPress + Grok Bot FAQ
Direct answers for operators connecting WordPress to Grok Bot through NotFair.
Connect WordPress at notfair.co, install the NotFair plugin from the Grok Bot marketplace, then ask Grok Bot to inspect live data. Writes stay staged until you approve them.
No. Grok Bot setup is marketplace install: Plugins → search notfair → Add → Authorize or Authenticate. NotFair does not invent a terminal one-liner for Grok Bot.
Only with explicit approval. 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.
WordPress.com documents a hosted MCP for paid plans / Jetpack AI or Complete. Automattic also publishes remote MCP repositories.
Related pages
Keep evaluating the same connection.
WordPress MCP
Tool surface, endpoint, and 86 WordPress tools.
WordPress for Claude
Same hosted MCP endpoint on Claude's first-class landing.
WordPress for Codex
Codex CLI product landing for the same tools.
WordPress for ChatGPT
ChatGPT-style workflows through an MCP-capable OpenAI client.
Grok Bot setup
Marketplace install steps for the NotFair Grok Bot plugin.
Compare WordPress MCP servers
Sourced benchmark with public verification prompts.
WordPress write safety
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.
Connect WordPress to Grok Bot
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.