Woocommerce Mcp

io.github.wppolandPublished by GitHub account wppolandv0.1.1Updated Oct 24, 2026

Read-only MCP server for WordPress + WooCommerce products, orders, sales, and posts.

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Read-only MCP server that lets an assistant query a WordPress and WooCommerce store for products, orders, sales, and blog posts.

What you can do
Exposes five read-only tools over the official WordPress and WooCommerce REST APIs: list_products and get_product for catalog data such as name, SKU, price, stock and permalink; list_orders for recent orders with an optional status filter; sales_report for totals over a week, month, last month or year; and search_posts for published blog posts. It never creates, edits or deletes anything in the store, and requires no plugin installation.
When to use it
Useful when an assistant should answer questions about a live store, for example last month's sales or the most recent on-hold orders, without giving it write access. Also fits public WordPress sites where only blog post search is needed, since that tool works without WooCommerce keys.
Requirements
Runs locally as a Node.js process (Node 18+), installed from the npm package @wppoland/woocommerce-mcp or built from source. Needs the environment variable WP_URL with the HTTPS base URL of the store, plus WC_CONSUMER_KEY and WC_CONSUMER_SECRET for the WooCommerce tools; search_posts works without keys. Network access to the store is required.
Before you install
The WooCommerce credentials WC_CONSUMER_KEY and WC_CONSUMER_SECRET are sent to the store over HTTPS as REST query auth, so use HTTPS and issue a key with Read permission only. Store data is read and returned to the assistant, and the server is read-only, so it does not write, send or delete store content.

Installation

In SourceWeft

  1. Open Woocommerce Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

woocommerce-mcp

A small, read-only Model Context Protocol 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, a senior WordPress developer working with WordPress since 2006. If you need this wired into a real store stack, we build WooCommerce ERP and API integrations and enterprise e-commerce architecture (headless, integrations, AI-ready data).

Tools

ToolWhat it doesNeeds WooCommerce keys
list_productsList / search products (name, sku, price, stock, permalink)yes
get_productFull details for one product by idyes
list_ordersRecent orders, newest first, optional status filteryes
sales_reportSales totals for a period (week / month / last_month / year)yes
search_postsSearch published blog posts (public WP REST API)no

Everything is read-only. The server never creates, edits, or deletes anything in the store.

Install & build

From npm (package name is scoped - the unscoped woocommerce-mcp name is locked on the registry):

bash
npm install -g @wppoland/woocommerce-mcp# or: npx @wppoland/woocommerce-mcp

From source:

bash
git clone https://github.com/wppoland/woocommerce-mcp.gitcd woocommerce-mcpnpm installnpm run build

Configure

Set three environment variables:

VarRequiredExample
WP_URLyeshttps://shop.example.com
WC_CONSUMER_KEYfor wc_* toolsck_xxx
WC_CONSUMER_SECRETfor wc_* toolscs_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 Read access only.

Use with Claude Desktop / Claude Code

Add to your MCP client config (e.g. claude_desktop_config.json):

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."

Docs on wppoland.com

Articles (off-site)

Field notes published on DEV (not duplicates of wppoland.com pages):

Show HN: discussion

Verify

bash
npm run check   # builds, then asserts all five tools register (no network/credentials needed)

Notes

  • 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.

License

MIT © WPPoland

Source: README.md at commit 0943ad2

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts