Shopware and AI: Is there an MCP server for Shopware?

Shopware is a platform for online shops that you can run yourself, use as PaaS or use as SaaS. If you want an AI assistant such as Claude or ChatGPT to work with products and orders, the first question is: is there an MCP server for it?

In short

Yes. Shopware ships an official MCP server in the core. It is still experimental, according to Shopware until version 6.8. It has two endpoints: one to manage the shop, and one for agents that use a shop like a customer.

What Shopware offers itself

The MCP server in the core. According to Shopware, it arrived with version 6.7.11.0 behind the MCP_SERVER feature flag. From 6.7.14.0 the flag is gone, and a session first shows only three tools for searching and enabling. The client enables further tools group by group. According to the docs, claude.ai reads the tool list only once per connection, so a tool enabled during the conversation stays invisible there. Since 6.7.15.0 you can therefore name groups in the connection URL (?toolsets=). The server uses Streamable HTTP. The docs give setup steps for Claude Desktop, Claude Code, Cursor and Codex. In its blog of 17 July 2026, Shopware also names ChatGPT and aims the server at developers, agencies and enterprises. It describes Copilot as the assistant for merchants.

Administration endpoint /api/_mcp. Sign-in uses the credentials of a Shopware integration or an OAuth token. According to the tools reference, the core has generic tools to search, read, create, update and delete any record. It adds tools for system settings, media upload, order state and theme configuration. Most write tools run as a dry run by default. Only dryRun=false writes for real. The media upload writes at once. Shopware checks the integration’s permissions on every call. Administrators also set an allowlist of the tools a client may see.

Store API endpoint /store-api/_mcp. According to Shopware, it runs in the context of a sales channel and is meant for agents that use a shop like a customer. Sign-in needs the sales channel’s access key, but no customer login. Besides the tools for searching and enabling, the core ships only one tool there, which reads the context. The allowlist does not apply to this endpoint: every registered tool is open to every client that can sign in to the sales channel. This endpoint is experimental too.

Extensions. Plugins, Symfony bundles and apps can add their own tools. According to Shopware, there are the packages SwagMcpMerchantTools for merchant workflows such as revenue reports and SwagMcpDevTools for logs. Shopware calls both an experimental proof of concept with no compatibility guarantee that may be removed at any time. The earlier standalone repository shopware/shopware-admin-mcp is deprecated and archived, according to its README.

Agentic Commerce. According to the help centre, the Agentic Commerce extension is in beta. It publishes a UCP profile at /.well-known/ucp so that AI agents can find the shop. MCP is one of the transports you can select, starting with Shopware 6.7. According to the help centre, the connection to the ChatGPT marketplace works only in the US and is currently not available in Europe.

Copilot in the Administration. According to Shopware, the assistant is available to all customers from version 6.7.1.0, including the free Community Edition. Advanced skills cost extra through Shopware Intelligence+ from 6.7.3. For Data Insights and the agentic features, where Copilot carries out tasks in the Administration, the help centre names a limited free quota per month. After that the shop needs Intelligence+. The pricing page says you must first sign up to Intelligence+ for the agentic features. The same page lists AI-assisted content creation for Rise. The older help page on Shopware AI requires the Commercial Extension for these features. Shopware itself calls Copilot a beta. The help page on Copilot names version 6.7.13.0 or newer. The merchant must review and approve every proposed action. According to the docs, Copilot uses the /api/_mcp endpoint of its own shop. Shopware writes that the Copilot infrastructure is fully hosted in Europe. According to Shopware, inputs are not used to train the models. According to the help centre, Shopware does record requests to improve the product.

Two APIs. According to Shopware, the Admin API gives integrations read and write access to every entity. The Store API is the customer-facing interface for catalog, cart, checkout and account, also for headless frontends.

Operating model and data location. According to Shopware, Shopware handles updates, hosting and infrastructure for SaaS. For PaaS Native, Shopware says data lives in AWS Frankfurt. We found nothing from Shopware on the location of the SaaS variant. The documentation does not say whether the MCP server is available on SaaS. It says only that apps, as extensions of the server, work in Shopware Cloud.

What the community offers

According to its README, bnymnDev/shopware-mcp works through the Admin API. It is read-only by default. Write access needs the --allow-write switch, and even then every write first shows the request as a dry run. According to its README, kochfreiburg/shopware-mcp-server offers six read tools for products and categories through the Store API. It runs on AnythingMCP, self-hosted or at its cloud provider in Frankfurt.

We read further GitHub projects but did not test them. According to its README, markus-michalski/claude-mcp-shopwareadmin offers 43 tools for shop management with Claude Code. According to its README, the valantic UCP bridge connects agents to shops that offer UCP. According to its README, dithom/shopware-mcp is for fixing bugs in Shopware plugins, not for shop management.

We found two commercial providers. According to its connector page, AnythingMCP offers a Store API connector with 6 tools. It is the connector from the kochfreiburg repository. datavessel describes in its blog a hosted server for Claude and ChatGPT with approvals. Both pages are vendor statements. They do not prove how the providers process shop data or where they store it. We found no Zapier app or viaSocket page for Shopware. Zapier lists only a different product, “Shop-Ware”.

What this means for your company

• The official server is experimental. Plan for tool changes and check your Shopware version, at least 6.7.14.0.
• Create a dedicated role with the needed permissions for the integration. Avoid --admin, and narrow the allowlist.
• The Store API endpoint has no allowlist. Register only tools there that protect their own data access.
• What reaches the AI assistant falls under its terms, no longer under Shopware’s.