WooCommerce MCP: Run Your Store From Claude or ChatGPT

WooCommerce MCP today: what WooCommerce ships 📦

Yes, WooCommerce has its own MCP, and it’s free.

Status today:

• WooCommerce 11.2.1 (released October 9, 2026) registers seven abilities through the WordPress Abilities API, with no setting to turn on: products-query, product-create, product-update, product-delete, orders-query, order-update-status and order-add-note.
• WooCommerce marks product-update, product-delete and order-update-status as destructive. Product delete moves the product to trash unless the caller forces a permanent delete.
• The older /wp-json/woocommerce/mcp endpoint still ships behind the experimental “WooCommerce MCP” option, which is off by default, signs in with WooCommerce REST API keys and is deprecated.
• WooCommerce’s developer docs already describe 11.3, which has not shipped yet: the endpoint goes away with an HTTP 410, the MCP Adapter becomes a plugin you install separately, remote connections sign in with a WordPress Application Password and an order-notes-query ability joins the list.
• WooCommerce calls the whole feature a developer preview.

Does the standalone MCP Adapter 0.7.1 work alongside the copy WooCommerce 11.2.1 bundles? On WordPress 7.1.3 with WooCommerce 11.2.1, a scripted check of the adapter’s default server listed all seven abilities with the experimental option left off, and having both adapter copies installed produced no error, because only the standalone 0.7.1 code loaded. A probe, not an AI session, but it showed the 11.3-style setup working.

Which route fits your store 🧭

Routes are compared from each vendor’s own docs, listings and code. WooCommerce’s native abilities through MCP Adapter 0.7.1 and Easy MCP AI 2.2.2 were also run on stores seeded with demo products, orders and coupons (WooCommerce 11.2.1, Claude Code). The W7S, MCP for WooCommerce and Pipedream rows were not tested; they are as their makers describe them.

Use the native route when you work from a desktop app or the command line, you only need product and order basics, and free, first-party WordPress and WooCommerce code beats feature breadth. On 11.2.1 the documented path is the experimental option, which starts WooCommerce’s bundled adapter, while the 11.3 docs move you to the standalone MCP Adapter plugin; either way, the client connects to /wp-json/mcp/mcp-adapter-default-server as a WordPress user with an Application Password, and the probe above found the standalone adapter serves the same seven abilities without opening the deprecated REST-key endpoint that the option switches on. If you later add an MCP plugin, run one MCP plugin per site.

Use a plugin route when your AI lives in the claude.ai or ChatGPT web apps, or when the job includes customers, coupons, sales reports or an audit trail. The adapter’s site-owner guide is blunt: the web apps “cannot connect to MCP Adapter on their own today” because WordPress has no OAuth server and the adapter adds none; Claude does document a limited beta for fixed request headers, Basic authentication included, which was not tested here. A real attempt ended the same way: claude.ai accepted the server URL, found no sign-in service and failed with “Couldn’t register with Adapter test’s sign-in service.”

For the web apps, the route covered here is Easy MCP AI, a free plugin that runs its own MCP server inside WordPress with OAuth 2.1 built in and lists Claude and ChatGPT as documented OAuth clients, so the sign-in the web apps need comes from your site. Easy MCP AI is built by Themeisle, the team behind WPShout. It does not use the MCP Adapter or WooCommerce’s MCP endpoint: its WooCommerce tools call WooCommerce’s own REST API inside WordPress, which is why the 11.3 endpoint removal does not affect it. It has 20,000+ active installs on WordPress.org.

Set up Easy MCP AI for your store ⚙️

Install and switch the WooCommerce group on

On a live store, line up public HTTPS first, because the OAuth sign-in refuses plain HTTP, and run the checks on the Easy MCP AI Dashboard, because some hosts strip the Authorization header or block /wp-json/ at the firewall. Install Easy MCP AI from Plugins > Add New Plugin, then open Easy MCP AI > Tools > Abilities and switch the WooCommerce group on; it starts off. The caveat: Easy MCP AI’s general REST tools, on by default, follow WooCommerce’s own permission checks even with the group off, so a credential with REST read access can still read WooCommerce routes, orders and customers included, and one with REST write access can change them. You can switch the wc/v3 namespace off under Tools if you want that door closed.

Connect Claude

On Easy MCP AI > Dashboard, the connect card offers a “Connect to Claude (1-click)” button. It opens claude.ai’s “Add custom connector” dialog with your site name and MCP server URL already filled in. Clicking Continue makes claude.ai check the server and detect “Sign in now” with automatic OAuth registration. The plugin’s documented finish: your site’s consent page, where you sign in as the user the client should act as, choose what the AI may read or change and click “Approve & Continue”. Cursor goes through the same consent flow.

Connect ChatGPT

“Connect to ChatGPT” on the same card opens ChatGPT’s plugins page. On a Business workspace, the form sits under the Add menu as “Add custom MCP server”: enter a name and your server URL, leave Authentication on OAuth, tick “I understand and want to continue” and click “Create as a plugin”; Easy MCP AI’s documented finish is approving access on your site. Whether you can add a custom MCP server depends on your ChatGPT plan and workspace settings, and on Business and Enterprise workspaces an administrator must allow it. Whichever app you use, start with a read-only question such as the low-stock prompt in the sessions below, then check Easy MCP AI’s Audit log for the call before you ask for a change.

Scope what the AI may touch

Reading the store works with the defaults. Changing store data through the dedicated WooCommerce tools needs Full access or the WooCommerce write box ticked under Custom, and a Custom grant holding REST write also reaches WooCommerce’s write routes, with each route’s own permission check deciding. The “Read + write content” token preset gives WooCommerce read only. Bind each connection to a WordPress user whose role fits the job rather than an administrator by habit. New products from Easy MCP AI’s product tool are saved as drafts unless the AI asks to publish, and an agent may ask on its own, as the native session below shows, so switch on Force draft on create under Settings > Access & safety if new products must wait for review.

👉 Get Easy MCP AI free from WordPress.org

What a connected store session looks like 🧪

No claude.ai or ChatGPT sessions were run for this article; what follows are the Claude Code runs from the route comparison.

A delete that waits for approval

With WordPress 7.1.3, WooCommerce 11.2.1, Easy MCP AI 2.2.2 and Claude Code with a full-access API key bound to the store’s admin user, the opt-in “Ask before destructive actions” switch was turned on and the opening prompt was:

“Our fall promo ended early. Delete the FALL5 coupon.”

Claude Code listed the coupon, then stopped:

“I haven’t deleted it yet because this site requires an administrator to approve deletions first.”

The site first offered Claude Code an in-chat approval prompt, which the headless session could not answer, then returned a link to an approval page, preview “WooCommerce: Delete Coupon (id: 29)”, that only the WordPress user the AI acts as can decide, and the request would have expired after 15 minutes if nobody answered.

After a human approved it, the identical call went through:

“I deleted the FALL5 coupon (ID 29), so customers can no longer use it at checkout. The two orders that already used it keep their discount.”

The delete was permanent: no trash entry, no coupon afterwards. The follow-up prompt, “Order #40 shipped this morning. Mark it as completed.”, ran with no pause at all, because the single-order update tool, cancelled and refunded statuses included, is not on the default approval list (the batch-orders tool and REST writes do pause):

“Order #40 (Lena Hoffmann, $68.95) has moved from Processing to Completed.”

Completing the order also triggered WooCommerce’s “Completed order” email, which the order notes show failed to send because the store had no mail set up. On a live store with that email switched on, completing the order triggers WooCommerce’s customer notification, and whether it arrives depends on the store’s mail setup.

The native route: products and orders only

A second store ran the native route (WooCommerce 11.2.1, MCP Adapter 0.7.1, the experimental “WooCommerce MCP” option off, Claude Code signed in with an Application Password). The prompt “Which of my products are low on stock or sold out right now, and are any of them in orders that are still processing or on hold?” got a correct answer:

“One low-stock product is in a processing order: Swiss Water Decaf Colombia, in order #39.”

The agent created Kenya AA at $19.50 with 30 in stock and published it by its own reasoning, since the other products were published:

“I created the product and it’s live, but it isn’t in the Single Origin category yet. The tools I can use here have no way to set categories when creating or updating a product.”

11.2.1’s product-create has no category field, so the agent set everything else and flagged the gap. 11.2.1 registers no coupon ability at all, so a coupon request has nothing to call on the native route; a scripted probe of the adapter’s default server found no WooCommerce abilities beyond the seven for products and orders.

What it can’t do (yet) 🚧

• Refunds. No dedicated Easy MCP AI tool creates a refund; the AI can mark an order refunded and list the refunds on an order.
• Store settings. The dedicated WooCommerce tools read shipping zones, shipping methods, tax rates and payment gateways but write none of them.
• Line items. The single-order tool cannot edit an order’s line items.
• Reports. Sales reports come from WooCommerce’s legacy report endpoints, not WooCommerce Analytics.
• Logs. The WooCommerce log tools redact secrets, but customer names, emails and addresses stay visible.
• Restore. Change history keeps before/after snapshots of MCP changes but cannot restore WooCommerce objects, and deletes through the dedicated tools are permanent.
• Native route. No customer, coupon or refund abilities in 11.2.1, and product-create has no category field.

Staying in control of your store 🔒

WooCommerce’s own docs warn that order and customer operations may expose personal data and advise a dedicated user with only the capabilities the job needs. Grant WooCommerce read for reporting and add write only when the job is a store edit.

Turn on “Ask before destructive actions” to pause calls covered by the approval policy, check the “Never ask for” exceptions and keep API keys out of Unattended mode; only the login-gated approval page provides a separate human channel, because the credential-holding client decides in-chat approvals. As the session above shows, deletes pause while status changes through the single-order tool run straight through; add wp_wc_update_order to the “Always ask for” list if those should wait too.

Keep the Audit log on; it’s on by default. It records every MCP tool call with the user, client, tool, redacted arguments, result status and duration, and a paused call shows up as Pending.

Whatever the AI reads is returned to the AI client and processed by that client’s model, usually a cloud vendor. Customer names and addresses in orders are part of that, so treat the AI vendor’s data terms as part of your store’s compliance picture.

The subtler risk is prompt injection, the top item on OWASP’s LLM risk list: text the AI reads, like product reviews or order notes, can carry instructions that steer a model with write access. Scoped grants, a non-admin user, approvals for deletes and the Audit log are the practical mitigations, and the Dashboard’s Pause AI access switch makes the site refuse every client’s tool calls in one move if something smells wrong.

Bottom line 💬

If your AI lives in Claude Code, Cursor or another desktop client and the job is product and order basics, WooCommerce’s own abilities plus the free MCP Adapter do the job. If it lives in the claude.ai or ChatGPT web apps, or the job includes coupons, customers, sales reports or an audit trail, a plugin with its own OAuth sign-in is the practical route, and Easy MCP AI, free with no paid tier, is the one set up and run from Claude Code here. Hosted connectors like Pipedream and WPVibe relay requests through the vendor’s servers (WPVibe still installs its own plugin on the store), as their makers describe them.

For everything AI can do for a store without MCP, from support replies to product copy, the WPShout ChatGPT for WooCommerce guide still applies.

Are you running your store from an AI assistant yet, and which route did you pick?