
Wraps the WooCommerce REST API v3 so you can query store data directly from Claude. You get five tools covering the essentials: list and fetch individual products, orders, and customers. It's part of the Pipeworx gateway, which means you can either connect to this specific pack or tap into their full suite of 673+ data sources. Nice touch is the ask_pipeworx function that lets you skip manual tool calls and just ask questions in plain English. Reach for this when you're building workflows around e-commerce ops, need to pull order details for customer support, or want to analyze product catalogs without writing separate API clients.
WooCommerce MCP Pack — wraps the WooCommerce REST API v3
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
woo_list_products | List products from a WooCommerce store using Basic auth (consumer key + secret). Returns product IDs, names, prices, stock status, and type. Supports per_page (max 100) and page for pagination. |
woo_get_product | Fetch a single WooCommerce product by numeric ID. Returns full details including name, description, price, categories, attributes, and stock quantity. |
woo_list_orders | List WooCommerce orders, optionally filtered by status (pending, processing, on-hold, completed, cancelled, refunded, failed). Returns order IDs, totals, customer info, and line items. |
woo_get_order | Fetch a single WooCommerce order by numeric ID. Returns full order details including line items, customer billing/shipping, payment method, totals, and current status. |
woo_list_customers | List customers registered in a WooCommerce store. Returns customer IDs, names, emails, and order counts. Supports per_page (max 100) and page for pagination. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"woocommerce": {
"url": "https://gateway.pipeworx.io/woocommerce/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/woocommerce/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Woocommerce data" })
The gateway picks the right tool and fills the arguments automatically.
MIT