A WooCommerce MCP that can reprice your catalog and can't refund anyone
Updated October 31, 2026
Through Kitepod, your assistant can reprice every product in your WooCommerce store in one conversation, and it can't refund a single order. That's what a WooCommerce MCP should look like.
That split is deliberate. Product work (prices, stock, variations, images) runs straight through under the default policy, snapshotted so you can undo it. Every order change waits for a person's approval, in every policy preset, and refunds and other payment actions are refused outright. You do those in wp-admin with your payment gateway, the way you do now.
Four things you'd ask a store assistant
Our supplier put prices up. Add $1 to every 100g tin in the Green Tea category and show me the new prices before you save anything.
Your assistant finds the products through WooCommerce's REST API, works out the new prices and does a dry run. Then it writes them in batches (WooCommerce caps a batch at 100 items), all inside one change set. If sales drop off a cliff next week, you can put every price back in one step, up to three months later.
Add Hojicha as a new tea in 50g, 100g and 250g sizes at $9, $16 and $34, with 20 of each in stock. The product shot is at the URL I'm pasting below. Keep it as a draft.
It pulls the image into your media library with alt text, creates a variable product with a Size attribute and three variations, sets stock on each and leaves it as a draft for you to look at. Because it goes through WooCommerce's own API, WooCommerce's validation, lookup tables and hooks all run, the same as if you'd clicked through the product screen.
Make a coupon AUTUMN15: 15% off, minimum spend $30, expires November 30.
Coupons go through WooCommerce's API too, but they aren't one of the routes Kitepod maps. So the default policy holds it for someone to approve, and only its database side can be rolled back. Expect your assistant to mention that before submitting.
Order 2231 shipped yesterday but it's still on processing. Mark it completed.
Your assistant reads the order, explains what will happen (completing an order usually emails the customer), submits the change and hands you an approval link. Nothing happens until a person clicks approve. The AI can't approve its own work. Ask it to refund order 2231 instead, and it'll say no and point you to wp-admin.
WooCommerce's own MCP, as of October 2026
WooCommerce has been building MCP support of its own. Its developer docs call it a "developer preview" and warn that "future updates may introduce breaking changes."
WooCommerce 10.9 added seven canonical abilities: query, create, update and delete products, query orders, update an order's status, and add an order note. They run through the WordPress Abilities API and the separate WordPress MCP Adapter plugin, which WooCommerce doesn't bundle. You connect with a WordPress username and an Application Password over HTTPS, or through a local proxy. The older /wp-json/woocommerce/mcp endpoint was removed in WooCommerce 11.3.
It's a clean, official design, and it's free. If you're a developer who wants the bare abilities with nothing in between, it's a reasonable pick.
| WooCommerce MCP (preview) | Kitepod | |
|---|---|---|
| Status | Developer preview | For live stores |
| Setup | MCP Adapter plugin, Application Password | Kitepod plugin, OAuth sign-in, no password pasted |
| Products | Query, create, update, delete | Simple and variable products, prices, stock, categories, images, coupons |
| Order status changes | An ability, checked against WordPress permissions | Always waits for a person's approval |
| Refunds | No ability listed | Refused |
| Undo | Not published | Every product write, 90 days |
| Beyond the store | WooCommerce abilities | Plugins, SEO, theme, pages, every connected site |
In the preview, an order status change is an ability like any other. In Kitepod, the approval sits on the site's side, and the AI can't skip it.
What needs a person, and what Kitepod won't touch
- Coupons, store settings, shipping zones, tax rates and payment gateways aren't mapped by Kitepod. Under the default policy, a person approves changes there, and Kitepod can only reverse the database side.
- Payment gateways can be switched on or off, with approval, but Kitepod never handles gateway credentials.
- Orders hold customers' personal data. Kitepod's WooCommerce skill tells your assistant to show only what the task needs, but you're still responsible for which assistant you connect.
- With HPOS on, orders live in their own tables. Kitepod goes through the REST API and never queries those tables directly.
- Kitepod isn't a backup service. On a store especially, keep your own.
Connecting your store
Put the Kitepod plugin on the store (WordPress 6.4+, PHP 7.4+). When you press Connect, you're choosing which WordPress account the AI works through, and a Shop Manager is a sensible pick: the AI can never outrank the account behind it. Finally, register https://kitepod.com/mcp as a connector in Claude or ChatGPT and sign in. Screens for each app are on WordPress MCP.
Finer points
Does WooCommerce have its own MCP server?
Yes, in developer preview as of October 2026. It runs through the WordPress MCP Adapter, and WooCommerce 10.9 added seven product and order abilities. How the adapter turns abilities into tools is in the MCP Adapter guide.
Can the AI issue refunds?
No. Kitepod refuses refunds and other payment actions. The store owner does them in wp-admin with the payment gateway.
Can it bulk-edit prices?
Yes. It updates products in batches of up to 100, keeps the whole job in one change set and runs a dry run first, so you can undo the batch in one step.
Does it write product descriptions?
Your assistant drafts them, using your own AI subscription, and Kitepod saves them to the product. Ask for drafts if you want to read them before they go live.
Does it work for an agency running several stores?
Yes. Every connected site is in the same conversation, and you can invite a client as an approver on just their store. WordPress care plans covers that setup.
The approval link for an order lands with whoever you invite, so a client can sign off on their own store's order changes without a wp-admin login of yours.