WooCommerce MCP integration
A WooCommerce MCP for the work behind your storefront.
Ask your AI to inspect products, review orders, prepare catalog updates, and work with WooCommerce settings through EMCP Pro. Dedicated read and write dispatchers use WooCommerce’s own REST controllers, with separate confirmation requirements for refunds, deletions, and batch changes.
Pro integrationWooCommerce active
Prepare a seasonal catalog update
| Review before changing | Confirm after saving |
|---|---|
| Product & variation IDs | Same target records |
| Current → proposed price | Saved price values |
| Stock & sale schedule | Expected availability |
| Storefront preview | Correct displayed offer |
A practical place to start
A catalog update your store team can review.
- 01
Find the exact products
Filter the catalog and retrieve the product and variation IDs involved. Include current prices and stock values so a similarly named product does not become the wrong target.
- 02
Prepare the changes
Show a before-and-after table with IDs and proposed values. Enable the write tool for the authorized update; batch changes additionally require explicit confirmation.
- 03
Read the catalog back
Retrieve the affected products again. Check the storefront presentation and any sale-price schedule, variation selection, or tax display relevant to the change.
Built for WooCommerce
Turn a catalog request into a reviewable change
Start a seasonal update by finding the exact products and variations involved. Ask for current prices, stock, and identifiers in a review table before applying anything. After the approved update, read the affected records again. The assistant coordinates the steps; WooCommerce remains the system that stores product data and enforces endpoint permissions.
Follow an order from question to action
An order-management request often needs context before a status change. Read the order and its notes, decide what needs updating, and make only the requested change. Refunds deserve their own explanation: the write tool must be enabled, the request requires confirmation, and an actual payment reversal depends on the gateway and refund parameters. A confirmation flag is not a promise that money can later be restored.
Keep brand content and search metadata in their proper places
Native WooCommerce brand operations manage the brand record and its existing image attachment. Search titles and descriptions belong to the active SEO integration. This creates a useful two-part workflow: prepare the brand archive, then update supported taxonomy SEO and inspect the rendered archive. Describe native brands separately from third-party brand plugins.
Store settings belong in the operating workflow too
Catalog work often touches more than product descriptions. A new shipping destination may need a review of zones, methods, and tax settings. A promotion may need a coupon with the right restrictions. Discover the relevant operation, read the current record, and give the assistant a concrete requested change. Read-only reports can help answer a store question without modifying an order.
For a checkout built with FunnelKit, combine WooCommerce’s store records with FunnelKit inspection. The former describes products and orders; the latter describes the saved funnel and checkout configuration. Keeping those sources explicit makes a checkout review easier to act on.
See the WooCommerce tool reference for operation requirements and the WooCommerce native MCP documentation for its separate integration approach.
Walkthrough: review a seasonal product update before writing
With WooCommerce active and EMCP Pro enabled, try: “Find the products in my summer collection and list their IDs, current prices and stock status. Propose new descriptions for review. Do not change prices, stock or publication status.”
- Discover the operation catalog through
woo-readand read the matching products. Resolve variations separately so a parent product is not mistaken for a purchasable variation. - Prepare a table of exact product IDs, existing descriptions and proposed descriptions. Confirm which records and fields should change before enabling
woo-write. - Discover the supported write operation and pass only the approved fields. Read the affected products again and inspect their storefront pages, including variation selection and the displayed price.
This is a proposed workflow using the WooCommerce dispatcher contract, not an executed catalog update. Store tools require the appropriate WooCommerce permissions. Keep SEO changes in the Yoast integration or the SEO integration actually active on your site.
Choose by the work you need to do
WooCommerce MCP integrations, compared.
Compare the documented workflows in EMCP, Novamira, Respira, and WPVibe. A general code or API route may offer more than a dedicated integration documents.
Checked · Documentation review, not a hands-on benchmark. “Unverified” means the reviewed sources do not establish that capability; it does not mean unsupported. Editions and installed versions may affect availability.
Scroll horizontally to compare all four products. Each source number opens the supporting documentation.
| Workflow | EMCPOur integration | Novamira | Respira | WPVibe |
|---|---|---|---|---|
| Products and variations | Dedicated REST-backed operations [1] | Catalog specialization [2] | Dedicated store add-on [3] | Documented product/batch workflow [4] |
| Orders and notes | Read, update and add notes [1] | Outside advertised specialization [2] | Dedicated order operations [3] | Order-reading/export recipe [5] |
| Refunds | Confirm-gated; actual gateway behavior matters [1] | Outside advertised specialization [2] | Dry-run-first refund workflow [3] | General access; exact task unverified [4] |
| Tax/settings writes | Dedicated WooCommerce controllers [1] | Beyond documented catalog specialization [2] | Payment/shipping/tax settings read-only [3] | Tax-setting recipe [6] |
| Brand archive SEO | Native brands plus separate supported SEO adapter [1] | Category/tag/attribute coverage; brand parity unverified [2] | Brands and feed functionality [3] | Yoast category noindex recipe [7] |
Sources & comparison methodology
We compare specific tasks, including EMCP’s limits. Vendor documentation describes advertised support; it does not prove identical behavior, reliability, or performance. Broad API access is distinguished from a documented integration workflow. No scores or tool counts determine a winner.
- EMCP documentation: woocommerce
- novamira.ai/mcp/woocommerce/
- respira.press/addons/woocommerce
- wpvibe.ai/cookbook/bulk-update-woocommerce-prices-with-ai/
- wpvibe.ai/cookbook/export-woocommerce-orders-to-csv-with-ai/
- wpvibe.ai/cookbook/configure-woocommerce-tax-rates-with-ai/
- wpvibe.ai/cookbook/bulk-noindex-woocommerce-product-categories-with-ai/
Get connected
Put WooCommerce in your AI’s toolkit.
- 1
Activate the store integration
Install EMCP Pro alongside WooCommerce. The connected WordPress account must satisfy WooCommerce’s endpoint permissions for the task.
- 2
Begin with a store read
Discover woo-read operations and request a small product or order sample. Use returned identifiers for later requests and check the store’s current configuration.
- 3
Enable the required writes
Turn on woo-write when you are ready to change store data. Refunds, deletions, and batch operations have an additional confirmation requirement; inspect their parameters before proceeding.
Then connect Claude Code, Claude Desktop, or Cursor to use the WooCommerce tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about WooCommerce, supported operations, and the workflow on your site.
Is this limited to product descriptions?
No. The documented surface also includes orders, coupons, reports, customers, and store configuration. Discover the available operations on your installed version.
Can every WooCommerce change be undone?
No universal rollback guarantee is made. Refunds, deletion, and external side effects need operation-specific review. Read back saved state and use an appropriate recovery plan.
Does the integration support HPOS?
EMCP routes order operations through WooCommerce’s own REST controllers, which handle the storage layer. Review any additional extensions involved in your order workflow as part of testing.
How does this relate to WooCommerce’s own MCP support?
WooCommerce also documents native MCP work. EMCP provides its own woo-read and woo-write dispatchers within a wider WordPress toolkit. Compare the operations and release status you need in each product rather than assuming the same coverage.
Your tools. Your WordPress site.