WooCommerce MCP server (read-only)
Our verdict
Our open-source read-only MCP server for WooCommerce and WordPress. Agents query products, orders, and sales reports; no write access, no store plugin. Read-only by design keeps a live store safe to point AI at.
Practitioner brief
What it is
Our open-source MCP server (MIT, TypeScript) that lets Claude or any MCP client read a live WordPress + WooCommerce store over the official REST APIs: list_products, get_product, list_orders, sales_report, and search_posts. Nothing to install on the store itself - it talks to endpoints WooCommerce already ships. search_posts works keyless against any public WordPress site, so you can demo it before generating a credential.
Why read-only is the whole design
There are no write tools, by decision, not omission. An agent that can only read cannot oversell stock, mangle a price, or cancel an order because it misread a prompt - the worst outcome is a wrong answer, not a wrong database. The second layer is the credential: the WooCommerce key is created with Read permission only, so even a hypothetical write attempt is refused by the store. Two independent layers have to fail before anything changes.
Stack and shipping status
TypeScript on the official @modelcontextprotocol/sdk with zod schemas and stdio transport, so it drops into Claude Desktop or Cursor without a hosted endpoint. A multi-stage node:22-alpine Dockerfile passes MCP introspection (initialize plus tools/list). Listed on Glama with a quality score; the awesome-mcp-servers listing is in review. Why Trial and not Adopt: the write-path question (quotes, order intents) is deliberately unanswered - that is a separate, human-gated project.
Added: 2026-07-07 · Last reviewed: 2026-07-07