Ecommerce market report
Shopify and BigCommerce have the clearest official shopper-facing MCP surfaces for product discovery, cart actions, and checkout. commercetools has the broadest documented merchant and project administration surface. WooCommerce is promising for merchant product and order operations, but its official integration remains in developer preview.
Choose by actor and action. A storefront MCP helps a buyer search products, manage a cart, ask policy questions, or reach checkout. A merchant MCP lets an operator or agent read and change products, inventory, customers, discounts, orders, or settings. The same brand can expose both surfaces with completely different risk profiles.
The ratings measure documented MCP capabilities and governance fit as of September 21, 2026. They are not a payment-compliance score, uptime guarantee, or product-quality benchmark. Name the actor and irreversible step before connecting an assistant.
This table measures the documented MCP surface, not every UI, GraphQL API, REST API, or partner capability. Storefront, merchant, docs, and proxy surfaces are labeled separately.
| Platform | What the official MCP can do today | Action boundary | Rating |
|---|---|---|---|
| Shopify Storefront MCP | Store-specific official storefront server for product search, product details, policies, cart, customer account, and order flows. | Shopper-facing. No general external Admin MCP is documented; checkout is a separate boundary. | 9.5/10 |
| BigCommerce MCP | Storefront MCP with B2C and B2B tools for products, carts, checkout, shopping lists, and quotes. | Beta; store owner enables Early Access. Shopper session sync and buyer permissions carry identity and scope. | 9.0/10 |
| commercetools Commerce MCP | Managed or self-hosted project MCP for products, categories, inventory, customers, discounts, carts, quotes, orders, and more. | Use explicit tool allow-lists, field filtering, API scopes, and optional admin mode. Do not enable all casually. | 9.0/10 |
| WooCommerce MCP | WordPress MCP Adapter abilities for querying, creating, updating, and deleting products plus order status and notes. | Developer preview. Merchant operations only in the reviewed page; no documented shopper chat or checkout surface. | 7.5/10 |
| Shopify AI Toolkit or Admin API | Official developer, Sidekick, and Admin API surfaces for building merchant features. | Not a general external merchant MCP. Treat developer tools and normal APIs separately from Storefront MCP. | Not rated |
| Generic automation proxy | A service such as Zapier MCP calling connected commerce apps. | Depends on the connected app, credentials, action, and proxy controls. | Not rated |
Shopify and BigCommerce lead for buyer-facing commerce, while commercetools leads for governed merchant operations. WooCommerce has useful merchant abilities, but its integration is still a developer preview.
9.5/10
Shopify's Storefront MCP is designed for a specific store's catalog, cart, policies, and shopper flows. An agent can search products, manage a cart, answer policy questions, and help a shopper reach checkout. Do not describe it as a merchant-admin MCP: Shopify's Admin API and Sidekick app extensions are separate official surfaces.
9.0/10
BigCommerce documents B2C and B2B Storefront tool sets for product search, related products, cart operations, and checkout links, with shopping lists and quotes for B2B buyers. The server is currently beta and requires Early Access from a store owner. Session sync can carry logged-in shopper identity, pricing, and availability, so approval must be visible at cart and checkout boundaries.
9.0/10
commercetools documents a project MCP with read, create, and update tools for products, categories, inventory, customers, discounts, carts, quotes, and orders. It is the broadest merchant/project surface here, but configuration responsibility is high. Select explicit tools, scopes, and fields, and keep Knowledge MCP, which only supplies docs and API schema, separate from project access.
7.5/10
WooCommerce's MCP integration is in developer preview. It documents product queries and mutations, order queries, status updates, and notes through WordPress Abilities. This is merchant administration, not a documented consumer shopping or checkout MCP. Use a dedicated WordPress user and Application Password, and stage the connection before production.
An ecommerce MCP label does not identify the actor or financial boundary. A shopper session, a merchant project, and a developer token should never be treated as interchangeable. Verify store, environment, role, buyer, fields, and the exact operation before a tool call.
Storefront
Catalog search, product details, policies, cart, customer account, and checkout path. This can improve shopping without granting product, inventory, order, or settings administration.
Merchant
Products, inventory, customers, discounts, orders, project settings, and content. Scope by store, project, role, fields, environment, and least privilege.
Docs or proxy
A docs MCP supplies implementation guidance. A proxy routes a selected action through another service. Neither automatically has the identity, audit, or support semantics of a first-party account MCP.
1. Read catalog and policy data first. Check price, availability, variants, delivery promise, returns, customer identity, and order state without writing where possible.
2. Plan the journey in Wireslate. Map the shopper path or merchant change, including conversion, margin, shipping, discount, support, fulfillment, and approval assumptions.
3. Use the narrowest draft or sandbox action. Let the specialist MCP prepare a product update, cart, discount, content item, or order only in the smallest needed scope. Keep payment capture, refund, fulfillment, inventory, and production publish behind review.
4. Confirm, execute, and measure. A human confirms the store, buyer, amount, inventory, and action. Return conversion, margin, order value, inventory movement, fulfillment, returns, and support signals to Wireslate.
Wireslate MCP Server
Connect ChatGPT, Claude, Codex, or another AI tool to a Wireslate Whiteboard. Map the shopper or merchant journey, model margin and costs, review the change, then hand approved work to the commerce MCP that implements it.
An MCP that can read or create an order does not necessarily authorize payment, capture funds, issue a refund, or bypass checkout. Shopify and BigCommerce document checkout-link flows, while commercetools and WooCommerce expose project or order actions subject to scopes and permissions. Verify payment, capture, refund, inventory, and fulfillment actions separately.
Preview and beta status matter. BigCommerce labels its MCP beta, and WooCommerce labels its integration developer preview with breaking-change risk. A mature normal API does not make an MCP production-ready by default.
Methodology: researched September 21, 2026 using first-party vendor documentation and the official MCP specification. Ratings reflect documented action breadth and governance fit, not live testing, pricing, uptime, payment compliance, or product quality. Recheck status and use a staging store before production implementation.
Commerce MCP coverage changes as vendors add storefront tools, merchant abilities, beta gates, and identity controls. Use a staging store and test the exact financial or inventory action.
Shopify and BigCommerce are the strongest documented choices for shopper-facing search, cart, and checkout. commercetools is strongest for governed merchant and project operations. WooCommerce is useful for early product and order administration, but its official MCP is still in developer preview.
A merchant MCP acts on store administration such as products, inventory, customers, discounts, and orders. A storefront MCP helps a shopper search, compare, add to cart, and reach checkout. The permissions, data, identity, and approval requirements are different.
Do not assume it can. Shopify and BigCommerce document checkout-link flows, while commercetools and WooCommerce document project or order operations subject to scopes and permissions. Verify payment, capture, refund, and fulfillment actions separately and keep human approval at the financial boundary.
No. Shopify documents Storefront MCP for catalog, cart, policies, and shopper experiences. The Admin API is a separate API, and Sidekick app extensions are a separate built-in merchant surface. A normal Admin API or developer toolkit should not be described as a remote Shopify merchant MCP.
Wireslate holds the visual plan, financial model, team review, and human approval. The specialist ecommerce MCP performs the approved storefront or merchant action, then measured conversion, margin, order, inventory, fulfillment, and support results return to Wireslate for review.
Claims were checked against public product and help material. A red X means the feature was not identified in the reviewed material; a yellow ~ means the tool has a related capability but not the same workflow. These are not claims about every plan or future release.
Map the shopper or merchant journey, model margin and costs in a Wireslate Whiteboard, review the approval points, then hand scoped work to the ecommerce MCP.