Grow your WooCommerce store by asking.

An MCP (Model Context Protocol) server lets AI assistants like Claude, ChatGPT and Cursor read and edit your store directly. Respira is the WooCommerce MCP that covers the full store surface, 104 tools across products, variations, brands, coupons, customers, orders and refunds, with a snapshot, a dry-run preview and an approval step on every change.

With Respira, yes. Every write is duplicate-first and snapshotted before and after, so any change stays reversible for 90 days. Destructive operations have a dry-run preview, refunds are dry-run by default and capped to the refundable total, and payment gateways, shipping zones and tax settings are read-only.

Four things: changes land on a copy first, anything that moves money or many rows runs as a dry run before it is written, live changes wait for approval, and every write can be rolled back. Respira adds all four on every write, with 90 days of undo and read-only payment, shipping and tax settings. WooCommerce’s own abilities rely on WordPress permissions, which decide who may act; Respira adds the layer that decides whether a change is the one you meant.

No, it works next to it. WooCommerce ships canonical abilities for products and orders in core and is adding abilities to its extensions. Keep them connected. Respira runs in its own namespace, never shadows WooCommerce’s abilities, and adds what a store owner needs on top: changes on a copy with approval and 90 days of undo, the rest of the store (variations, brands, coupons, customers, refunds), the storefront in page builders, and the growth tools.

Most community servers translate the WooCommerce REST API into tools, which is useful for reading and scripted edits. Respira adds the safety layer (copies first, dry runs, approval, a PII-safe audit log and 90 days of undo), the parts of the store a REST translation leaves raw (variations and swatches, brands, refunds, AI-readiness), and storefront editing in Elementor, Divi, Bricks, Flatsome and block themes.

Only if you are running a WooCommerce store and want to manage products, orders, and inventory through the AI you already use: Claude, ChatGPT, Codex, Cursor or any MCP app.

Yes. Cancel anytime from billing. You will have a 7-day grace period, then WooCommerce features are disabled. Data remains safe.

Yes for the store itself: products, variations, coupons, orders, reports, feeds and the readiness score work on any WooCommerce site, whichever of the 19 supported page builders it uses. Storefront editing is narrower: product cards can be edited in Elementor, Divi, Bricks, Flatsome and block themes, and sale and low-stock badges are placed on block themes. Other builders get a clear unsupported answer instead of a false success.

Yes, properly, since 4.0.0. Analysing a shop page on a block theme returns real structural analysis against the native archive-product template instead of "no page builder detected". Badges are positioned inside the product image, product card fields are addressable by canonical WooCommerce block name, and update_checkout_layout returns an honest capability error rather than a misleading one. Proven on WordPress 7.0.2, PHP 8.5, WooCommerce 10.9.4 and the stock Twenty Twenty-Five block theme. It is not yet proven on GreenShift. This came from a published field study by Dale Smith of revWorx (https://revworx.ai/), who builds only on FSE block themes and live-verified that the storefront tools went inert there.

Yes. Since 4.0.0 there are bounded, HPOS-compatible reports: revenue, a sales time series, top products, orders and privacy-safe customer summaries. Each one states its metric definitions and the coverage behind the number, so an agent quoting a figure can also say what that figure counts.

Yes, behind an approval gate. Webhook management uses the native WooCommerce webhooks, accepts HTTPS targets only, restricts topics to an allowlist, treats secrets as write-only so they are never returned, and keeps test deliveries redacted and rate limited.

Yes. Your WooCommerce add-on purchase includes technical support for WooCommerce features. Email word@respira.press directly for human support.

You get a 7-day grace period. After that, WooCommerce features are disabled while your data remains safe. Reactivate anytime.

No. Payment gateways, shipping zones, and tax settings are read-only. AI can read for context but cannot modify them.

Simple, variable, grouped, external, virtual, and downloadable products are supported.

Yes, with guardrails. Refunds are dry-run by default, so the AI previews the amount without moving any money; you have to explicitly confirm before a refund is issued. Every refund is capped to the order’s remaining refundable total and is snapshotted and audited.

That is what the agent-ready commerce layer (v3.1) does. The add-on generates always-fresh product feeds in six formats (Google Shopping, OpenAI/ChatGPT JSONL, Meta, Pinterest, TikTok, CSV), serves a store llms.txt at your site root, scores your catalog against the Google Shopping spec, and creates signed cart links whose orders are attributed back to the AI assistant that sent them.

Respira ARC is the free plugin that ships the readable half: feeds, llms.txt, readiness score and cart links. The WooCommerce Add-on includes all of that plus the agent tools that act on a store. If both are installed, ARC steps aside automatically and settings carry over, so no, with the add-on you do not need ARC.

Yes, since v3.1. List, inspect and update subscriptions (status transitions validated against what Subscriptions itself allows), reschedule bookings with a conflict scan, and manage membership statuses and end dates. Every write is dry-run by default and tested against the real extensions. Since v3.2 the add-on also reads and edits STAGGS product configurators.