The short version
WooCommerce 10.9 (mid-2026) shipped an official MCP in core: seven canonical abilities for querying and writing products and orders. It is built in, free, and maintained by the people who maintain WooCommerce. That is the right place for the data layer to live.
Respira is the safe, complete layer above it. It covers the full store surface (54 tools: products, variations, swatches, coupons, customers, orders, refunds, the Staggs configurator, AI-readiness), wraps every write in a snapshot, a dry-run preview and an approval step, and edits product cards and shop layouts inside 16 page builders. On WooCommerce 10.9 and above, Respira detects the official abilities and delegates to them, then wraps them in its own safety envelope.
So this is not really “either or”. If you only need to query products and orders from a script, use the official MCP. If you are pointing an AI agent at a live store and want it to be safe and complete, use Respira on top.
| Official WooCommerce MCP | Respira WooCommerce MCP | |
|---|---|---|
| Scope | 7 abilities (products + orders) | 54 tools (full store) |
| Snapshots + rollback | ✗ | ✓ 90 days |
| Dry-run on destructive ops | ✗ | ✓ |
| Refunds | ✗ | ✓ dry-run by default |
| Builder / storefront editing | ✗ | ✓ 16 builders |
| Cost | Built in, free | EUR 95/yr, free on Studio |
The core distinction
The official MCP speaks the data. Respira adds the safety and the layout.
When an AI agent decides to “discount every product in the Summer category by 20 percent”, the official abilities will run that write directly. There is no snapshot taken first, no dry-run preview, no approval step, and no one-click way to undo it if the agent misread the catalog. That is fine for a developer running a careful script. It is a different proposition when an autonomous agent is acting on a live store with real orders.
Respira was built safety-first. Every write is duplicate-first and snapshotted before and after, reversible for 90 days. Destructive operations have a dry-run preview. Refunds are dry-run by default and capped to the order’s remaining refundable total. Payment gateways, shipping zones and tax settings are read-only. That safety envelope is the whole point.
What the official WooCommerce MCP is
WooCommerce 10.9 added seven canonical abilities through the WordPress Abilities API and the MCP Adapter:
products-query,product-create,product-update,product-deleteorders-query,order-update-status,order-add-note
They are schema-defined, permission-gated, and respect WooCommerce’s own authentication. Query abilities are read-only; write abilities declare their destructiveness. It is a clean, official foundation, and it is the correct home for core data operations.
What it does not cover: product variations, attributes and swatches, coupons, customers, refunds, the storefront, page-builder layouts, or any product configurator. And by design, it has no snapshot, dry-run, approval or rollback layer. Those are left to the client.
What Respira adds
Respira’s WooCommerce add-on is the layer the official seven abilities do not try to be:
- The rest of the surface. Full variation CRUD and one-call matrix generation, colour and image swatches (the WooCommerce 10.9
wc-visualtype), coupons, customers (PII-aware), order notes and refunds, the Staggs product configurator, and a 0-100 AI-readiness score per product and across the catalog. - The safety envelope. Snapshot before and after every write, 90-day rollback, dry-run on destructive operations, refunds dry-run by default, an approval queue before changes go live, and an audit log that records IDs only for customer writes, never names or emails.
- Builder-aware storefront editing. The one thing no other WooCommerce MCP does: read and edit product cards and shop layouts inside Elementor, Divi, Bricks, Flatsome and 12 more builders. A correct price in a broken product card is still a broken store.
Coverage, side by side
| Capability | Official WooCommerce MCP | Respira |
|---|---|---|
| Products | ✓ | ✓ |
| Orders | ✓ query + status + note | ✓ |
| Variations + swatches | ✗ | ✓ |
| Coupons | ✗ | ✓ |
| Customers | ✗ | ✓ PII-aware |
| Refunds | ✗ | ✓ dry-run default |
| Product configurator (Staggs) | ✗ | ✓ |
| AI-readiness scoring | ✗ | ✓ |
| Storefront / builder editing | ✗ | ✓ 16 builders |
Safety, side by side
| Safety | Official WooCommerce MCP | Respira |
|---|---|---|
| Snapshot before write | ✗ | ✓ |
| Roll back catalog and content writes | ✗ | ✓ 90 days |
| Dry-run on destructive ops | ✗ | ✓ |
| Refunds dry-run by default | ✗ | ✓ |
| Approval queue before live | ✗ | ✓ |
| Read-only payment / tax / shipping | ✗ | ✓ |
| PII-safe audit log | ✗ Partial | ✓ IDs only |
Why not both
This is the honest answer: use both. On WooCommerce 10.9 and above, Respira does not reimplement the official write paths. It detects the canonical abilities and delegates the matching write to them (wrap-and-defer), then wraps that call in its snapshot, dry-run and audit envelope. Respira never collides with WooCommerce’s own tools, and it inherits whatever the official abilities improve over time. On the large majority of stores still below 10.9 (it only shipped in mid-2026), Respira runs its native path.
You get the official foundation plus the safety and completeness on top, from one connection.
When to use the official MCP
Reach for the official WooCommerce MCP, on its own, when:
- You only need to query products and orders, or make simple status changes, from a script.
- You are a developer running careful, reviewed operations against a single store.
- You want the smallest possible, fully built-in surface with no extra plugin.
When to use Respira
Reach for Respira when:
- You are pointing an AI agent (Claude, ChatGPT, Cursor) at a live store and want every change snapshotted, previewable and reversible.
- You need the parts the seven abilities skip: variations and swatches, coupons, customers, refunds, or a product configurator.
- Your storefront is built with a page builder and the layout is the product.
- You manage more than one store and want agency-grade multi-site operations from one set of credentials.
Pricing
The official WooCommerce MCP is built into WooCommerce core and free. Respira’s WooCommerce add-on is EUR 95 per year on the Maker and Builder plans, and included free with Studio and Founder. It requires Respira Core and the WooCommerce plugin.
Bottom line
The official WooCommerce MCP is the right foundation, and Respira is glad it exists. If your AI is only reading data or making careful scripted edits, the official seven abilities may be all you need. If your AI is acting on a live store and you want it to be safe and complete, Respira is the layer to put on top. They work better together than either does alone.
Join the conversation
0 comments · Respira accountNo comments yet. Be the first to weigh in.