WooCommerce MCP Server

82 MCP tools for WooCommerce — products, orders, customers, coupons, shipping, taxes, and more.

Local serverstdio

What is the WooCommerce MCP server?

Connect WooCommerce to Claude, Cursor or any other MCP client and it stops being a tab you switch to. 82 MCP tools for WooCommerce — products, orders, customers, coupons, shipping, taxes, and more. The woocommerce mcp server is what makes that connection.

What the server does

MCP server for managing WooCommerce stores through AI assistants like Claude. Provides 101 tools covering products, orders, customers, coupons, shipping, taxes, webhooks, settings, reports, and more.

  • Full store management — — CRUD operations for products, categories, tags, brands, orders, customers, and coupons
  • Product taxonomy — — attributes, attribute terms, and variations with batch support
  • Shipping — — zones, zone methods, and shipping classes
  • Taxes — — tax rates and tax classes
  • Webhooks — — create, manage, and monitor webhook subscriptions
  • Settings — — read and update store configuration

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Read — only exploration**: Create a key with Read permissions only
  • Domain — Tools
  • Products — list, get, create, update, delete
  • Categories — list, get, create, update, delete
  • Tags — list, get, create, update, delete
  • Brands — list, get, create, update, delete
  • Attributes — list, get, create, delete
  • Variations — list, get, create, update, batch update
  • Orders — list, get, create, update, delete
  • Customers — list, get, create, update
  • Coupons — list, get, create, update, delete
  • Webhooks — list, get, create, update, delete

Credentials and setup notes

Configuration is passed through the environment: WORDPRESS_SITE_URL, WOOCOMMERCE_CONSUMER_KEY, WOOCOMMERCE_CONSUMER_SECRET, MCP_AUTH_TOKEN, MCP_SERVER_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Back up your store before using destructive tools. Use a WordPress backup plugin or your host's backup feature. - Test on staging first. Clone your production store to a staging environment and point this server at the staging URL. - Use read-only mode when exploring. Set WOOCOMMERCE_MCP_READ_ONLY=true to block all write operations — only list, get, and report tools will work.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch WooCommerce.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. WooCommerce's toolset — Read, Domain, Products and 11 more — is a fair guide to whether it matches your workflow. It is maintained by AmitGurbani; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
Readonly exploration**: Create a key with **Read** permissions only
DomainTools
Productslist, get, create, update, delete
Categorieslist, get, create, update, delete
Tagslist, get, create, update, delete
Brandslist, get, create, update, delete
Attributeslist, get, create, delete
Variationslist, get, create, update, batch update
Orderslist, get, create, update, delete
Customerslist, get, create, update
Couponslist, get, create, update, delete
Webhookslist, get, create, update, delete
Settingslist groups, get, update
Datalist countries, list currencies

How to install the WooCommerce MCP server

{
  "mcpServers": {
    "woocommerce": {
      "command": "npx",
      "args": ["-y", "@amitgurbani/mcp-server-woocommerce"],
      "env": {
        "WORDPRESS_SITE_URL": "https://store.example.com",
        "WOOCOMMERCE_CONSUMER_KEY": "ck_your_key",
        "WOOCOMMERCE_CONSUMER_SECRET": "cs_your_secret"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Back up your store before using destructive tools. Use a WordPress backup plugin or your host's backup feature. - Test on staging first. Clone your production store to a staging environment and point this server at the staging URL. - Use read-only mode when exploring. Set WOOCOMMERCE_MCP_READ_ONLY=true to block all write operations — only list, get, and report tools will work.
VariableDescriptionRequired
WORDPRESS_SITE_URLEndpoint or connection string the server talks to.Yes
WOOCOMMERCE_CONSUMER_KEYCredential the server authenticates with.Yes
WOOCOMMERCE_CONSUMER_SECRETCredential the server authenticates with.Yes
MCP_AUTH_TOKENCredential the server authenticates with.Yes
MCP_SERVER_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use WooCommerce to Read.
  • Use WooCommerce to Domain.
  • Use WooCommerce to Products.

Frequently asked questions

It connects WooCommerce to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Read, Domain, Products, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with WooCommerce directly.