What Shopify, Shopware, Magento and WooCommerce officially offer through MCP in November 2026 and how merchants can assess it.
All four shop systems work with MCP, but with different goals and at different levels of maturity. Shopify offers MCP servers for agents that search products, build carts and create checkouts on behalf of buyers. Shopware ships a server for admin tasks in its core. WooCommerce exposes products and orders through a WordPress plugin. Adobe has announced a Commerce MCP, and Magento Open Source has no official server. This is the status in November 2026 according to the vendors.
Shopify MCP today is no longer the old Storefront MCP. According to its own documentation, Shopify removed the catalog and cart tools at /api/mcp. They are replaced by servers that follow the Universal Commerce Protocol (UCP) at /api/ucp/mcp: Storefront Catalog, Cart, Checkout, Order and Ask. If you follow older tutorials, you build on an endpoint that no longer exists in that form.
What matters is not whether a platform has MCP, but who the server is for. A server for buyers puts your products into AI assistants. A server for your team saves work in the back office. Each needs different permissions, different controls and different preparation.
This article is for managing directors, e-commerce leads and IT managers who run Shopify, Shopware, Magento or WooCommerce or who are choosing a platform right now. It is the overview for our three detailed articles on Shopware MCP in practice, the Magento MCP server and the WooCommerce MCP server. The Shopify part is new and therefore more detailed. If you are still planning a shop: with the solution25 shop subscription you can choose between Shopware, WooCommerce and Shopify.
MCP stands for Model Context Protocol. The official project site describes it as an open-source standard for connecting AI applications to external systems. It compares MCP to a USB-C port: one standard connector instead of many separate cables. AI applications such as Claude or ChatGPT use it to reach data sources, tools and workflows.
For an online store this means: an MCP server announces which tools it offers, for example “search products” or “create cart”. The assistant calls the right tool and gets structured data back. It does not have to read pages or know a separate interface for every shop.
One simple distinction helps when you compare the platforms. It explains why the offerings look so different.
There is a third group: tools for developers. They bring documentation and validation into the code editor and at first have nothing to do with your shop data. Shopify offers such tools. What exists for Adobe Commerce is covered in our Magento article.
How agents work in retail in general is explained in our articles on agentic commerce and on AI agents in e-commerce. This article only asks what the four shop systems officially offer through MCP today.
If you search for “Shopify MCP”, you find many tutorials about the Storefront MCP. That status is outdated. The page “Migrate from Storefront MCP” on shopify.dev carries the label “Removed”: the catalog and cart tools at https://{shop}/api/mcp were removed. In the changelog of June 24, 2026, Shopify had announced that the old cart tools would be maintained until August 31, 2026.
The successor is a group of servers that follow the Universal Commerce Protocol (UCP). They run at Shopify and are reachable per shop at https://{shop}/api/ucp/mcp. The documentation names UCP version 2026-08-25 as the specification. On the pages we opened we found no beta or preview label, and no explicit statement on general availability either (as of November 2026).
| Server | Job | Tools according to the documentation |
|---|---|---|
| Storefront Catalog MCP | Find products and store locations of a single shop | search_catalog, lookup_catalog, get_product, search_locations, lookup_locations |
| Global Catalog MCP | Search products across many Shopify merchants, endpoint at catalog.shopify.com | search_catalog, lookup_catalog, get_product |
| Cart MCP | Build a cart over several conversation turns | create_cart, get_cart, update_cart, cancel_cart |
| Checkout MCP | Turn a cart into a checkout and lead the buyer to payment | create_checkout, get_checkout, update_checkout, complete_checkout, cancel_checkout |
| Order MCP | Fetch the state of an order | get_order |
| Ask MCP | Answer questions about the shop’s products, policies and services | ask_business |
| Customer Accounts MCP | Actions in the customer account, such as order status and account details | discovered at runtime through tools/list |
Separately there is the Shopify AI Toolkit. It connects AI coding tools to Shopify’s developer docs, API schemas and store management through Shopify CLI. As an alternative Shopify names the Dev MCP server, which runs locally and needs no authentication. Both are aimed at developers who build themes, apps or extensions. Shopify itself points out that the toolkit does not remove the need to review and test the result.
Under the name Shopify MCP, Shopify also describes a remote MCP server that lets merchants build and run their store through the AI agent of their choice. It is meant to expose GraphQL Admin API queries and mutations, plus tools for common tasks such as creating a store, setting up a theme and managing products. The page carries the label “Coming soon”: Shopify MCP is not publicly available yet. The page does not yet name an endpoint, authentication, permissions or safeguards (as of November 2026). Until then, according to Shopify, the AI Toolkit can prepare and run supported store management tasks through the authenticated Shopify CLI. That is a tool for developers and not a counterpart to Shopware’s admin server.
With Shopify you do not run the server, Shopify does. That saves setup but moves the question of control. You should know two things: the access tiers for agents and the settings in the admin.
Shopify distinguishes agents by how they identify themselves. The documentation names three tiers.
| Capability | Token | Signed | Anonymous |
|---|---|---|---|
| Catalog tools | yes | yes | yes |
| Cart tools | yes | yes | yes |
| Checkout tools | yes | yes | no |
| complete_checkout | only with permission to complete purchases | no | no |
| Orders (get_order) | yes, with the matching scope | no | no |
Limits grow with the tier. Shopify gives concrete numbers only for the Global Catalog: by default 5 requests per second for each API client on authenticated requests. For the servers at the shop Shopify publishes no numbers and writes that the limits can change. Checkout MCP is limited more strictly than Cart MCP at every tier.
The normal case is a handoff. The agent creates the checkout and receives a continue_url. It gives this address to the buyer, who pays in the merchant’s shop. Shopify states explicitly that for general access this is how checkout completes and complete_checkout is not called.
Only agents with a token that carries the permission may complete the purchase inside the conversation. The page we opened does not describe how an agent obtains this permission. Orders have one more limit: through get_order an agent only sees orders that were placed through that agent.
The merchant view is in the Shopify Help Center under the term agentic storefronts. The key statements there:
For direct checkout in Microsoft Copilot Shopify names clear limits. It applies only to stores that sell to customers in the United States and appears only to customers based in the United States. Subscription-only products, bundles, customizable products and B2B-only products are not supported. Local delivery, pickup in store and pickup points are not available. Google Analytics and custom pixels do not fire in this checkout. Shopify says there are no fees for selling in Copilot’s direct checkout, only the standard payment processing fees.
In ChatGPT, according to the Help Center, customers buy in your online store checkout, which opens in an in-app browser or a new tab.
For merchants in the United States: Direct checkout in Microsoft Copilot is the one channel in this article that Shopify limits to US-based customers, so it is relevant for you first. Sales tax is usually calculated through a tax service integration in the shop, and an agent shows the prices your shop returns. solution25 and most Shopware partners are based in Europe, so calls usually take place in the morning, East Coast time. Prices for our own services are in euros and stay in euros.
Shopware takes the opposite route and starts with the admin. The MCP server is part of the core and runs in your own installation. According to the developer documentation, both MCP endpoints have existed since Shopware 6.7.11.0. Up to 6.7.13 you had to enable them with a flag, and since 6.7.14.0 they are always on. The MCP classes stay marked as experimental until Shopware 6.8.0 (as of November 2026 according to the vendor).
The second server is less well known. It works in the context of a sales channel and shows what a storefront shows. So it is meant for agents that act for buyers. According to the documentation, however, the core only registers the tools for discovering further tools and one tool that returns the sales channel context. The page names no core tools for catalog search, cart or checkout. Extensions can register their own tools.
Important for security: this server has no allowlist and no admin permission check. The access key of the sales channel is enough. Shopware writes that the sales channel context is the entire security boundary. The limits are deliberately tighter, at 120 calls per minute and 600 per ten minutes.
Which everyday tasks the admin server takes on is shown in Shopware MCP in practice with seven examples. For an overview of Copilot and further AI features, see Shopware AI. The basics of protocol, clients and setup are explained in MCP server for Shopware.
With Magento you have to separate two products: Adobe Commerce and Magento Open Source.
In Experience League, Adobe describes the Commerce MCP as a foundation that helps developers build custom agentic experiences from discovery to checkout, using real-time commerce data. The page names conversational product discovery, cart and checkout inside the conversation, and guidance after the purchase. But it carries the label “Coming Soon” with the note that the feature is subject to change. Editions, prices and a date are not stated there. The page was last updated on October 8, 2026 (as of November 2026).
For Magento Open Source we found no official source that describes an MCP server in the core. If you run Open Source, you use modules or connectors from agencies, vendors and the community. Their quality varies a lot, and the responsibility for selection and updates is yours.
Which projects exist, how a module inside the shop differs from a server next to the shop and what Adobe already offers developers is covered in the article on the Magento MCP server.
WooCommerce has an official path that changed considerably over the past year. The developer documentation calls the feature a developer preview. Interfaces and patterns may change in future releases (as of November 2026 according to the vendor).
The documentation does not mention cart and checkout for buyers. WooCommerce MCP is therefore a tool for your team, not a sales channel. The step-by-step setup and the move to version 11.3 are described in the article on the WooCommerce MCP server.
The table summarizes what the vendors describe in their documentation in November 2026. It does not judge which platform is better. The offerings pursue different goals and can only be compared against your own task.
| Criterion | Shopify | Shopware | Adobe Commerce and Magento | WooCommerce |
|---|---|---|---|---|
| Official server | yes, several servers following UCP | yes, in the core since 6.7.11.0 | Adobe Commerce: announced. Magento Open Source: no official source found | yes, abilities in the core, connection through the MCP Adapter plugin |
| Who runs it | Shopify, per shop at /api/ucp/mcp | you, in your own installation | not described on the Adobe page | you, in your WordPress installation |
| Catalog | yes, for one shop and across all merchants | yes, through the admin. No core catalog tool named for the Store API server | announced: conversational product discovery | yes, query and maintain products |
| Cart | yes, Cart MCP | not named in the core, possible through extensions | announced | not mentioned in the documentation |
| Checkout | yes, usually as a handoff to the shop. Completion in the conversation only for permitted agents | not named in the core | announced | not mentioned in the documentation |
| Admin tasks | announced: Shopify MCP for store management (“Coming soon”). For developers: AI Toolkit and Dev MCP | yes, data, order state, settings, theme | not described on the Adobe page. For Open Source: third-party modules | yes, products and orders |
| Access protection | agent profile, three tiers (Token, Signed, Anonymous), limits per tier | Admin: role, allowlist, dry run. Store API: access key of the sales channel | not described on the Adobe page | WordPress user with application password, check per ability |
| Maturity according to the vendor | UCP servers: no label found. Old Storefront MCP removed. Shopify MCP for store management: “Coming soon” | experimental until 6.8.0 | “Coming Soon” | developer preview |
Two notes on reading the table. First: “not named” means that the vendor page we opened says nothing about it. It does not mean that it is technically impossible. Second: the status changes quickly. WooCommerce marked the old endpoint as deprecated in version 10.9 and removed it in 11.3. Shopify removed a server and replaced it. Check the linked sources again before you decide.
MCP alone is no reason to change platforms. But the differences show where each vendor invests, and they change what you have to prepare yourself.
Your products are already reachable for agents if your store meets the requirements. Your work is in the data: complete titles and descriptions, well-kept variants, completed policies. In the admin under Sales channels, Agentic, check which channels are active and whether that fits your range. If you sell bundles, subscriptions or customizable products, you should know the restrictions of each channel. For admin tasks through an assistant, Shopify has announced the Shopify MCP server. It is not available yet.
The quick benefit is in the team: reports, stock lists, text maintenance. Start with an integration that may only read. For agents on the buyer side the Store API server is a foundation, but according to the documentation the ready-made tools for it have to come from extensions. Until Shopware 6.8, plan for changes to names and data formats.
Do not wait for the Commerce MCP while date and editions are open. If you want to connect an assistant today, choose a module with permissions per tool and a log. Keep the connection small enough that you can switch later.
The connection is set up quickly but remains a developer preview. Plan a short check after every major update. For customer data, WooCommerce says the site operator is responsible for data protection compliance.
If you do not have a platform yet, treat MCP as one of several criteria, next to product range, integrations and budget. With the solution25 shop subscription our team builds and runs the shop on Shopware, WooCommerce or Shopify. The plans are Scale at 299 euros a month, Pro at 499 euros a month and Enterprise on request, each with a 24-month minimum term and no setup fee. We choose the platform by your requirements, not by a single feature.
Whatever the platform: agents only find what is well maintained. Our articles on GEO for Shopware and on llms.txt go with this.
An MCP server gives a language model access to your shop. The model can be wrong, and it can be misled by text in product data or customer messages. The safeguards depend on who runs the server.
Legal questions about handling customer data depend on your individual case. This article is not legal advice.
The term is used for two things. Mostly it means the servers through which AI agents work with Shopify stores: Storefront Catalog, Global Catalog, Cart, Checkout, Order and Ask, which follow the Universal Commerce Protocol, plus the Customer Accounts MCP and the Dev MCP for developers. Shopify itself also calls one product Shopify MCP, a server for store management. In November 2026 it is labeled “Coming soon” and is not publicly available yet.
According to its own migration page, Shopify removed the catalog and cart tools at /api/mcp. The successor runs at /api/ucp/mcp. According to Shopify, the Customer Accounts MCP is unchanged.
No. Shopify runs the servers. According to the Help Center, agentic storefronts are active by default for eligible stores. Your job is to maintain product data and policies and to check the channels in the admin.
With Shopify the normal case leads the buyer through an address into your shop’s checkout. Only agents with a token that carries the permission may complete the purchase directly. For Shopware and WooCommerce the documentation names no core tools for checkout through MCP.
That depends on the goal. For agents on the buyer side Shopify describes the most extensive offering in November 2026. For admin tasks with fine-grained permissions Shopware describes the most extensive offering. WooCommerce covers products and orders and is a developer preview. Adobe has announced. This does not add up to a ranking.
solution25 is a Shopware Platinum Partner from Bremen, Germany, and also works with Shopify and WooCommerce. We cannot promise that an AI assistant brings revenue or replaces jobs. We can work out with you which task is worth it, which permissions it needs and what your platform actually delivers today.
Write to us through the contact page and tell us which platform you use and which task you have in mind. Then we tell you honestly whether MCP is the right way for it today.

Besnik Bilalli is the founder and CEO of solution25, the Shopware agency from Bremen. Before founding the agency in 2017, he built his own online store and grew it to more than 500 orders a day. Since then he has been helping merchants with Shopware projects, from the first budget to ongoing operations. He’s happy to answer questions about this article personally: get in touch.
Responsible for content and updates: Besnik Bilalli. Last updated: November 2026. Next content review: February 2027.