woocommerce-mcp
This MCP server gives an AI client read access to a WooCommerce store (orders, products, customers, stock, sales) plus two optional, gated write tools for changing stock levels and order status.
Browse orders —
list_orders(filter by status, date range, or customer id/email/name) andget_orderfor full detail: line items, addresses, totals, shipping, refunds, customer note.Browse products —
list_productsby search term, exact SKU, stock status, or category;get_productreturns one product, with variations included for variable products.Look up customers —
list_customerssearchable by name, email, or username (guests are not listed; find them via orders).Stock reporting —
low_stock_reportfinds published products at or under a threshold (default 5) plus out-of-stock items, optionally including each variable product's variations.Sales reporting —
sales_summaryover a required date range: order count, revenue, refunds, average order value, top sellers, filtered by order status.Write stock levels (only with
WC_ALLOW_WRITES=true) —update_stocksets a product's or variation's quantity and turns on stock management.Write order status (only with
WC_ALLOW_WRITES=true) —update_order_statuschanges an order's status, triggering WooCommerce side effects such as customer emails.
Caveats visible in the schema versus the README:
Only 9 tools are registered here:
restock_priority, described in the README, is absent from this schema, and thewoocommerce://storeresource is not listed either.The README says every tool declares all four MCP hints, but read tools only expose
readOnlyHint;update_stockandupdate_order_statusomitopenWorldHint, thoughupdate_order_statusis correctly flaggeddestructiveHint: true.Read tools are safely distinguishable from the two write tools, and writes appear default-off per the README's environment-variable gate.
Read-only (optionally write-enabled) access to a WooCommerce store's REST API v3: list and fetch orders, products (including variations), customers, low-stock reports and sales summaries with revenue, refunds, average order value and top sellers. With writes enabled it can set stock quantities and change order statuses, and it exposes a store resource with the store URL, WooCommerce/WordPress versions, currency, timezone and write flag.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@woocommerce-mcp which products are below 5 in stock?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
woocommerce-mcp
An MCP server that lets Claude look at a WooCommerce store: orders, products, customers, stock and a sales summary. It talks to the WooCommerce REST API v3 with a normal API key, and it is read-only unless you switch writes on.
Works with Claude Desktop, Claude Code and any other MCP client that can start a stdio server.
What it looks like in use
Once the server is connected you can ask things like:
"What sold best in the last 30 days?"
"Which products are below 5 in stock?"
"What do I need to reorder first?"
"Show me the open orders from ann@example.com"
"Set the stock of SKU MUG-1 to 40" (only with writes enabled)
Claude picks the tool, the server answers with trimmed JSON, Claude explains it.
Related MCP server: mcp-woocommerce
Install
Python 3.10 or newer.
pipx install git+https://github.com/inmanjeffrey89-cell/woocommerce-mcpor
pip install git+https://github.com/inmanjeffrey89-cell/woocommerce-mcpEither one puts a woocommerce-mcp command on your PATH. python -m woocommerce_mcp does the same thing.
Get API keys from WooCommerce
In the WordPress admin go to WooCommerce > Settings > Advanced > REST API and click "Add key". Pick a user who can manage the store, set permissions to Read, and generate. Copy the consumer key and consumer secret right away; WooCommerce shows the secret once.
Read is enough for everything except update_stock and update_order_status. If you want those, create the key with Read/Write and set WC_ALLOW_WRITES=true (see below).
The store needs to be on HTTPS. WooCommerce only accepts key and secret authentication over HTTPS.
Configure
The server reads four environment variables:
Variable | Required | Meaning |
| yes | Store address, the WordPress root, for example |
| yes | Consumer key from the REST API page |
| yes | Consumer secret from the REST API page |
| no |
|
If one of the required variables is missing the server prints which one and exits instead of starting.
Claude Desktop
Add this to claude_desktop_config.json (Settings > Developer > Edit Config):
{
"mcpServers": {
"woocommerce": {
"command": "woocommerce-mcp",
"env": {
"WC_URL": "https://shop.example",
"WC_CONSUMER_KEY": "ck_xxx",
"WC_CONSUMER_SECRET": "cs_xxx"
}
}
}
}Claude Desktop does not read your shell PATH. If it reports that the server failed to start, replace "woocommerce-mcp" with the full path that which woocommerce-mcp prints.
Claude Code
claude mcp add woocommerce \
-e WC_URL=https://shop.example \
-e WC_CONSUMER_KEY=ck_xxx \
-e WC_CONSUMER_SECRET=cs_xxx \
-- woocommerce-mcpAdd -e WC_ALLOW_WRITES=true to enable writes. Check with claude mcp list.
Tools
Read tools (always on):
Tool | What it does |
| Recent orders, with filters for status, a date range and a customer id, email or name |
| One order with line items, addresses, totals, shipping, refunds and the customer note |
| Products with price and stock, filtered by search term, SKU, stock status or category |
| One product; variable products come with their variations |
| Registered customers, searchable by name, email or username |
| Everything at or under a stock threshold, plus items marked out of stock |
| What runs out first at the recent sales rate: units sold, sales per day and days of stock left, soonest first |
| Order count, revenue, refunds, average order value and top sellers for a date range |
Write tools (need WC_ALLOW_WRITES=true):
Tool | What it does |
| Set a product's or variation's stock quantity |
| Change an order's status |
With writes off, the server doesn't register these two tools at all. tools/list returns the 8 read tools with writes off and all 10 with WC_ALLOW_WRITES=true, so you can check the gate from outside with a single tools/list call instead of reading the code. The server's instructions tell Claude that writes are off and how to turn them on, so it can explain why it can't change stock or an order.
Every tool declares all four MCP tool hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint), so a client that checks them can tell the eight read tools from the two that change the store. update_order_status is marked open-world because a status change can make WooCommerce email the customer.
There is also one resource, woocommerce://store, with the store URL, WooCommerce and WordPress versions, currency, timezone and whether writes are enabled.
Money values are passed through as strings exactly as WooCommerce reports them, with the currency code alongside. Dates go in and come out in the store's timezone.
About WC_ALLOW_WRITES
update_order_status triggers the same side effects as changing the status in the admin: customer emails go out, stock can be released or restocked, and payment gateways may react. Setting an order to refunded only changes the label; no money moves. update_stock overwrites the quantity and turns on stock management for that product.
Leave writes off unless you need them, and when you turn them on, read what Claude proposes before you approve the tool call.
Errors
Bad keys, missing orders, a store that is not reachable, rate limits and non-JSON responses all come back as a plain sentence that says what went wrong and, where it helps, what to check. Claude sees the sentence, not a stack trace.
Limits worth knowing
sales_summary,low_stock_reportandrestock_prioritywalk the whole result set 100 items at a time. They stop at 5,000 items and settruncated: truein the result when that happens.low_stock_reportchecks published products. Passinclude_variations: trueto also check each variable product's variations; that costs one request per variable product. With it off,variable_products_uncheckedsays how many variable products were skipped.Products and variations with stock management off have no quantity to compare, so they never count as low. They show up in
untracked_count, with up to 10 of them inuntracked_examples, so a "nothing is low" answer can say what it couldn't check.restock_prioritycounts completed and processing orders from the last 30 days by default (days,status) and lists items with under 14 days of stock left (cover_days). An item that sold nothing in the window is left out, even if it was out of stock the whole time, so runlow_stock_reporttoo. Variable products work as inlow_stock_report; when stock is kept on the parent, every variation's sales count against it.The
woocommerce://storeresource readssystem_status, which WooCommerce only shows to users who can manage the store. With a more limited key you still get the URL and the writes flag.
Development
git clone https://github.com/inmanjeffrey89-cell/woocommerce-mcp
cd woocommerce-mcp
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytest
ruff check .The tests mock every HTTP call, so they run without a store. To try the read tools against a real store, export the three variables and run:
python scripts/smoke_live.pyIt prints what each read tool returns and never writes anything.
License
MIT. See LICENSE.
Available Tools
9 toolsget_orderARead-only
One order in full: line items, addresses, totals, shipping, refunds and the customer note.
Inputs: order_id (required). Returns: object
get_productBRead-only
One product with price, stock and categories. For a variable product the variations are included with their own SKU, price and stock.
Inputs: product_id (required). Returns: object
list_customersARead-only
Registered customers, optionally matching a name, email or username. Guest checkouts are not customers; find those through list_orders.
Inputs: limit, search. Returns: object
list_ordersBRead-only
Recent orders, newest first. Filter by status (pending, processing, on-hold, completed, cancelled, refunded, failed, or several comma-separated), a date range (YYYY-MM-DD or ISO 8601), and a customer (numeric customer id, or an email or name to search for).
Inputs: after, limit, before, status, +1 more. Returns: object
list_productsARead-only
Products with price and stock. Filter by a search term, an exact SKU, stock_status (instock, outofstock, onbackorder) or a category (id or name).
Inputs: sku, limit, search, category, +1 more. Returns: object
low_stock_reportARead-only
Published products whose tracked stock is at or below the threshold, plus anything marked out of stock. Walks the whole catalog. Set include_variations to also check each variable product's variations, at the cost of one extra request per variable product.
Inputs: threshold, include_variations. Returns: object
sales_summaryARead-only
Order count, revenue, refunds, average order value and the best-selling products between two dates (YYYY-MM-DD, inclusive). Counts orders in the given statuses. Walks every matching order, so a wide range takes several requests.
Inputs: after (required), before (required), top, status. Returns: object
update_order_statusADestructiveIdempotent
Change an order's status (pending, processing, on-hold, completed, cancelled, refunded, failed). WooCommerce runs its usual side effects, such as emailing the customer. Setting refunded only relabels the order; it does not send money back. Needs WC_ALLOW_WRITES=true.
Inputs: status (required), order_id (required). Returns: object
update_stockAIdempotent
Set a product's stock quantity and turn on stock management for it. Pass variation_id to set one variation of a variable product. Needs WC_ALLOW_WRITES=true.
Inputs: quantity (required), product_id (required), variation_id. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
List/get pairs on orders and products are clearly distinct, and the two update tools target different resources. The only real overlap is low_stock_report versus list_products with a stock_status filter, but the threshold-scanning semantics and extra options keep them separable.
Core tools follow a clean verb_noun pattern (list_orders, get_product, update_stock, update_order_status). The two report tools (low_stock_report, sales_summary) break the verb-first convention, but they remain short, readable, and unambiguous.
Nine tools is well within the ideal band and each one maps to a concrete WooCommerce operation (orders, products, customers, stock, sales reporting). Nothing feels padded or redundant.
Read coverage is decent (orders, products, customers, sales), but the surface is thin on writes: no create_order, no update_product for name/price/attributes, and no get_customer detail lookup. Agents hitting those tasks will dead-end.
Maintenance
Related MCP Connectors
Run a WooCommerce shop from Claude or ChatGPT: sales and stock reports, SEO, prices, products, menus and site design. Every change is a draft that you approve with one click, and you can undo it. Free forever: 100 actions a day. Skill: github.com/SakkoulasGiannis/addsynapse-woocommerce
Ask Claude or ChatGPT about your WooCommerce sales, stock and orders. Safe edits with undo.
WooCommerce MCP server for ChatGPT, Claude and any AI agent: list orders, update order status, create refund, create coupon, update product and get sales report in your own WooCommerce account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to WooCommerce yourself; Cotlet does not store your password and you need no WooCommerce API key. About the official WooCommerce API: Yes. WooCommerce has a full REST API (wc/v3) for orders, products, customers, coupons, refunds and reports, and a store owner creates consumer keys for it per store (checked 16 Oct 2026). Setup and FAQ: https://cotlet.dev/integrations/woocommerce-api-mcp-server
Let your AI manage WooCommerce and Shopify stores: products, SEO, descriptions and images.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage WooCommerce stores, including products, orders, customers, categories, coupons, attributes, variations, order notes, refunds, reports, payment gateways, meta data, reviews, settings, data, posts, and system status through natural language.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with WooCommerce stores via the WooCommerce REST API, supporting operations like listing products, orders, and customers.308 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to securely access and reason over WooCommerce orders, products, and inventory through read-only MCP tools, with PII redaction, rate-limit handling, and bounded pagination.5MIT
- AlicenseNot gradedqualityAmaintenanceEnables interaction with WooCommerce stores through the WordPress REST API, providing tools for managing products, orders, customers, shipping, taxes, coupons, payment gateways, reports, and store settings. Also supports WordPress content operations such as creating and updating posts and post metadata.MIT