wp-woo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WC_KEY | No | WooCommerce consumer key, required for WooCommerce tools | |
| WP_URL | Yes | Site URL, no trailing slash | |
| WP_USER | No | WordPress username, required for WordPress tools | |
| WC_SECRET | No | WooCommerce consumer secret, required for WooCommerce tools | |
| WP_MCP_MODE | No | read (default) or write | read |
| WP_APP_PASSWORD | No | WordPress application password, required for WordPress 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 |
|---|---|
| wp_site_infoA | Show which capabilities are configured (WordPress, WooCommerce) and whether write mode is on. |
| wp_list_postsB | List WordPress posts. Optionally filter by status or search text. |
| wp_get_postC | Get one WordPress post, including its content. |
| wp_create_postB | Create a WordPress post. Always created as a draft unless the owner has allowed otherwise. Requires write mode. |
| wp_update_postA | Update a WordPress post's title, content or excerpt. Cannot publish; publishing is done by a human in wp-admin. Requires write mode. |
| wp_trash_postA | Move a WordPress post to the trash (recoverable). Never permanently deletes. Requires write mode. |
| wp_list_pagesC | List WordPress pages. |
| wc_list_productsC | List WooCommerce products. Filter by search text, SKU or stock status. |
| wc_get_productC | Get one WooCommerce product with its description. |
| wc_create_productB | Create a simple WooCommerce product as a draft. Requires write mode. |
| wc_update_productB | Update a WooCommerce product's price, sale price, stock or description. Cannot change publish status. Requires write mode. |
| wc_list_ordersB | List WooCommerce orders, newest first. Filter by status. |
| wc_get_orderC | Get one WooCommerce order. |
| wc_update_order_statusA | Change a WooCommerce order's status (for example processing to completed). Cannot refund. Requires write mode. |
| wc_sales_reportC | Sales totals for a period. Uses WooCommerce's reports endpoint. |
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 15 tools
The wp_/wc_ prefixes plus action names cleanly separate WordPress content tools from WooCommerce commerce tools, and no two tools do the same thing. The only soft spot is posts vs. pages: wp_get_post/wp_update_post have no page equivalents, so an agent must infer that wp_list_pages is read-only and not a candidate for page retrieval or edits.
Nearly all tools follow a strict prefix + verb_noun pattern (wp_list_posts, wp_get_post, wc_update_order_status), which is very predictable. wp_site_info breaks the pattern as the one noun-only tool, a minor deviation.
15 tools is well within a healthy range and each one maps to a distinct resource-and-action pair across two domains. Nothing feels padded or redundant; the read/write split per resource is proportionate.
Posts have full read/create/update/trash coverage and products and orders have solid read/update surfaces, but pages are list-only with no get, create or update, and there is no product deletion, no customer tools. Refunds and publishing are explicitly out of scope, which is a deliberate but real dead end.