{
  "markdown": "# mcp-woocommerce\n\nWooCommerce MCP Pack — wraps the WooCommerce REST API v3\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `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. |\n| `woo_get_product` | Fetch a single WooCommerce product by numeric ID. Returns full details including name, description, price, categories, attributes, and stock quantity. |\n| `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. |\n| `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. |\n| `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. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"woocommerce\": {\n      \"url\": \"https://gateway.pipeworx.io/woocommerce/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/woocommerce/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Woocommerce data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 3264,
  "sha": "c100fc5caaa4cb98c2358a8ad337ace0481b4c2626b1c9a8a3c477bb5aba653b",
  "repo_slug": "pipeworx-io/mcp-woocommerce",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_woocommerce_6f77b992/readme"
}