Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By woocommerce
Manage a WooCommerce store from Claude: diagnose revenue drops, triage orders and refunds, audit catalog AI-readiness, generate product content, and review coupon performance.
npx claudepluginhub woocommerce/woocommerce-claude --plugin woocommerce-claudeRun a comprehensive AI readiness audit of a WooCommerce store's product catalog
Use when the merchant asks whether coupons are working, which coupon codes are performing, whether discounting is eating margin, what a promotion cost, which coupons drive new customers, or which codes need attention. Produces a merchant-friendly WooCommerce coupon performance triage using existing analytics tools, with aggregated data only, no customer PII, and no suggestions to build new tools.
Use when the merchant asks to triage failed orders, on-hold orders, stuck payments, unpaid orders, payment pipeline, checkout failures, payment-gateway problems, or which orders need chasing. Produces a merchant-friendly WooCommerce payment-risk triage using existing analytics tools, with no customer PII and no suggestions to build new tools.
Generate rich, AI-optimised content for a WooCommerce product — description, FAQs, attributes, and SEO metadata
Use when the merchant asks to triage refunds, returns, refund spikes, high refund rates, refund leakage, refunded products, refunded countries, refund timing, or what is driving refunds. Produces a merchant-friendly WooCommerce refund diagnostic using existing analytics tools, with aggregated data only, no customer PII, and no suggestions to build new tools.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
AI agent skills to operate your Shopify store via native Admin GraphQL. 63 workflows across marketing, inventory, fulfillment, finance, and support.
Complete Wix eCommerce + Marketing + Events + CMS + Pipeline management for Claude Desktop Cowork — GraphQL-powered product management, AI-driven product creation, intelligent category management, performance-based categories, advanced order operations, comprehensive tax management, smart email campaign targeting with segments/labels, guided workflows, analytics, inventory, customer insights, event management with ticket sales and guest check-ins, CMS data collections CRUD, and Pipedrive-style Kanban pipeline with cart-to-customer tracking and audit trails. Includes 27 commands, 32 skills (+ plugin development guide), 2 agents.
Expert subagent and skills for WooCommerce development — plugin/extension creation, hooks/filters, REST API, checkout blocks, payment gateways, shipping methods, HPOS, catalog, admin UI, testing, deployment, and PHP 8.x patterns.
Guidelines for UI text and copy in WooCommerce. Use when writing user-facing text, labels, buttons, messages, or documentation in WooCommerce projects.
Manage Shopify stores: product creation, bulk imports, content pages, blog posts, and SEO metadata.
AI-powered Saleor e-commerce configuration with streamlined commands and intelligent discovery
QIT testing skills for WooCommerce extensions
Make any WooCommerce store AI-operable.
WooCommerce core already has native MCP support (in developer preview) — AI tools can connect and perform basic product and order operations. That's the plumbing.
WooCommerce for Claude adds the intelligence layer on top: structured store knowledge, AI readiness scoring, analytics insights, and a library of Skills that make a Woo store genuinely useful to AI.
Core MCP: "Claude can talk to your store." WooCommerce for Claude: "Claude can understand your store and help you run it better."
For a typical WooCommerce store, the plugin's load is lighter than loading the WC Analytics dashboard a few times an hour. It queries WooCommerce's pre-aggregated analytics lookup tables, caches every result for an hour, and runs nothing in the background — no cron, no polling, no sync jobs.
pnpm exec wp-env start..mcpb file. Claude Desktop registers WooCommerce for Claude automatically — no copy-paste, no JSON, no API key wrangling.The setup page auto-creates a Read-only WooCommerce REST API key (named "WooCommerce for Claude — Claude Desktop") and embeds it in the bundle. Switch to Read + Write on the same page if you want Claude to be able to create or edit products and orders. The bundle contains a credential — if it leaks, click Regenerate on the same page to revoke it instantly.
Same setup page, Manual Setup card. Pick your client from the dropdown — WooCommerce for Claude renders a copy-pasteable JSON snippet (or a claude mcp add … one-liner for Claude Code) with this store's URL and the auto-generated API key already filled in.
If you'd rather configure everything yourself — for example to drop the admin page from your workflow, ship via WP-CLI, or wire a CI deploy — the manual flow is:
In WooCommerce > Settings > Advanced > REST API, create a new key with Read or Read/Write permissions. Save the consumer key (ck_...) and consumer secret (cs_...). The MCP endpoint authenticates with the standard WooCommerce REST API key flow — ck_... as the username and cs_... as the password over HTTP Basic auth. HTTPS is required for production; HTTP works for local dev.
The recommended path is to connect through @automattic/mcp-wordpress-remote — a lightweight local proxy that translates stdio-based MCP (what most clients speak) into HTTP requests to WordPress. This works across Claude Desktop, Claude Code, and any other MCP client.
Claude Code — one command:
claude mcp add woocommerce-claude \
--env WP_API_URL=https://yourstore.com/wp-json/woocommerce-claude/mcp \
--env WP_API_USERNAME=ck_xxx \
--env WP_API_PASSWORD=cs_xxx \
-- npx -y @automattic/mcp-wordpress-remote@0.3.0
Claude Desktop / Cursor / generic — add to your MCP config manually:
{
"mcpServers": {
"woocommerce-claude": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote@0.3.0"],
"env": {
"WP_API_URL": "https://yourstore.com/wp-json/woocommerce-claude/mcp",
"WP_API_USERNAME": "ck_xxx",
"WP_API_PASSWORD": "cs_xxx"
}
}
}
}
Having trouble? See the mcp-wordpress-remote troubleshooting guide.
If your MCP client supports HTTP transport natively (some do, many don't), you can point it straight at the endpoint without the proxy. Use HTTP Basic auth with the consumer key as the username and consumer secret as the password.
You now have these tools available (plus the nine built-in woocommerce-* CRUD tools from WC core):