WooCommerce now has a native MCP server. It shipped as a first version in WooCommerce 10.3, and as of 10.9 it exposes seven abilities through the WordPress MCP adapter: query products and orders, create and edit products, change order status, and add order notes. It is labelled a developer preview. datavessel’s WooCommerce MCP server connects the same store to Claude or ChatGPT with nothing installed, and adds the rest of the stack, an approval on every write, a ledger, and agents on a schedule. Which one you want depends on who is asking the questions. The setup on our side is in connect Claude to your store.
Native facts are as documented in September 2026. WooCommerce ships monthly; check its developer docs for the current ability list.
What the native WooCommerce MCP is
It is built on two WordPress-core pieces: the Abilities API, which lets plugins describe operations in a typed, permission-checked way, and the WordPress MCP adapter, which exposes those abilities to any MCP client. WooCommerce registers its abilities there, so the same mechanism that serves WooCommerce can serve any plugin that adopts the Abilities API.
The practical facts:
- Version. Introduced in 10.3; the current ability set arrived with 10.9. Older stores do not have it.
- Abilities. Seven as of 10.9: list and query products and orders, create products, edit products, change order status, add order notes.
- Auth. Remote clients authenticate with a WordPress username and an Application Password, created under Users, then Profile. Requests run as that user, and each WooCommerce ability enforces its own permission callback on top.
- Clients. Claude Desktop, Claude Code, Cursor and any MCP-capable tool.
- Status. Developer preview. The older REST-derived MCP endpoint is deprecated and kept as a compatibility layer.
It is a sound foundation, and if you were about to build a WooCommerce MCP server from the REST API, stop; that work is done in core.
What it is for, and what it is not
The native server is a platform primitive for one site. It is the right choice for:
- Developers working on a store from Claude Code or Cursor who want typed access to products and orders while they build.
- Plugin authors who want their own domain exposed as MCP tools through the Abilities API.
- Single-store admin work where the questions stay inside WooCommerce and the client can hold an Application Password.
What it deliberately is not: an operations layer. There is no approval queue, no record of who approved what, no schedule, nothing outside WooCommerce, and connecting it to ChatGPT means exposing an authenticated endpoint on your own site. An Application Password is a developer’s credential, not a workflow for an owner approving a refund from a phone.
What datavessel’s WooCommerce MCP server is
datavessel is an e-commerce harness: a hosted MCP server plus everything an operator needs around the tools. For WooCommerce the catalog is 19 typed tools, 12 reads and 7 writes: products, orders and order details, order totals, sales reports, top sellers, customers, coupons and refunds on the read side; product creation and updates, inventory updates, order updates and notes, coupons and refunds on the write side. It connects through a WooCommerce REST API key you create and can revoke; nothing is installed in WordPress.
The differences that decide it:
- The rest of the stack in the same conversation. WordPress posts and media, GA4, Search Console, Google and Meta ads, Klaviyo, Merchant Center and reviews sit next to the store: 300+ tools across 18 providers. “Which blog posts send the most traffic to products that are low on stock” is one prompt.
- Claude and ChatGPT over OAuth. A browser sign-in in either assistant; no endpoint on your site, no Application Password pasted into a client. Guides: Claude and ChatGPT.
- Approvals, not permissions alone. Every write pauses with the exact change and the reasoning, approved on web or mobile. Some actions never run unattended regardless of settings.
- A ledger per store, every action timestamped.
- Schedules and triggers. Order-desk sweep, product-copy refresh, SEO audit, on a clock or on a WooCommerce webhook.
- Any WooCommerce version with REST API v3, and many stores. An agency connects every client site behind one connector, isolated per client.
Side by side
| Native WooCommerce MCP (10.9) | datavessel MCP server | |
|---|---|---|
| Ships as | Part of WooCommerce core, developer preview | Hosted service, nothing on the site |
| Auth | WordPress Application Password | OAuth sign-in in Claude / ChatGPT |
| Scope | Products, orders, order status, notes | Store + WordPress content, analytics, ads, email, reviews, feeds |
| Permissions | WordPress user plus ability callbacks | Read/write separation, approval gate |
| Writes | Direct, as the user | Proposed, approved on web or mobile |
| Audit | WordPress and WooCommerce logs | Full ledger per action, per store |
| Schedules / triggers | No | Yes, agents and webhooks |
| Extensible in-process | Yes, via the Abilities API | No; via new providers on the datavessel side |
| Older WooCommerce | No, 10.3+ | Yes, REST API v3 |
| Best for | Developers, plugin authors | Owners, ops teams, agencies |
Which one should you use?
Use the native server if you are a developer or plugin author on WooCommerce 10.9 or later, your client can hold an Application Password, and the work stays inside the store. It is free, first-party and extensible in a way a hosted service never will be.
Use datavessel if the person asking is the owner or an operator, the questions cross into content, analytics and ads, you want ChatGPT as well as Claude, you need approvals and a record, or you run more than one site.
Use both if you are an agency: native MCP for the engineers building plugins and themes, datavessel for the account managers running operations across every client’s store. They authenticate separately against the same site and do not conflict.
Frequently asked questions
Does WooCommerce have an official MCP server?
Yes. Since WooCommerce 10.3, with the current seven abilities as of 10.9, built on the WordPress Abilities API and MCP adapter. It is a developer preview as of September 2026.
How do I enable the WooCommerce MCP?
Update to 10.9 or later, create an Application Password for the WordPress user the assistant should act as, and add the site’s MCP endpoint to Claude Desktop, Claude Code or Cursor with that username and password. Consult the WooCommerce developer docs for the current endpoint and any feature flag.
Can I connect the native WooCommerce MCP to ChatGPT?
It authenticates with an Application Password against your own site, and ChatGPT’s custom connectors expect a remotely reachable endpoint with a sign-in flow. Check the docs for your setup before relying on it. datavessel connects to ChatGPT through the standard connector flow.
Is datavessel’s WooCommerce MCP read-only?
No. Seven of the 19 tools are writes: products, inventory, orders and notes, coupons and refunds. Every write pauses for your approval.
Which WooCommerce versions does datavessel support?
Any version with the REST API v3, on any host, cloud or self-managed, including stores that have not reached 10.9.
Can I use both at the same time?
Yes. Each authenticates on its own, and neither installs anything on the other’s behalf. Developers on native, operators on datavessel is the common split.
The bottom line
WooCommerce building MCP into core, on top of the Abilities API, is good news for everyone: it settles the question of whether WooCommerce stores belong in AI clients. The native server is the right primitive for developers. datavessel’s WooCommerce MCP server is the operations layer for the people running the store: the site and its stack in one conversation, every write behind an approval, every action in a ledger, on any WooCommerce version.
Connect your WooCommerce store to Claude or ChatGPT with approvals and a ledger built in: the datavessel MCP server →
Leave a Reply