mcp-server-woocommerce
Related Servers
Alternatives to mcp-server-woocommerce
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables merchants to read shop data and propose changes to orders, pricing, catalogue, translations, and design through an MCP client, with every write previewed and confirmed in the dashboard.MIT- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to run one or more WooCommerce stores through the REST API: browsing the catalog, working through orders, issuing refunds, adjusting prices and stock in bulk, and reading sales analytics. Every write is previewed before it is applied and can be recorded to an audit log.136 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables secure, read-only access to WooCommerce store data through MCP-compatible assistants, letting users query products, orders, sales summaries, and inventory alerts without exposing store credentials.-
- FlicenseNot gradedqualityBmaintenanceEnables managing WooCommerce stores through a web dashboard and MCP, including viewing products and orders, updating stock quantities, and deleting products via the WooCommerce REST API.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search a shop's products, retrieve product details, prepare PayPal checkout links, and check order status over MCP. Payment approval remains with the buyer in PayPal.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage products, shopping carts, and orders in an online store through a well-defined MCP API.-
TDQS
Scored across 2 tools
The two tools are clearly split by action (fetch-by-id vs create), so an agent can easily tell them apart. The only softness is that 'item' is a generic placeholder rather than a named WooCommerce resource (product, order, coupon), leaving slight doubt about what object is being operated on.
Both names follow the same prefix_verb_noun pattern (example_get_item, example_create_item), which is predictable and readable. The shared 'example_' prefix reads as a template/placeholder rather than domain-specific naming, but internal consistency is solid.
Two tools is very thin for a server purporting to cover WooCommerce, which spans products, orders, customers, and coupons. It is a coherent minimal pair rather than a mismatch, but it clearly sits in the '1-2 tools feels thin' band.
Only get-by-id and create exist for a single unspecified resource: no list/search, no update, no delete, and no coverage of any actual WooCommerce entity. This surface would force agents to fail on routine e-commerce workflows such as browsing or modifying products and orders.