Shopware MCP

What shopware-mcp does

The shopware-mcp MCP server gives an MCP host a focused interface to a Shopware 6 shop instead of exposing the full Admin API directly. It returns compact JSON for common store operations, including products, orders and order history, documents, customers, categories, promotions, reviews, payment and shipping methods, plugins, stock, sales channels, scheduled tasks, and trading settings.

Its diagnostic tools cover both back-office data and the customer-facing buying path. checkout_simulate creates a temporary cart through Shopware’s Store API, while storefront_search investigates product visibility. The temporary checkout is deleted and does not create an order.

The server also provides operational analysis. shop_pulse compares current order activity with matching hours on recent weeks. shop_audit combines seventeen checks covering order processing, stock, storefront configuration, promotions, reviews, scheduled tasks, extensions, and selected EU-duty indicators. sales_report, customer_report, and stock_forecast provide aggregates and inventory coverage calculations.

How it works

The MCP host communicates with the server, which communicates with the Shopware 6 Admin API. Storefront checkout simulation uses Shopware’s Store API. At startup, the server checks installed extensions and registers additional supported tools, so the available tool set can differ between shops.

For less common data, entity_schema describes Shopware entities, including supported custom entities from plugins, and entity_search applies Shopware Criteria filters and aggregations. Credential-bearing entities are refused, and secrets in other responses are scrubbed.

Setup and configuration

The package is published as shopware-mcp for Node.js. The README documents a shopware-mcp setup command that logs in as an administrator and creates a role with the privileges required by the tools. The supplied material does not specify the package-install command, connection environment variables, or the complete configuration schema.

The audit can run outside an MCP host with shopware-mcp audit, making it suitable for cron or CI. shopware-mcp brief --html brief.html generates a self-contained HTML report containing the pulse, audit, and recent sales; --slack adds a one-paragraph summary for a channel.

Tools and capabilities

• Query products, orders, customers, categories, promotions, reviews, stock, channels, plugins, and store settings.
• Simulate checkout conditions for guests or customers without placing an order.
• Inspect storefront search visibility and explain common checkout failures.
• Produce sales, customer, stock-forecast, pulse, audit, and entity-query results.
• Perform fifteen narrow write operations when explicitly enabled, including shipping, payment-state changes, refunds, stock corrections, notes, documents, products, promotions, customer updates, tags, and review moderation.

Limitations and notes

The server starts read-only. Write access requires --allow-write; even then, writes begin as dry runs showing the request, and a write budget can limit the number of real changes made by a process. The available tools depend partly on installed extensions.

The audit and reports are based on Shopware data and configured store behavior; they do not replace review of the underlying shop. Checkout simulation is intentionally non-persistent: it uses a throwaway cart, deletes it, and does not submit an order. The supplied README excerpt does not identify client-specific setup requirements or list environment variables.