GoBuildWP

Native WooCommerce MCP and a Free and Pro module

WooCommerce MCP vs GoBuildWP: products and orders in core, or the whole store in Pro.

WooCommerce MCP vs GoBuildWP is a scope question. WooCommerce's docs described products and orders in Developer Preview when checked on 29 September 2026. GoBuildWP Free supports basic store reads and one product's basic fields; Pro adds variations, coupons, refunds, shipping, tax and reports. Supported before-images have recovery paths; full orders, customers, refunds and external effects are not universally reversible.

Vendor sources checked 29 September 2026, Sources

Where WooCommerce MCP leads

Why WooCommerce's own route matters

From WooCommerce's developer docs and its April 2026 blog post, read 29 September 2026.

  1. Free, inside the plugin you already run

    No extra plugin or licence: a feature flag turns it on. GoBuildWP Free reads the store and edits single products, but order writes need Pro.

  2. Built on the WordPress standard

    The abilities are registered through the Abilities API and published by the MCP Adapter, so any Adapter-aware client can reach them.

  3. The vendor's own understanding of the data

    Each ability runs its own permission check, and the docs say plainly that customer data may reach the model and advise a least-privilege user.

Where GoBuildWP leads WooCommerce MCP

What a store needs beyond two objects

GoBuildWP's side, set against what WooCommerce's docs and blog say.

  1. Refunds, coupons and reports

    WooCommerce's docs list seven abilities for products and orders. GoBuildWP has 65, 13 of them free, from variations and coupons to refunds and sales reports, and is HPOS-safe.

  2. Shipped in a release

    WooCommerce MCP is a Developer Preview. GoBuildWP's WooCommerce module is part of the released Pro plugin.

  3. A person before money moves

    GoBuildWP can require a human to approve refunds and other destructive calls. WooCommerce does not document confirmation for its abilities.

  4. A safety net under WooCommerce's own MCP

    GoBuildWP does not have to be the only route into the store. Writes made through WooCommerce's MCP server land in GoBuildWP's change log with undo where the data allows, and on WordPress 7.1 an off-by-default setting holds them to the site's safety profile and a person's approval.

  5. Inspect the recovery boundary

    Supported product field before-images and order-status snapshots have recovery paths. Status restoration can run hooks again; notifications, stock, fulfilment and gateway refunds may remain. Inspect the entry before offering recovery for a full object edit.

  6. Funnels and extension updates

    Pro reads supported FunnelKit reports and offers bounded extension updates. The default fresh-backup gate is separate from archive validation. Selected probes can trigger attempted files-only recovery, which can fail and cannot reverse database migrations or external effects.

Feature by feature

Store scope first, then the rest of the site

WooCommerce's cells come from its developer docs and the April 2026 blog post, which disagree on the number of abilities and the credential; both versions are shown.

  • Yes
  • Partly
  • No
  • Not documented
WooCommerce MCP compared with GoBuildWP, feature by feature
FeatureWooCommerce MCPGoBuildWP
WooCommercePartly: Developer Preview: products and orders only, 7 abilities in the docs and 9 in the blog.12Yes: Free: 13 reads across catalogue, orders and customers, plus a single-product editor. Pro: 52 more for coupons, refunds and reports; HPOS-safe; FunnelKit steps too.
Price and usage capsFree inside WooCommerce.2Store reads and single-product edits are free; the rest needs Pro, from $39 a year ($39–$99.99 a year, or $59.99–$199.99 once).
Where it runsInside WooCommerce core, switched on with a feature flag.1A separate plugin on the same site, with its own endpoint beside WooCommerce's.
TransportYes: stdio through WP-CLI, or remote through the mcp-wordpress-remote proxy.1Yes: Streamable HTTP straight to the site, on either MCP revision (2026-07-28, 2025-11-25), with no proxy; stdio through WP-CLI on the site's own machine.
OAuth 2.1 sign-inNot documented: Not documented by WooCommerce; its docs use Application Passwords, its April blog a REST API key.12Yes: OAuth 2.1 sign-in with PKCE and CIMD or DCR, revocable per client, so no Application Password is pasted.
Scoped, expiring credentialsNot documented: Not documented by WooCommerce.Yes: Access tokens expire, can be held to a subset of abilities, and cannot rise above a profile.
Safety profiles and read-onlyNot documented: No read-only mode documented by WooCommerce; each ability checks its own permission.1Yes: A Read Only profile lets an agent look at orders without changing them; the two looser profiles sit above it.
Writes made through other MCP serversWooCommerce MCP is one of those servers. Each of its abilities checks its own permission; a change log or undo is not documented.1Yes: Run both: GoBuildWP Free snapshots writes made through WooCommerce's own MCP server so they can be undone where the data allows, and on WordPress 7.1 an off-by-default setting holds them to the safety profile and a person's approval.
ElementorNo: Outside WooCommerce MCP's scope: store abilities only.1Yes: Free: 18 Elementor abilities, so product landing pages are in reach of the same agent.
Block editorNo: Outside the store's scope.1Yes: Core block edits complete in a browser tab, and Free edits block theme templates, Global Styles and patterns with undo; the Spectra, Kadence Blocks and GenerateBlocks modules are Pro.
AI-designed site headerNot documented: Not documented by WooCommerce MCP.Yes: Free builds the store's header for the brand, cart and menu included and one per Polylang language on a translated shop, checks it before and after saving, and keeps it undoable.
Other page buildersNo: Not a WooCommerce concern.1Yes: Shop pages built in Flatsome, Divi 5, Bricks or WPBakery are editable in Pro.
SEO pluginsNo: Store abilities only, so no SEO plugin coverage.1Yes: Free sets one product's SEO title, description and robots through AIOSEO, Yoast, The SEO Framework and others; Pro writes the rest, up to 100 posts in one call.
Form pluginsNo: Store abilities only, so no form plugins.1Yes: Free reads Contact Form 7 and three other form plugins' entries; Pro edits them, Formidable and the rest.
Updates and backups across sitesNot documented: Not documented by WooCommerce MCP.Yes: For several shops, GoBuildWP Cloud lists pending updates and backup status, free for 3 sites. Pro adds reviewed bulk plugin/theme updates with backup options and, on eligible sites, selected checks and attempted file recovery. Database changes and checkout behavior need separate verification.

Weighing more than WooCommerce MCP and GoBuildWP? 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.

Mapping the two tool sets

WooCommerce MCP's seven abilities next to GoBuildWP's equivalents

WooCommerce's developer docs, read again on 3 October 2026, still label the feature Developer Preview and list seven abilities: query, create, update and delete products, then query orders, update an order's status and add an order note. They also describe an older set derived from the REST API, marked deprecated. Here is where each of the seven lands in GoBuildWP, and which edition you need for it.

  • Query products: wppilot/woocommerce-list-products and woocommerce-get-product, both in GoBuildWP Free.
  • Update a product: woocommerce-edit-product is Free for one product's basic fields; variations, attributes and bulk price or stock changes are Pro.
  • Create or delete a product: woocommerce-create-product and woocommerce-delete-product are Pro. WooCommerce gives you both free, which is a real point in its favour.
  • Query orders: woocommerce-list-orders and woocommerce-get-order are Free, the latter returning addresses, items, totals, notes and refunds.
  • Update order status and add a note: woocommerce-update-order-status and woocommerce-add-order-note are Pro. Again, WooCommerce's core feature does this at no cost.

Order data reaches the model either way

WooCommerce's docs warn that order and customer operations can expose names, email addresses, physical addresses and payment details to the AI provider. That warning applies to GoBuildWP just as much: reading an order means the client receives the order. GoBuildWP's customer list omits password and token data, but an order read returns the addresses because that is what the agent asked for. Neither product can stop data from leaving the site once a read is allowed.

What you can control is which reads exist for a given connection. GoBuildWP access tokens can be limited to named abilities and capped at the Read Only profile, so a reporting agent can be given woocommerce-sales-summary and the sales reports without ever holding a tool that reads a single customer. WooCommerce documents a permission callback on each ability and recommends a least-privilege user; it does not document per-credential ability scoping. Check your AI provider's retention settings before either connection touches real orders.

If both servers are connected, give each one a job

Connecting both endpoints means the client sees two tools that list products and two that read orders. An agent will pick whichever description reads better, which makes a test hard to repeat. Decide the split before you start: for example, WooCommerce's abilities for product creation on a developer's staging store, GoBuildWP for everything that needs approval or a change record. Then switch off the overlapping GoBuildWP abilities on the GoBuildWP Abilities screen, or leave the WooCommerce feature flag off for that connection's site, so each request has one obvious route.

We have not run the two side by side on one store, so treat coexistence as something your staging test establishes, not something this page promises.

Undo and approvals for WooCommerce's own MCP writes

Running both servers on one store no longer means two kinds of evidence. From GoBuildWP Free 1.18.0, mapped product edits/deletes through WooCommerce 10.3's own abilities can retain whole-post snapshots when target resolution and capture succeed. Inspect the entry before requesting restoration: that snapshot can rewind later stock or sales-related state, and does not reverse external effects. A current installed-version restore test is still needed. An order status change or an order note is recorded too, marked irreversible with the reason: a status change can email the customer and move stock, and a note may already have reached the customer, so neither can be quietly reversed.

On WordPress 7.1, the Other MCP servers setting can also hold WooCommerce's writes to the store's safety profile and send destructive ones to a person for approval in wp-admin, with Pro's approval queue applying as well. It is off by default.

Pricing and hosting model

Free in core, or part of a Pro licence

WooCommerce MCP

Free, in WooCommerce core, behind a feature flag. The blog post names WooCommerce 10.7 and WordPress 6.9+, and says the remote proxy needs Node.js 22 or newer.

GoBuildWP

GoBuildWP Free reads the store and edits single products at no cost. The rest of the WooCommerce module ships in GoBuildWP Pro, $39–$99.99 a year, or $59.99–$199.99 once, which a store-only job has to justify on its own.

Who should pick which

Products and orders, or the whole back office?

Choose GoBuildWP when

  • Agents handle refunds, coupons, customers or sales reports.
  • Store writes need configured human approval, an inspected record and recovery support for the selected operation.
  • The same agent also edits product pages, SEO or forms.

WooCommerce MCP is a good fit when

  • You want WooCommerce's own abilities, free and in core.
  • You are a developer trying the Abilities API on a staging store.
  • Changing products and order statuses is all the agent does.

A test you can repeat on staging

Three store checks with synthetic orders

  1. Refund part of an order

    Using a gateway in test mode, request a partial refund on one order. WooCommerce's documented abilities stop at order status and notes, so record what it offers; on GoBuildWP, check the refund in WooCommerce and in the gateway.

  2. Change and restore status only

    On an approved synthetic order, inspect capabilities, profile and confirmation, record the original status, apply one transition and request supported status recovery. Verify stored status; record notes, stock, email and gateway events separately. This is not full-order restoration.

  3. Verify the documented connection

    Follow current developer docs with a dedicated credential, inspect the actual tools and perform one authorized read. Preserve a redacted trace and version tuple; the older blog discrepancy does not justify an unsupported credential test.

Sources, checked 29 September 2026

WooCommerce MCP vs GoBuildWP: the sources behind each row

WooCommerce's two sources contradict each other: the developer docs list seven abilities and Application Passwords, the April 2026 blog nine abilities and a REST API key. We read both on 29 September 2026.

Best WordPress MCP server, all options compared

FAQ

Turning on WooCommerce MCP, and running it beside GoBuildWP

How do I switch WooCommerce MCP on?

It is a feature flag: enable mcp_integration through the woocommerce_features filter, or set the woocommerce_feature_mcp_integration_enabled option to yes with WP-CLI. Abilities are then served on the MCP Adapter's default endpoint, /wp-json/mcp/mcp-adapter-default-server.

Is WooCommerce MCP ready for a live store?

WooCommerce still labels it Developer Preview as of 29 September 2026, and its April blog post recommends staging. Its docs also warn that order and customer data can reach the AI provider.

Which credential does it take?

Use the current WooCommerce developer documentation as setup authority. Our 29 September reading specified a WordPress Application Password, not a WooCommerce REST API key. The April blog's different instructions are historical context. Verify actual discovery and an authorized read on the installed versions.

Can I use both on one store?

GoBuildWP has its own endpoint registration path beside the Adapter. Coexistence was not runtime-tested in this audit. On a synthetic staging store, test both endpoints, required reads and an approved bounded write/recovery before relying on concurrent use.

Try a refund on a synthetic store.

Connect WooCommerce's abilities and GoBuildWP Pro to the same staging shop, and see which one completes the order work you do every week.