ai.studio/woocommerce-gold
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WC_URL | No | Alternative to WC_STORE_URL. | |
| GOLD_LICENSE | No | Alternative to GOLD_LICENSE_KEY. | |
| WC_STORE_URL | No | WooCommerce store URL, e.g. https://yourstore.com. Alternative env var names: WOOCOMMERCE_STORE_URL, WC_URL. | |
| WC_CONSUMER_KEY | No | Woo REST consumer key (ck_…). Alternative env var name: WOOCOMMERCE_CONSUMER_KEY. | |
| GOLD_LICENSE_KEY | No | Gold license key (PRO $29 once). Alternative env var name: GOLD_LICENSE. Can also be stored in ~/.gold-mcp/license.key. | |
| KEYGEN_ACCOUNT_ID | No | Keygen CE account id for online license validation (optional; offline 7-day grace). | |
| WC_CONSUMER_SECRET | No | Woo REST consumer secret (cs_…). Alternative env var name: WOOCOMMERCE_CONSUMER_SECRET. | |
| WOOCOMMERCE_STORE_URL | No | Alternative to WC_STORE_URL. | |
| WOOCOMMERCE_CONSUMER_KEY | No | Alternative to WC_CONSUMER_KEY. | |
| WOOCOMMERCE_CONSUMER_SECRET | No | Alternative to WC_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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gold_setup_checkA | SETUP CHECK for WooCommerce Gold — run this FIRST. Shows license tier, which API keys are set vs missing (names only, never values), and the exact next step. |
| gold_wc_desc_bulk_byokA | POWER: bulk-generate unique product descriptions via YOUR OWN OpenAI key (BYOK - key stays local, charged by OpenAI not us). Reads product name+attributes -> writes description per product. Skips products that already have long descriptions unless overwrite=true. PAID ONLY PRO $29. |
| gold_wc_seo_meta_bulkB | POWER: bulk-set SEO title + meta description (Yoast/RankMath compatible _yoast_wpseo_title/_metadesc or rank_math_title/description) on many products. Trimmed to 60/155 chars automatically. BYOK. PAID ONLY PRO $29. |
| gold_list_productsA | Gold PRO $29: list Woo products via GET /wp-json/wc/v3/products — BYOK WC_STORE_URL+CONSUMER_KEY/SECRET fail-closed, no fake data. |
| gold_get_productA | Gold PRO $29: get single Woo product via GET /wp-json/wc/v3/products/{id} — BYOK fail-closed. |
| gold_create_productA | Gold PRO $29: create Woo product via POST /wp-json/wc/v3/products — BYOK fail-closed. Destructive, requires PRO. |
| gold_update_productC | Gold PRO $29: update Woo product via PUT /wp-json/wc/v3/products/{id} — BYOK fail-closed. |
| gold_update_stockB | Gold PRO $29: update Woo stock via PUT /wp-json/wc/v3/products/{id} {stock_quantity, stock_status} — BYOK fail-closed. Bulk-ready (call per SKU). |
| gold_list_ordersA | Gold PRO $29: list Woo orders via GET /wp-json/wc/v3/orders — BYOK fail-closed. |
| gold_get_orderA | Gold PRO $29: get Woo order via GET /wp-json/wc/v3/orders/{id} — BYOK fail-closed. |
| gold_update_order_statusB | Gold PRO $29: update order status via PUT /wp-json/wc/v3/orders/{id} {status} — BYOK fail-closed. |
| gold_create_refundC | Gold PRO $29: create refund via POST /wp-json/wc/v3/refunds — BYOK fail-closed. Destructive. |
| gold_list_customersB | Gold PRO $29: list Woo customers via GET /wp-json/wc/v3/customers — BYOK fail-closed. |
| gold_create_couponC | Gold PRO $29: create Woo coupon via POST /wp-json/wc/v3/coupons — BYOK fail-closed. |
| gold_get_reportsB | Gold PRO $29: get Woo reports via /wp-json/wc/v3/reports/sales etc — BYOK fail-closed. Types: sales, orders, customers, coupons, stock, revenue. |
| gold_low_stock_alertB | Gold PRO $29: low-stock alert via GET /wp-json/wc/v3/products?stock_status=onbackorder/lowstock — BYOK fail-closed. Moat: one call alerts for reorder. |
| gold_wc_batchB | BULK batch on products/orders/coupons/categories — create+update+delete up to 100 rows in ONE call (the CodeCanyon Advanced Bulk Edit $69 killer). resource: products|orders|coupons|categories. PAID ONLY PRO $29. |
| gold_wc_variationsC | List or bulk-create product VARIATIONS (size/color) — clothing shops cannot live without this; techspawn has it, we added it. PAID ONLY PRO $29. |
| gold_wc_categories_bulkB | Ensure 1-50 product CATEGORIES exist in one call (creates missing only) — SEO tagging at scale. PAID ONLY PRO $29. |
| gold_wc_coupons_bulkA | Generate up to 100 unique coupon codes in one call (PREFIX-XXXX, e.g. influencer drops) + optional usage limit. PAID ONLY PRO $29. |
| gold_wc_daily_digestB | POWER TOOL: your store's morning briefing in ONE call - today's orders + revenue + AOV, low-stock products, open orders needing action. BYOK. PAID ONLY PRO $29. |
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 21 tools
Most CRUD tools target distinct resources, but there are overlapping boundaries: gold_update_stock duplicates a subset of gold_update_product, gold_wc_batch can write to products/orders/coupons/categories alongside the individual create/update tools, and gold_get_reports, gold_low_stock_alert, and gold_wc_daily_digest all surface store metrics/stock information. Descriptions are detailed enough to usually disambiguate, but the set is not cleanly partitioned.
All tools share a gold_ prefix and snake_case, but the conventions diverge: core resource operations use verb_noun like gold_list_products and gold_create_coupon, while bulk/feature tools use a gold_wc_* pattern like gold_wc_batch and gold_wc_daily_digest, and gold_setup_check is a noun-ish outlier. This is readable but not a single predictable verb_noun schema.
21 tools is on the heavy side for a single server, but each tool addresses a concrete WooCommerce resource, reporting, or bulk-operation need, so the count is large yet justified by the domain. It stays below the extreme threshold and does not feel bloated with pointless duplicates.
The server covers product lifecycle well (list/get/create/update, stock, categories, variations) plus orders, refunds, coupons, customers, reports, and store diagnostics. Gaps include no delete/update for coupons and no customer create/update, but core store workflows and dead-ends are mostly handled.