WooCommerce MCP Pack — wraps the WooCommerce REST API v3
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 36 tools
The set is dominated by overlapping 'answer a question' meta-tools — ask_pipeworx, ask_pipeworx_beta (admittedly identical to ask_pipeworx), ask_pipeworx_grounded, deep_research, entity_profile, compare_entities and recent_changes all claim overlapping territory, and the six Polymarket tools (edges, arbitrage, kalshi_spread, fill_risk, edge_tracker, bet_research) use nearly identical market-scanning language. Descriptions do give usage guidance, but the boundaries between the router variants are blurred and selection will be error-prone.
Nearly everything is snake_case with predictable verb_noun or noun_verb structure (list_orders, get_product, compare_entities, validate_claim). The only deviation is two competing namespacing conventions (woo_ prefix on WooCommerce tools vs. bare/pipeworx_ names on the rest), which is a minor inconsistency rather than a stylistic clash.
36 tools is heavy for the stated WooCommerce scope, and only 5 of them are actually WooCommerce operations — the rest belong to a general Pipeworx data gateway. The count is inflated by a large, loosely-related catalog bolted onto a small e-commerce core.
For a WooCommerce server the surface is severely read-only: list/get for orders and products and a customer list, with no create, update, delete, refund, coupon, category, or order-status-transition operations. Agents needing to fulfill, modify, or manage a store hit a dead end almost immediately.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "when-will-bitcoin-hit-150k"
- },
- {
- "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
- }
-]New value: +[
+ {
+ "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ },
+ {
+ "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."polymarket_kalshi_spread1 field changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "will-bitcoin-reach-100k-in-july-2026"
- },
- {
- "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
- }
-]New value: +[
+ {
+ "market": "when-will-bitcoin-hit-150k"
+ },
+ {
+ "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."polymarket_kalshi_spread1 field changedInput schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."Chargebee MCP Pack — wraps the Chargebee API v2
Shopify MCP Pack — wraps the Shopify Admin REST API (2024-01)
Klaviyo MCP Pack — wraps the Klaviyo API for email marketing
Add one secure layer between your agents and this server.