woocommerce-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WP_URL | Yes | Base URL of the WordPress/WooCommerce site, e.g. https://shop.example.com | |
| WC_CONSUMER_KEY | No | WooCommerce REST API consumer key (required for product/order/sales tools) | |
| WC_CONSUMER_SECRET | No | WooCommerce REST API consumer secret (required for product/order/sales tools) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_products | List or search WooCommerce products. Returns id, name, sku, price, stock status and permalink. |
| get_product | Get a single WooCommerce product by id, with full details. |
| list_orders | List recent WooCommerce orders, newest first. Optionally filter by status. |
| sales_reportA | WooCommerce sales totals for a period (week, month, last_month, year). Gross sales, orders, items. |
| search_postsA | Search published WordPress blog posts (public REST API, no WooCommerce keys required). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools serve entirely different purposes: one provides WooCommerce sales reports, the other searches WordPress blog posts. There is zero overlap in functionality, making it impossible to confuse them.
Tool names use different patterns: 'sales_report' is a noun phrase, while 'search_posts' follows a verb_noun pattern. This inconsistency makes the set feel ad hoc rather than systematically named.
With only 2 tools for a 'woocommerce-mcp' server, the count is far too low. While a minimal server could be justified, the expected scope for WooCommerce typically includes many more operations (e.g., products, orders, customers).
The tool surface is severely incomplete for WooCommerce. Key operations like managing products, orders, or customers are entirely missing, and the inclusion of a general WordPress search tool unrelated to e-commerce does not address the core domain.