shopware-mcp talks to your shop with the credentials you give it. Please report anything that could leak those credentials, bypass the read-only default or expose data that the tools promise to strip.
Use GitHub's private vulnerability reporting on this repository (Security → Report a vulnerability). Do not open a public issue for security problems. You will get an acknowledgement within a few days.
- Credential handling (OAuth token cache, logging, error messages)
- The
--allow-writegate anddryRundefaults - Secret scrubbing in
entity_searchand the blocked entity list - The HTTP transport's Host header check and bearer token comparison
Out of scope: Shopware itself, and deployments that expose the HTTP transport without a proxy despite the documentation.
- Give the Integration a read-only role unless you need write tools.
- Keep the HTTP transport on localhost, set
SHOPWARE_MCP_HTTP_TOKEN, or put it behind an authenticating reverse proxy. - Pin the npm version in production and review the changelog before upgrading.