To connect Claude to WooCommerce, you add one MCP connector — https://mcp.datavessel.io/mcp — in Claude’s settings, sign in with OAuth, and link your WooCommerce store at app.datavessel.io. From then on Claude reads your live products, orders, and customers, and can update product content with your approval — no CSV exports, no pasting, no plugins fighting your theme. This is the WooCommerce edition of the connect Claude to your store guide; Shopify and Shopware have their own walkthroughs.
Prefer ChatGPT? Same setup, same gates: connect ChatGPT to WooCommerce.
Why WooCommerce owners want this
WooCommerce’s superpower — it’s WordPress, you own everything — is also its tax: everyday questions mean wp-admin archaeology across Orders, Products, Analytics, and whatever plugins accumulated since 2019. Connected to Claude, the store becomes something you interrogate directly:
- “List products that sold last month but have no meta description.”
- “What’s my average order value this quarter versus last?”
- “Which orders from last week are still unfulfilled?”
- “Rewrite the description for [product] from its actual attributes — and show me before you save.”
The first three are instant reads. The fourth is a write — Claude drafts it, shows the exact change, and touches nothing until you approve.
There’s also a quieter benefit specific to WooCommerce: no new plugin. Every capability added through MCP lives outside your WordPress install — nothing to update, nothing conflicting with your theme, nothing slowing your site down, and nothing to clean up if you stop using it.
Setup, step by step
- Create a datavessel account and connect your store. At app.datavessel.io, add WooCommerce as a source with your store’s credentials. While you’re there, connect GA4 and Search Console too — WooCommerce’s own analytics answer “what sold”; the interesting questions (“what almost sold and why”) need the joins.
- Add the connector in Claude. Desktop, claude.ai, or mobile: Settings → Connectors → Add custom connector → paste
https://mcp.datavessel.io/mcp. Using Claude Code:claude mcp add --transport http datavessel https://mcp.datavessel.io/mcp. - Sign in when the browser opens. OAuth — no API keys pasted into config files, and you can revoke access anytime.
- Verify. Ask Claude: “What WooCommerce tools do I have?” You should see product, order, and customer tools listed. If a source is missing, connect it in the app — live sessions pick up new tools automatically.
Total honest time: about two minutes plus however long your WordPress login takes.
What Claude can do with WooCommerce (and what it can’t)
Reads (run freely): products with full details, orders, customers, sales questions across any date range — plus everything else you’ve connected (analytics, search queries, ads) in the same conversation.
Writes (always with approval): product updates — descriptions, prices, SEO fields. Claude proposes, you read the exact change, then it lands. Since WooCommerce lives inside WordPress, the same connection can also work your content: the catalog and the blog posts that sell it, one conversation.
Not on the menu: anything without a tool. The AI’s capabilities are the tool list — explicit, inspectable, and scoped to what you connected. That’s the design, not a limitation: how MCP’s read/write model works.
Five prompts to run in your first session
- “Give me a health check: last 30 days of orders vs the 30 before — revenue, order count, AOV.”
- “Find my 10 best-selling products and flag any with thin descriptions or missing SEO fields.”
- “Which products get search impressions but few clicks?” (needs Search Console connected — this is your title-rewrite shortlist)
- “Draft improved descriptions for the two worst offenders from #2. Show diffs; don’t save yet.”
- “Any orders stuck in processing more than 3 days?”
By prompt five you’ll notice the pattern: these are the checks you mean to run weekly. That’s the threshold where chat graduates to scheduled agents doing the checking for you — the e-commerce autopilot step.
If something doesn’t work
Three failure modes cover nearly every setup hiccup: no WooCommerce tools listed means the store isn’t connected at app.datavessel.io yet (the tool list mirrors your connected sources — connect it and live sessions update automatically); sign-in loops usually mean the browser blocked the OAuth redirect — retry in a normal window with the account you use in the datavessel app; and a write that “does nothing” is almost always the approval flow waiting for you — check for the approval card before assuming failure. Nothing here requires touching your WordPress install itself.
WooCommerce now has its own MCP server
Since WooCommerce 10.3, with seven abilities as of 10.9, WooCommerce ships a native MCP server built on the WordPress Abilities API. It is a developer preview aimed at people building on one site, authenticated with a WordPress Application Password. It does not add approvals, a ledger, a schedule or anything outside WooCommerce, which is what the setup above gives you. When to use which, and when both: WooCommerce MCP server: native vs datavessel.
The bottom line
One pasted URL, one OAuth sign-in, and your WooCommerce store stops being a place you dig through and becomes something you talk to — live reads instantly, writes only with your explicit approval. Start with the health-check prompt; you’ll know within ten minutes whether this changes your week.
Setup details, the full tool catalog, and every supported client: datavessel MCP →
Leave a Reply