--- title: "Shopware MCP server · Connect AI agents to your Shopware shop" description: "Connect inference.eu agents to the MCP server built into Shopware 6. Search products, orders and customers, and update entities within your integration's ACL." canonical: "https://inference.eu/connect/shopware/" language: "en" --- MCP servers · ERP # Shopware MCP server: connect AI agents to Shopware from the EU Shopware 6 ships a native MCP server with the core platform, still marked experimental until Shopware 6.8. It gives an agent structured access to your shop's data through the Admin API, with Shopware's own permission checks on every call. inference.eu agents connect to it over HTTP with integration credentials. [Contact sales](https://inference.eu/contact/)[What agents can do with it](#tools) 1. 01Authentication: API key 2. 02Official server 3. 03EU data centres ## What agents can do with it - 1 ### Entity search and retrieval \`shopware-entity-search\` and related \`shopware-entity-\*\` tools find and read products, orders, customers and other entities through the Data Abstraction Layer, with filters and associations. - 2 ### Entity changes and order states Create and update entities, change order states and manage media, always checked against the ACL of the integration or user behind the connection. - 3 ### System configuration and extensions \`shopware-system-config-\*\` tools read and change shop settings, and plugins or apps such as SwagMcpMerchantTools can add merchant workflow tools, prompts and resources of their own. ## What Shopware and its MCP server are shopware AG, based in Schöppingen, Germany, makes Shopware 6, an open-source e-commerce platform used by many European retailers and brands. Since version 6.7.11.0 the core ships an MCP server at `/api/_mcp` for the Admin API and a second one at `/store-api/_mcp` for shopper-facing agents. Both use Streamable HTTP. From 6.7.14.0 the server is on by default and offers progressive tool discovery: a small default tool set plus search, so the agent loads only the toolsets it needs. Shopware calls it experimental until 6.8, so tool names may still change. ## What agents can do with Shopware A merchandising agent can find products without descriptions or images in a category, draft missing texts in German and French, and update them after review. A customer service agent can look up an order by number, read its delivery and payment state, and move it to the next state once a person confirms. Operations teams can ask for orders stuck in "in progress" for more than three days, or list customers who ordered a recalled product. Developers can inspect system configuration across sales channels while debugging. ## Setup and authentication Create an integration in Shopware for the agent. For production, do not use the `--admin` flag; create an ACL role with only the permissions the agent needs and assign it to the integration. You receive an access key ID and a secret access key. On inference.eu, add the Shopware connector to an agent, enter your shop's `/api/_mcp` URL and the two integration credentials. They are stored encrypted in the EU and sent as `sw-access-key` and `sw-secret-access-key` headers. In the Shopware admin you can also limit which tools the integration may call. ## Data protection and where the data goes The MCP server runs inside your own Shopware installation, wherever you host it, so shop data does not pass through Shopware's company servers unless you use Shopware's cloud offering. Requests go from the agent straight to your shop. On inference.eu, the model that reads orders and customer records runs in EU data centres, and your integration credentials are stored encrypted in the EU. Orders contain names, addresses and purchase history, so give agents only the entities their task needs. ## Approvals and safe use Shopware enforces ACL checks on every tool call, applies per-principal rate limits and lets you allowlist tools per integration and per user. Note that MCP resources are not ACL-checked yet, so treat everything in an authenticated session as readable. On inference.eu you can require a person to approve write calls, such as changing an order state, updating prices or editing system configuration, while product and order lookups run freely. Test in a staging shop first, because the feature is still experimental. ## Shopware Vendor shopware AG Vendor based in Germany Category ERP Authentication API key Transport Remote (HTTP) Server [Official server](https://developer.shopware.com/docs/products/tools/mcp-server/) Documentation [developer.shopware.com](https://developer.shopware.com/docs/products/tools/mcp-server/getting-started.html) ## Shopware: common questions The questions buyers, developers and legal teams ask us most. Something missing? Ask us directly. Yes. Shopware 6 includes a native MCP server in the core platform since version 6.7.11.0, with an Admin API endpoint at /api/\_mcp and a Store API endpoint at /store-api/\_mcp. It is marked experimental until Shopware 6.8. Shopware 6.7.14.0 or later is the simplest, because the feature flag is gone and progressive tool discovery is available. On 6.7.11.0 to 6.7.13.x you must set MCP\_SERVER=1. The symfony/mcp-bundle package must be installed. With the access key ID and secret access key of a Shopware integration. You enter them in the connector, where they are stored encrypted in the EU, and the agent sends them as headers to your shop's MCP endpoint. Yes, in three ways: an ACL role on the integration, a tool allowlist per integration and per user in the Shopware admin, and approval rules on inference.eu that ask a person before write calls run. The Admin API server at /api/\_mcp is for back-office work with ACL-checked access to all entities. The Store API server at /store-api/\_mcp runs in a sales channel context for shopper-facing agents, with the same data a storefront sees. Yes. Plugins and Symfony bundles register tools, prompts and resources through service tags, and apps declare them in Resources/mcp.xml. Shopware's own SwagMcpMerchantTools extension adds merchant workflow tools as an example. The MCP server runs inside your Shopware installation, so requests go from the agent to your own shop. The model on inference.eu that reads the results runs in EU data centres, and your credentials are stored encrypted in the EU. Shopware labels it experimental until 6.8, and tool names may change. Many teams start with read-only roles in a staging shop, then allow selected writes with human approval once the workflows are stable. [Ask a question](https://inference.eu/contact/) ## Related [All MCP servers](https://inference.eu/connect/#directory) - [MollieConnect inference.eu agents to the official Mollie MCP server. Look up payments, settlements and customers, and create payment links or subscriptions with approval.Banking and payments](https://inference.eu/connect/mollie/) - [AdyenConnect inference.eu agents to Adyen's official MCP server. Create payment sessions and links, handle refunds and cancels, and manage terminals and webhooks.Banking and payments](https://inference.eu/connect/adyen/) - [OdooConnect inference.eu agents to the MCP server built into Odoo AI. Search and group records across apps, and create or update records you expose as tools.ERP](https://inference.eu/connect/odoo/) - [n8nConnect inference.eu agents to n8n's built-in MCP server to search and run the workflows you expose, and build workflows and data tables, with approvals.Automation](https://inference.eu/connect/n8n/) ## Move your AI workloads to EU infrastructure Tell us which models you use and roughly how much traffic you have. We reply within one working day with pricing and next steps. - Reply within one working day - Pricing for your volume - DPA ready to sign