Woocommerce MCP logo

Woocommerce MCP

by wppoland

Read-only WooCommerce and WordPress data access for products, orders, sales reports, and public blog searches.

Install Woocommerce MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "wppoland-woocommerce-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@wppoland/woocommerce-mcp"
      ],
      "env": {
        "WP_URL": "YOUR_VALUE_HERE",
        "WC_CONSUMER_KEY": "YOUR_VALUE_HERE",
        "WC_CONSUMER_SECRET": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @wppoland/woocommerce-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The wppoland/woocommerce-mcp MCP server exposes read-only WordPress and WooCommerce data through five MCP tools. It uses the existing REST APIs, requiring a WordPress URL and WooCommerce read credentials for store data, while public post search needs no keys. Use it when an MCP client needs to inspect products, recent orders, sales totals, or published blog content without installing a store plugin or enabling write access.

Use cases

  • Search WooCommerce products by name or SKU
  • Review recent orders by status
  • Compare sales totals across supported periods
  • Look up published WordPress posts
  • Inspect product details by ID

Key features

  • Read-only WooCommerce REST API access
  • Product listing and product detail lookup
  • Recent order retrieval with status filtering
  • Sales reports for four periods
  • Public WordPress post search

Tools5

What Woocommerce MCP lets your agent do. Expand a tool for its parameters.

Self-reported~78 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

17/18 checks healthy over the last 80d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @wppoland/woocommerce-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads146Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed5Callable tools this server registers over MCP.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Woocommerce MCP works

What wppoland/woocommerce-mcp MCP server does

The wppoland/woocommerce-mcp MCP server connects an MCP client to an existing WordPress and WooCommerce site. It provides five read-only tools for inspecting store and publishing data:

  • list_products lists or searches products and returns fields such as name, SKU, price, stock, and permalink.
  • get_product retrieves full details for a product by its ID.
  • list_orders returns recent orders in newest-first order and can filter by status.
  • sales_report returns sales totals for the week, month, previous month, or year.
  • search_posts searches published WordPress blog posts through the public REST API.

The server does not create, update, or delete products, orders, posts, or other store records. It also does not require a plugin to be installed on the WordPress site.

How it works

The server communicates with the site’s existing REST endpoints. WooCommerce tools authenticate with a consumer key and consumer secret, while blog-post search can query any public WordPress site without WooCommerce credentials. Credentials are sent to the configured store over HTTPS as REST query authentication, so the store should use HTTPS and the keys should have read-only permission.

MCP clients invoke the tools and receive the corresponding API data. API errors are passed through with the store’s message, and credentials are not echoed in logs. Logs are written to stderr so they do not interfere with the stdio MCP protocol on stdout.

Setup and configuration

Install the wppoland/woocommerce-mcp MCP server from npm or build it from the Git repository. The project requires Node.js 18 or newer because it uses the built-in fetch implementation. A source installation uses npm install followed by npm run build; the resulting entry point is dist/index.js.

Set these environment variables before starting the server:

  • WP_URL: the WordPress site URL.
  • WC_CONSUMER_KEY: a WooCommerce REST API consumer key for store tools.
  • WC_CONSUMER_SECRET: the matching WooCommerce REST API consumer secret.

Create the WooCommerce credentials under WooCommerce settings, Advanced, REST API, and grant Read permission. search_posts remains available without the two WooCommerce variables when the WordPress site is public.

Tools and capabilities

The wppoland/woocommerce-mcp MCP server is suitable for conversational store lookups such as checking product availability, reviewing recent orders, or asking for last month’s sales total. Product search supports name and related product fields, while order retrieval supports an optional status filter. Sales periods are limited to the documented week, month, last month, and year options.

A typical Claude Desktop configuration runs the built JavaScript file with Node and supplies the three environment variables in the MCP server definition. The README also identifies Claude Code as a supported usage context.

Limitations and notes

This is a read-only interface. It cannot modify catalog data, process orders, change order status, publish posts, or perform other write operations. WooCommerce keys are required for the product, order, and sales tools, but not for public post search. The server depends on the target site’s WordPress and WooCommerce REST APIs and does not provide a separate store-side plugin.

The repository includes a check script that builds the project and verifies that all five tools register without requiring network access or credentials. The project is released under the MIT license.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Woocommerce MCP

Install it with npm using `npx -y @wppoland/woocommerce-mcp`, or clone the repository, run `npm install`, and build it with `npm run build`.

Set `WP_URL`, `WC_CONSUMER_KEY`, and `WC_CONSUMER_SECRET`. The WooCommerce key and secret are needed for store tools; public post search does not require them.

Yes. The README provides a Claude Desktop configuration that runs the built `dist/index.js` file with Node and passes the environment variables.

No. All five tools are read-only, and the server does not create, edit, or delete store data.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWoocommerce MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/wppoland-woocommerce-mcp?style=directory)](https://allmcps.com/mcp/wppoland-woocommerce-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/wppoland-woocommerce-mcp"><img src="https://allmcps.com/api/badge/wppoland-woocommerce-mcp?style=directory" alt="Woocommerce MCP on AllMCPs" /></a>