Store platform

Shopware MCP Server

Shopware's built-in MCP server (Shopware 6.7.14+) lets AI clients work with a store through the Admin API endpoint /api/_mcp and a store-facing /store-api/_mcp, with progressive tool discovery and extension via plugins and apps.

What it is and why it matters

What it does

• Expose admin and storefront capabilities to MCP clients
• Authenticate with an integration created by bin/console integration:create
• Discover tools progressively, starting from shopware-tool-search
• Extend with plugins, Symfony bundles or apps (Resources/mcp.xml)

Best for

Shopware 6.7 merchants and agencies who want a first-party MCP on their own installation.

How to connect it

1. Check the prerequisites as described in the documentation: Shopware 6.7.14.0 or later, and symfony/mcp-bundle installed (verify with composer show symfony/mcp-bundle). On 6.7.11.0 to 6.7.13.x, set MCP_SERVER=1 in your .env file first.
2. Create an integration with bin/console integration:create "My MCP Client". The documentation example adds --admin, which gives full Admin API access. For anything beyond testing, omit it, create an ACL role with only the permissions you need and assign it to the integration. The command prints an access key and a secret.
3. Add the server to your AI client, as described in the documentation. Claude Desktop and Cursor use a JSON config with type streamable-http. Claude Code uses type http. Codex uses config.toml with environment variable names for the headers. In each case the URL is your shop address followed by /api/_mcp, and the credentials go in the sw-access-key and sw-secret-access-key headers.
4. Keep the credential files out of version control. Do not commit .mcp.json, .cursor/mcp.json or similar files.
5. Open or restart the client and look for the Shopware server in the tools panel. The first connection may take a few seconds. Run bin/console debug:mcp to list the registered capabilities.
6. Restrict what can be discovered and called. In Settings → Integrations, use Edit MCP Allowlist on your integration. Then try a read-only prompt such as listing products.

Exact commands and addresses change. Use the official documentation for the current steps.

Installation guide for Shopware MCP Server

Client-by-client steps, what to prepare, the first prompts to run and fixes for common errors.

ClaudeChatGPTGeminiMicrosoft CopilotPerplexityCursorClaude Code

→

Questions you can ask it

• Show all products in my store.
• Find products with stock below five units.
• Find all active products without descriptions.
• Suggest SEO-friendly meta titles for the products in one category, and show them to me without saving anything.

What it cannot do

• It does not work on Shopware versions older than 6.7.11.0, and the discovery flow described here needs 6.7.14.0 or later.
• It is not a hosted service. You run it on your own Shopware installation, and someone has to create the integration and edit client config files.
• It is experimental until Shopware 6.8, so APIs and tool names may change and saved prompts or workflows may need updating.

Staying safe

• The --admin flag grants full Admin API access. For production, omit it and use a dedicated ACL role with only the permissions needed. Start with read-only access.
• Use the per-integration MCP allowlist (Settings → Integrations → Edit MCP Allowlist) to limit which tools, resources and prompts can be called. Enabling a tool also enables its dependencies. For example, enabling shopware-entity-delete also enables entity search and schema.
• Integration credentials do not expire while the integration exists, so treat them like a password. Never commit them to version control, and delete the integration if a key leaks. Run price changes or deletions only as supervised tasks, and ask for a preview first.

Watch out for: Experimental until Shopware 6.8: APIs and tool names may change. An --admin integration grants full Admin API access, so restrict it.

Frequently asked questions