Comparisons
WordPress MCP alternatives, compared with sources. No winner theatre.
The main WordPress MCP alternatives are the official MCP Adapter, WordPress.com's hosted MCP, Elementor's and WooCommerce's own MCP, MCP built into a host, and self-hosted plugins such as Respira, Easy MCP AI, EMCP and Royal MCP. Each page below puts one of them next to GoBuildWP, with dated vendor sources and a test you can repeat on staging.
Choose a route
Three questions before comparing WordPress MCP alternatives
- Is the site on WordPress.com, Jetpack-connected, hosted on a vendor-specific platform or standalone self-hosted?
- Do you need one plugin’s operations or work across builders, forms, SEO and commerce?
- Which actions need human approval, and exactly which retained data can be restored?
The cards below point to dated vendor documentation and selected source checks. None represents a matched runtime benchmark. Open each comparison for edition, default, scope and unknowns; the market map owns the selected feature matrix and additional alternatives.
Official routes
When the platform or plugin vendor ships its own MCP
These routes are owned by WordPress, Automattic, Elementor and WooCommerce. GoBuildWP can run beside them; the pages explain what each layer owns.
Elementor MCP vs GoBuildWP
Elementor's own MCP, documented for Atomic V4 pages; official launch reported 23 September, next to GoBuildWP's classic and atomic Elementor abilities.
Read the comparisonWordPress MCP Adapter vs GoBuildWP
The official protocol bridge for the Abilities API, now v0.7.0 in the WordPress.org directory and still not in core, versus a packaged server with sign-in, confirmation, a log and undo.
Read the comparisonWooCommerce MCP vs GoBuildWP
WooCommerce's native abilities, still a Developer Preview for products and orders, versus GoBuildWP's free store reads and full Pro module.
Read the comparisonWordPress.com MCP vs GoBuildWP
Automattic's hosted route for WordPress.com and Jetpack sites, versus an endpoint that runs inside your own WordPress install.
Read the comparison
Head-to-head with plugins
Third-party WordPress MCP servers, one at a time
Each page has a feature table with dated sources and route-specific limits, plus a staging protocol for assessing fit.
Respira vs GoBuildWP
Duplicate-first editing across 17 builders, versus supported before-image recovery, scoped credentials and a Free tier.
Read the comparisonEasy MCP AI vs GoBuildWP
Two free servers: WooCommerce and SEO data tools, versus Elementor editing, opt-in person confirmation and supported recovery.
Read the comparisonEMCP Tools vs GoBuildWP
Two self-hosted plugins with documented native edits and session recovery; compare approval routes, builder subsets and direct versus optional Cloud costs.
Read the comparisonWPVibe vs GoBuildWP
A hosted relay with daily call caps, versus a server inside WordPress, reached directly or through optional Cloud, with configurable request limits and supported before-image recovery.
Read the comparisonRoyal MCP vs GoBuildWP
Undo tokens, WebMCP and a hash-chained log, versus Free builder editing and bounded recovery.
Read the comparisonAI Engine MCP vs GoBuildWP
An AI suite with an MCP server inside, versus a dedicated server with builders and undo.
Read the comparisonminiOrange Secure MCP vs GoBuildWP
DLP, prompt-injection checks and request quotas, versus site-enforced profiles, supported undo and configurable request limits.
Read the comparisonFlex MCP vs GoBuildWP
Two session undos with redo, documented conflict checks and restore limits, plus Flex's scheduled AI tasks.
Read the comparisonNovamira vs GoBuildWP
Raw PHP, database and file access for staging, versus governed abilities and supported recovery boundaries.
Read the comparison
Weighing more than one plugin? The best WordPress MCP server comparison puts every option on one table. Running several sites, GoBuildWP Cloud adds reviewed bulk plugin updates with backup options, backup status for every site and one safety policy across sites.
Host-built MCP
When the hosting company runs the MCP server
Some hosts now ship MCP with the plan. They are convenient on that host and unavailable anywhere else, and they differ a lot in what they can touch.
InstaWP InstaMCP
A per-site MCP server switched on from InstaWP hosting, with token scopes, skills and memory. Only for sites hosted there.
Read the comparisonWP Engine MCP server
Part of WP Engine's Smart Search AI: a generated server URL that lets AI tools read and search a site's approved, published content. It does not edit the site.
Vendor pageHostinger WordPress MCP
Hostinger's managed WordPress plans connect its own Hostinger Agent. For Claude Desktop, its tutorial of 15 September 2026 installs an MCP server from Automattic with an Application Password.
Vendor page
Retired route
Still running Automattic's wordpress-mcp?
GitHub shows the repository archived by its owner on 17 September 2026, and its README asks people not to use it for new installations. Sites that still run it need a new route; the comparison below maps each of its features.
Specialists
MCP servers built around one plugin
A store extension and a cache plugin, each with its own MCP surface, compared with a server that spans the whole site.
MCP for WooCommerce by W7S vs GoBuildWP
A paid WooCommerce Marketplace extension, versus a WordPress-wide server with a WooCommerce module.
Read the comparisonxSpeed Cache vs GoBuildWP
A cache plugin with its own MCP optimise loop, versus coordinating the performance stack a site already runs.
Read the comparison
How we compare
Source it. Date it. Test it.
GoBuildWP does not score itself or declare a universal winner. Your site, its plugins, the connected WordPress user and the AI client are the final test. Read the review method.
Source it
Every competing row links to the vendor's own documentation, product page or WordPress.org listing. GoBuildWP rows come from the shipped, source-derived catalogue.
Date it
Each page shows when its sources were checked. A statement that was right in August can be incomplete in September.
Test it
The proposed matched staging test is one allowed read, one denied action and one supported write/restore. These are test instructions, not recorded runtime results.
Broader coverage · checked 2 October 2026
More direct connectors and builder substitutes
These primary-source additions broaden the shortlist. Priorities reflect workflow fit, not popularity. Capabilities are documented publisher claims; no matched runtime, market-share or search-ranking test was performed. This is not an exhaustive directory.
| Product and route | Documented fit | Limit or uncertainty | Primary sources |
|---|---|---|---|
| NIBWP Site plugin, skills and workflows | Broad plugin integrations, builder skills and reusable workflows. | Pro and all-skills Bundle are different offers; directory and pricing disagree on some entitlements/counts. | Directory · Pricing |
| SiteSkite Direct site MCP; separate managed fleet | Site MCP is free and accountless. Managed fleet backups, sandboxes and Studio are separate products. | Do not treat every route as a hosted relay or assume fleet features are included in site MCP. | Directory · Platform plans |
| WSP MCP Free site connector | Active free connector documenting plugin-specific operations, writes off by default and audit logs. | Release activity and documented operations do not establish successful writes or recovery on your stack. | Directory |
| PressBot MCP, admin agent and Telegram | Scheduled reviewed work. Checked public offer: 13 free read tools, 115 full tools, USD29/year for one site. | Counts use its own tool units; provider costs and the precise approval/schedule route still need review. | MCP · Pro · Changelog |
| Bricks first-party MCP Builder substitute | Shipped in Bricks 2.4 on 16 September; builder abilities and skills. | Abilities remain experimental. This is a Bricks-specific route, not a whole-site cross-builder product. | Release · Abilities docs |
Ten more assessed alternatives and their limits
| Product and route | Documented fit | Limit or uncertainty | Primary sources |
|---|---|---|---|
| Enable Abilities for MCP Ready-made abilities on the official Adapter | Free SEO, WooCommerce, LMS, Elementor and FSE capabilities. | Requires the separately installed Adapter; ready-made operations still need installed dependencies and permission checks. | Directory |
| Agent Abilities for MCP Governed capabilities | Off-by-default abilities and per-role/per-connection filtering. | Inspect actual policies and execution evidence; least privilege and audits are competed capabilities. | Directory |
| AtlasMCP Abilities discovery and REST generation | Automatic Abilities discovery; Pro broadens generated REST-to-MCP coverage. | Generated endpoint coverage differs from a tested plugin-native workflow. The directory uses its older AI Agent Hub slug. | Directory |
| Stonewright Public beta; Plugin and Direct modes | Documents inspect, approve, snapshot, write, readback and restore. | Beta modes differ; ability/tool counts cannot be added or treated as tested outcomes. | Repository |
| WP MCP (wpmcp/wpmcp) Self-hosted connector | Active releases and advertised paid plans, with snapshot/recovery workflows. | Repository and pricing disagree about Pro availability and snapshot retention; resolve before purchase. | Repository · Plans |
| WEBO MCP Core and specialist add-ons | Free core plus SEO, store and automation add-ons. | Domain query/mutate dispatchers use different count units; verify the edition and exact requested operation. | Directory · Add-ons |
| Breakdance 3.0 First-party builder connector | Agent Connector and native editing in RC1, dated 1 October. | Release candidate; Free-edition MCP entitlement was not established. | Release |
| Oxygen 6.2 First-party builder connector | Agent Connector in RC1, dated 30 September. | Release candidate; separate Oxygen Classic and inspect extension dependencies. | Release |
| OxyDance Pilot Builder editing substitute | Includes the former Bricks Pilot, counted once. | The editing FAQ limits support to static content; verify builder and dynamic-data requirements. | Product |
| Ollie MCP Pattern-led Gutenberg substitute | Experimental site-building route associated with Ollie Pro. | A free Ollie theme does not establish a free MCP entitlement. | Docs |
Use the same task matrix for every candidate: installed dependencies and edition; WordPress identity; external-client versus admin-Chat approval; native storage; readback and rendered verification; restoration limits; and plugin, fleet, client and provider costs. Approvals, undo, skills, self-hosting and native output are already competed features.
Reading the comparisons well
When another WordPress MCP route is the better choice
A comparison hub run by one of the vendors should say plainly where its own product is the wrong pick. These are the cases where the pages above point away from GoBuildWP, based on what each vendor documents.
- The site lives on WordPress.com: Automattic's hosted route is built for it, and a plugin-based server may not be installable on your plan. See WordPress.com MCP vs GoBuildWP.
- You are writing your own abilities and only need a protocol bridge: the official Adapter is the standard piece, and GoBuildWP adds a packaged server you may not need. See the Adapter comparison.
- The store runs WooCommerce Subscriptions, Bookings or Memberships: the W7S extension documents packs for those and GoBuildWP has none. See W7S vs GoBuildWP.
- You want a cache engine with its own tuning loop rather than control over the stack you already run: see xSpeed Cache vs GoBuildWP.
- The job is raw PHP, database or file work on a throwaway staging copy: a server built for unrestricted access does that with less ceremony. See Novamira vs GoBuildWP.
- The host runs PHP older than 8.0 or WordPress older than 6.9: GoBuildWP will not install there, and several routes on this page will.
Four traps when comparing MCP servers
Tool counts are the most quoted number and the least comparable one. One product counts a dispatcher that takes an action parameter as one tool; another registers each operation separately; a third generates tools from REST routes. GoBuildWP counts registered abilities, and even those are not equal in weight. Compare the operations you need, by name, not the totals.
"Undo" means different things. Some servers duplicate a page before editing it, some issue undo tokens, and GoBuildWP records a before-image per supported write in its change ledger. None of them can reverse an email already sent, a payment already refunded at the gateway or a file deleted outside WordPress. Ask each vendor what its undo restores, and test one restore yourself.
"Read-only" is enforced in different places: by the AI client's settings, by a per-key scope, by tool naming, or by the server refusing anything not annotated as read-only. Only the server-side kinds survive a client that ignores its own settings.
Documented is not tested. Every vendor row on these pages comes from vendor documentation with a date. None of it is a benchmark we ran, and that includes our own claims about other products' behaviour.
A scoring sheet you can reuse for any candidate
Run every shortlisted route through the same short sheet on one staging copy, with the same WordPress user role and the same AI client. Score each line yes, partly or no, and keep the evidence: the tool call, the result and a screenshot of the page.
- Install and connect: did it need an account, a relay or a Node.js proxy, or did the client talk to the site directly?
- Least privilege: can the connection be held to reads, and does a write attempt on that credential fail on the server?
- Your top three tasks: did each one finish in the plugin's own storage, so the page still opens in its editor?
- Review before a write: could you see the change before it ran, and can a person be required to approve the risky ones?
- Recovery: after one write, could you restore it, and did the restore say what it could not bring back?
- Cost: the plugin licence, any per-site or per-call relay fee, and the AI provider's usage, for the number of sites you actually run.
FAQ
Choosing a WordPress MCP route
What are the main WordPress MCP alternatives to GoBuildWP?
Official routes: the WordPress MCP Adapter for the Abilities API, WordPress.com MCP for hosted and Jetpack-connected sites, Elementor's official MCP and WooCommerce's native MCP. Third-party servers include Respira, Easy MCP AI, EMCP, WPVibe, Royal MCP, AI Engine, miniOrange, Flex MCP, InstaWP's InstaMCP and Novamira, plus host-built servers from InstaWP, WP Engine and Hostinger and specialists such as MCP for WooCommerce by W7S and xSpeed Cache. Automattic's older wordpress-mcp plugin was archived on 17 September 2026.
Is there a single best WordPress MCP option?
No. The routes own different layers: a protocol foundation, a hosted account route, vendor routes for one builder or store, and self-hosted servers that span several plugins. Pick the layer that matches your workflow, then run the same staging test on each candidate.
Can I run GoBuildWP next to an official MCP route?
The source uses distinct endpoints and does not require removing those routes. Coexistence on the actual installed versions remains untested here; verify required reads and a bounded staging task before deactivating another route or revoking its credential. GoBuildWP Free also records writes made through Elementor's and WooCommerce's own MCP servers in its change log, with undo where they can be put back, and on WordPress 7.1 can hold them to its safety profile.
Run the same test against every route.
Start GoBuildWP in Read Only on staging, prove one allowed read and one denied action, then compare the write, evidence and recovery path.