Show HN: A read-only MCP server for WooCommerce

WPPoland released a read-only Model Context Protocol server for WooCommerce that allows AI assistants like Claude to query live store data—products, orders, sales, and blog posts—via existing REST APIs without requiring plugins or write access. The open-source tool requires Node 18+ and WooCommerce API keys with read permissions, enabling natural language questions about store operations.

A small, read-only Model Context Protocol https://modelcontextprotocol.io server for WordPress + WooCommerce . It lets Claude or any MCP client answer questions about a live store — products, orders, sales, and blog posts — over the official REST APIs. No writes, no plugins to install on the store: it talks to the existing WordPress/WooCommerce REST endpoints. Built and maintained by WPPoland https://wppoland.com/en/ — senior WordPress & WooCommerce engineering. If you need this wired into a real store stack, we build WooCommerce ERP and API integrations https://wppoland.com/en/woocommerce-erp-integration/ and enterprise e-commerce architecture https://wppoland.com/en/enterprise-solutions/ headless, integrations, AI-ready data . | Tool | What it does | Needs WooCommerce keys | |---|---|---| list products | List / search products name, sku, price, stock, permalink | yes | get product | Full details for one product by id | yes | list orders | Recent orders, newest first, optional status filter | yes | sales report | Sales totals for a period week / month / last month / year | yes | search posts | Search published blog posts public WP REST API | no | Everything is read-only . The server never creates, edits, or deletes anything in the store. git clone https://github.com/wppoland/woocommerce-mcp.git cd woocommerce-mcp npm install npm run build Set three environment variables: | Var | Required | Example | |---|---|---| WP URL | yes | https://shop.example.com | WC CONSUMER KEY | for wc tools | ck xxx | WC CONSUMER SECRET | for wc tools | cs xxx | Create the WooCommerce keys in WooCommerce → Settings → Advanced → REST API → Add key with Read permission. search posts works without keys against any public WordPress site. The keys are sent to your own store over HTTPS as REST query auth. Use HTTPS, and give the key Readaccess only. Add to your MCP client config e.g. claude desktop config.json : { "mcpServers": { "woocommerce": { "command": "node", "args": "/absolute/path/to/woocommerce-mcp/dist/index.js" , "env": { "WP URL": "https://shop.example.com", "WC CONSUMER KEY": "ck xxx", "WC CONSUMER SECRET": "cs xxx" } } } } Then ask things like "What were last month's WooCommerce sales?" or "List the 5 most recent orders that are on hold." npm run check builds, then asserts all five tools register no network/credentials needed - Node 18+ uses the built-in fetch . - Logs go to stderr so they never corrupt the stdio MCP protocol on stdout. - API errors are surfaced with the store's message; credentials are never echoed. MIT © WPPoland https://wppoland.com/en/