Is there an official WordPress MCP?
Yes. WordPress.com documents a hosted MCP at public-api.wordpress.com for paid plans / Jetpack AI or Complete. Automattic also publishes remote MCP repositories for self-hosted and WordPress.com sites.
Vendor-authored, source-reviewed comparison · 2026
Best WordPress MCP servers, compared on publish depth, media, and restore
WordPress.com publishes an official MCP. Compare monthly operations, WordPress-specific tool count, media and exact-path HTML publishing, and whether supported changes can be restored.
- Published
- · September 17, 2026
- Last verified
- · September 17, 2026
- Products reviewed
- · 4
- Author
- · NotFair product team
Our verdict
Best for operators who want a plugin-connected WordPress MCP with restoreChange
NotFair uses the installed NotFair WordPress plugin and a counted tool surface covering posts, pages, media, exact-path HTML, settings, and restoreChange. MCP and SEO connections can be removed independently.
- Monthly operations
- Workspace plans
- Not a metered ad-network quota platform
- WordPress tools
- 86
- Reads, writes, restore
- Publish depth
- Posts, pages, HTML
- publishHtml at exact paths
- Restore
- restoreChange
- When the resource is unchanged
Comparison matrix
Publish depth, media, and restore
Ad-creative columns do not map cleanly here. The matrix compares media/HTML publishing and restore. “Not published” means the vendor’s public documentation does not support a more specific claim.
| Server | Operations / month | WordPress tools | Media / HTML publishing | Restore supported changes | Write access |
|---|---|---|---|---|---|
NotFair Our verdict | Free: 300/month after 7 unlimited days. Growth: unlimited ($99/mo monthly, or $950/yr (~$79/mo) annually). This platform is not one of the metered ad-network quota platforms.Usage source | 86 WordPress tools | Yes — uploadMedia for bounded images/files, plus publishHtml for sanitized exact-path HTML (rootId site-pages).Capability source | Yes — restoreChange reverses a supported mutation when getChange says the resource is unchanged. It does not undo external hook side effects. | Yes — posts, pages, media, terms, users, design, settings, plugins, themes, HTML, jobs |
WordPress.com official MCP | No NotFair-style SaaS cap is published; access follows WordPress.com / Jetpack plan eligibility. | Not published as a counted inventory on the public MCP docs used for this row | Official WordPress.com MCP documents site resources through wpcom MCP; exact media/HTML contracts follow those docs.Capability source | A NotFair-style restoreChange tool is not documented on the public pages used here. | Yes — WordPress.com MCP exposes mutating site resources as documented for eligible plans |
Automattic / mcp-wordpress-remote | No software subscription cap; usage remains subject to the WordPress site you operate. | Tool inventory is whatever the current repository exposes; this row does not invent a count | Repository documents WordPress REST resources including media; exact HTML-at-path behavior is not assumed. | A counted restore tool matching NotFair restoreChange is not claimed from the README used here. | Yes — mutating WordPress REST resources as documented in the repository |
Automattic / mcp-wpcom-remote | No software subscription cap; access follows WordPress.com auth and plan rules. | Tool inventory is whatever the current repository exposes; this row does not invent a count | Repository documents WordPress.com MCP resources; media/HTML contracts follow that README. | A counted restore tool matching NotFair restoreChange is not claimed from the README used here. | Yes — WordPress.com resources as documented in the repository |
NotFair WordPress media upload accepts bounded base64. publishHtml is sanitized HTML without a theme wrapper; executable scripts are rejected. restoreChange does not undo external hook side effects.
Operating model
Setup, safeguards, site routing, and client reach
| Server | Best for | Delivery | Credentials | Safety lifecycle | Multi-account | Clients |
|---|---|---|---|---|---|---|
NotFair Our verdict | Operators who want a plugin-connected WordPress MCP with exact-path HTML and restore | Hosted remote MCP + installed NotFair plugin | Existing workspace integration token; no user-facing rotation | Workspace-role gates, expectedVersion, requestId retries, and restoreChange. HTML is sanitized; scripts are rejected. No Google Ads impact snapshot. | Workspace-scoped connected websites with explicit siteId on every operation | Claude Web/Code, Codex CLI, Cursor, OpenClaw, Hermes |
WordPress.com official MCP | WordPress.com or Jetpack sites that want Automattic’s hosted MCP | WordPress.com-hosted remote MCP | OAuth 2.1 through WordPress.com; documented on paid plans / Jetpack AI or Complete | WordPress.com OAuth and plan gating; NotFair plugin restoreChange is not assumed | WordPress.com sites authorized for the authenticated user | MCP clients that can connect to public-api.wordpress.com |
Automattic / mcp-wordpress-remote | Developers who want Automattic’s remote MCP for a self-hosted WordPress site | Self-hosted / remotely connected open source | WordPress application passwords or the repository’s documented auth | Operator-owned WordPress auth; NotFair plugin restoreChange is not assumed | The WordPress site(s) the operator configures | MCP clients that can run or reach the remote server |
Automattic / mcp-wpcom-remote | Developers who want Automattic’s WordPress.com-oriented remote MCP | Self-hosted / remotely connected open source | WordPress.com OAuth as documented in the repository | WordPress.com OAuth as implemented by Automattic; NotFair plugin restoreChange is not assumed | WordPress.com sites authorized for the authenticated user | MCP clients that can run or reach the remote server |
NotFair is the publisher of this comparison and is therefore not a neutral party. Google Ads impact review is not claimed for WordPress. restoreChange requires the resource to be unchanged since the original mutation.
Testing method
A benchmark that can be rerun
We review the connection boundary, tool surface, write contract, site routing, and recovery path. Marketing claims without a public document, schema, or observable flow are not treated as verified capabilities.
01
Monthly capacity
How many MCP operations can the user run each month, what consumes quota, and what happens at the limit?
02
Tool depth
How many tools are WordPress-specific rather than a cross-platform total?
03
Publish depth
Can the agent create posts, pages, media, and exact-path HTML?
04
Connection
Can a non-developer connect a WordPress site without building OAuth infrastructure?
05
Useful reads
Can the agent inspect sites, content, media, settings, and change receipts?
06
Safe writes
Are mutations versioned, role-gated, and bound to a stable requestId?
07
After the write
Can restoreChange reverse a supported mutation when the resource is unchanged?
08
Site routing
Can the agent list connected sites and target an explicit siteId?
09
Client reach
Does the same remote endpoint work in the AI workspace the operator already uses?
Test boundary
NotFair was verified against its production registerWordPressTools() surface and plugin connection flow. Competitor rows are based on linked public documentation or source code; no competitor site was connected and no competitor write was executed for this review.
Decision guide
Choose by operating model
Choose NotFair
You want a plugin-connected WordPress MCP with exact-path HTML, media uploads, and restoreChange.
Choose WordPress.com official
You already run WordPress.com or Jetpack AI/Complete and want Automattic’s hosted MCP.
Choose mcp-wordpress-remote
You want Automattic’s self-hosted remote MCP for a WordPress site you operate.
Choose mcp-wpcom-remote
You want Automattic’s WordPress.com-oriented remote MCP rather than a NotFair plugin token.
NotFair production path
Inspect → edit with version → approve → restore if still unchanged
- listSites returns explicit siteIds; every website operation requires one.
- Read getResource or readFile first and pass expectedVersion on updates.
- publishHtml creates sanitized standalone HTML at an exact path (rootId site-pages).
- Writes wait for workspace-role permission and a stable requestId.
- getChange then restoreChange undoes a supported mutation if the resource is unchanged.
- HTML is sanitized and does not execute scripts. MCP and SEO tokens can be removed independently.
Remote endpoint
https://notfair.co/api/mcp/notfairPublic verification prompts
Use the same prompts on every server
01
Show my plan, monthly operation limit, operations used, and operations remaining.
02
List every WordPress-specific tool available in this connection; exclude tools for other platforms.
03
List connected WordPress sites and their siteIds.
04
Read the homepage page, including its version, before proposing an edit.
05
Upload a supplied PNG and return the media ID.
06
Preview publishing sanitized HTML at /test/t1.html. Do not execute until I approve.
07
After a write, return the requestId, change receipt, and restore eligibility.
08
Show how restoreChange would reverse that mutation if the resource is still unchanged.
09
Confirm MCP and SEO connections can be removed independently.
WordPress MCP server FAQ
Direct answers for buyers comparing NotFair’s plugin MCP with Automattic’s official and remote servers.
How many WordPress tools does NotFair expose?
NotFair advertises 86 WordPress tools, measured from registerWordPressTools() and guarded by a drift test.
Can NotFair publish a page at an exact URL?
Yes. publishHtml with rootId site-pages writes sanitized HTML at a path such as test/t1.html relative to the website home URL.
Was every competitor tested against a live site?
No. This review combines public documentation with live production verification of NotFair.
From comparison to first write
Connect once. Audit first. Approve only what you understand.
The free plan includes seven days of unlimited access, then 300 MCP operations each month. No credit card.