CommerceWeave MCP
Related Servers
Alternatives to CommerceWeave MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables connecting 13 e-commerce platforms such as Amazon, eBay, WooCommerce, and OTTO to Claude, ChatGPT, Copilot, and Cursor, exposing 160 tools to manage stores, orders, products, and marketplaces through natural language.AGPL 3.0
- FlicenseNot gradedqualityBmaintenanceEnables AI agents and counter staff to run inventory and fast sales for a single-branch physical store — products, stock movements (entries, sales, adjustments), reports, labels and imports — over the same database the app uses, exposed via stdio or a remote Streamable HTTP endpoint with OAuth 2.1 and access tokens. Every action is validated, permission-checked, optionally confirmed with a preview, recorded in history, and undoable, so changes made by an AI appear live in the counter UI.-
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to read from a real order and inventory database while routing every destructive write — cancellations, refunds, stock adjustments — into a pending-actions queue that a human approves or rejects in a dashboard. Includes scoped permissions, rate limiting, idempotency, and an append-only audit log so agent activity stays bounded and attributable.MIT
- AlicenseCqualityBmaintenanceEnables AI agents and CLI users to perform confirmed shop operations, manage products, orders, collections, webhooks, and promotions, and handle bounded metadata exports and private uploads through a local stdio server.8628 npmAGPL 3.0
- AlicenseCqualityDmaintenanceEnables AI agents to manage e-commerce operations across multiple platforms (Shopify, WooCommerce, Stripe, MercadoLibre) through a conversational interface.4121 npmMIT
- AlicenseBqualityCmaintenanceA read-only MCP server that lets an Agent Studio agent query a WooCommerce store's orders, products, inventory and customers, with pagination, filtering, typed errors and automatic rate-limit retry. It never mutates store data, keeping the blast radius of an agent's actions bounded to reads.7MIT
TDQS
Scored across 9 tools
Most tools target clearly distinct operations (listing connections, products, orders, per-order fetch, sales summary), and the three stock-related tools are differentiated by their descriptions (low-stock listing vs. per-connection summary vs. cross-platform comparison). The overlap between commerce_list_products and commerce_inventory_report, and the cluster of stock tools, still requires careful reading but is manageable.
All names share a `commerce_` prefix and snake_case, which is highly predictable. However, six follow verb_noun (list_products, find_product, get_order) while three are noun-only (low_stock, inventory_report, sales_summary), a minor deviation.
Nine tools is well within the sweet spot and each one covers a distinct reporting or lookup concern. No tool feels redundant enough to remove.
The surface is a coherent read/analytics layer, but commerce_find_stock_discrepancies points to `commerce_prepare_stock_update`, which does not exist on this server — a hard dead end. There is also no write path at all despite connections exposing write capability and safety mode, and no get-product detail tool.