woocommerce-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WOOCOMMERCE_URL | Yes | The URL of your WooCommerce store (e.g., https://your-store.com) | |
| WOOCOMMERCE_CONSUMER_KEY | Yes | Your WooCommerce consumer key | |
| WOOCOMMERCE_CONSUMER_SECRET | Yes | Your WooCommerce consumer secret |
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 |
|---|---|
| getRecentOrdersD | – |
| getOrderByIdD | – |
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 are clearly distinct: one retrieves recent orders, the other retrieves a single order by ID. There is no overlap in their purposes.
Both tools follow a consistent camelCase verb_noun pattern (getRecentOrders, getOrderById), making naming predictable.
With only 2 tools for a WooCommerce server, the tool surface is far too thin for the typical scope of e-commerce operations.
The server only provides order retrieval, missing critical CRUD operations for orders, products, customers, and other WooCommerce entities.