Shopware MCP Server: Native vs datavessel — Which One for Your Shop?

There are now two ways to get a Shopware MCP server. The native one ships inside the core platform: from 6.7.14 every shop exposes an MCP endpoint that AI clients such as Claude, Cursor and Copilot can call, with Shopware’s own permissions enforced on every request. datavessel’s hosted one connects the same shop to Claude or ChatGPT, but wraps it in approvals, a ledger, scheduled agents, and the rest of your stack. They solve different problems, and many shops will end up with both. This post is the comparison; the setup itself is in our guide to connect Claude to your store.

What changed: Shopware’s MCP server moved into the core

Until mid-2026 the official option was a standalone package, shopware-admin-mcp, that you ran locally with Node and a set of integration credentials. Shopware archived that repository on July 10, 2026. Its replacement is not a package at all. MCP support is now part of Shopware itself.

The facts that matter for a decision:

• Version. Shopware 6.7.14.0 or later. On 6.7.11 to 6.7.13 you can switch it on early by setting MCP_SERVER=1 in the shop’s .env. Older 6.x shops do not have it.
• Endpoints. An Admin API endpoint at /api/_mcp, authenticated with the same integration credentials as the rest of the Admin API, and a Store API endpoint at /store-api/_mcp for sales-channel-facing tools.
• Permissions. Every MCP request is validated against Shopware’s ACL, and administrators choose which tools, resources and prompts an agent is allowed to see. This is the biggest improvement over the archived package.
• Dry runs. Write tools run as dry runs by default, so an agent previews the change before it commits.
• Extensibility. Plugins and Symfony bundles register their own tools in-process, with full access to the DAL and the service container. If your agency builds Shopware plugins, this is the part you will care about most.

It is a well-designed foundation. If you were about to build your own Shopware MCP server against the Admin API, stop. That job is done, and done properly.

What the native server is for

The native server is a platform primitive. It gives an AI client typed access to the entities and system config of one shop, under that shop’s permission model. That is exactly right for:

• Developers working on a shop from Claude Code, Cursor or a similar tool, who want the agent to read products, orders and config while they build.
• Plugin and app authors who want to expose their own domain as MCP tools, using Shopware’s registration rather than a separate service.
• Single-shop admin work where the questions stay inside Shopware and the client can hold integration credentials.

What it deliberately does not try to be is an operations layer. There is no approval queue, no record of who approved what, no schedule, and nothing outside the shop. Dry runs are a safety feature for a developer at a keyboard, not a workflow for an owner approving a refund from a phone.

What datavessel’s Shopware MCP server is for

datavessel is an e-commerce harness: a hosted MCP server plus everything an operator needs around the tools. For Shopware specifically, the catalog today is 39 typed tools, 25 reads and 14 writes, covering orders and the full order, delivery and payment state machines, products, low stock, sales summaries, promotions, reviews, customers, CMS and landing pages, and SEO URLs. Nothing is installed on the shop; the connection is Admin and Store API credentials you can revoke.

The differences that decide it:

• The rest of your stack is in the same conversation. The same connector carries GA4, Search Console, Google and Meta ads, Klaviyo, Google Merchant Center, Judge.me, Gorgias, Slack and WordPress: 300+ tools across 18 providers. “Why did revenue dip on Tuesday” is answered across store, analytics and ads in one pass. A shop-only server cannot see the ad account.
• Claude and ChatGPT over OAuth. You sign in through a browser flow in Claude or in ChatGPT’s connector settings. There is no public endpoint on your shop to secure and no integration secret pasted into a client. The step-by-step guides are here for Claude and here for ChatGPT.
• Approvals, not dry runs. Every write pauses on a card with the exact change and the agent’s reasoning, approved on web or mobile. Some actions never run unattended regardless of settings.
• A ledger. Every run, read, proposal and decision is timestamped, per shop and per client. That is what turns “the AI did something” into “here is what was done, by whom, and why”.
• Schedules and triggers. Agents run on a clock or on Shopware webhooks, so the weekly SEO audit and the low-stock sweep happen without anyone opening a chat.
• Versions and fleets. Works with Shopware 6 shops on 6.5 and later, cloud or self-hosted, including the many that have not reached 6.7.14. And an agency connects twenty client shops behind one connector with isolated data per client.

Side by side

Which one should you use?

Use the native server if you are a developer or agency engineer building on a 6.7.14+ shop, your client can hold integration credentials, and the work stays inside Shopware. It is free, first-party, and extensible in a way a hosted service never will be.

Use datavessel if the person asking the questions is the owner or an operator, the questions cross into analytics and ads, you want ChatGPT as well as Claude, you need approvals and a record, or you run more than one shop.

Use both if you are an agency: native MCP for the engineers building plugins and themes, datavessel for the account managers running operations across every client’s shop. They do not conflict. They talk to the same Admin API under different credentials.

Frequently asked questions

Does Shopware have an official MCP server?

Yes. Since 6.7.14 the MCP server is part of Shopware core, at /api/_mcp for the Admin API and /store-api/_mcp for the Store API. The earlier standalone shopware-admin-mcp package was archived in July 2026 and is no longer maintained.

Do I need to build my own Shopware MCP server?

No, not any more. On 6.7.14 or later, use the native one. On older 6.x shops, or if you need operations features, datavessel’s hosted server connects the shop to Claude or ChatGPT in a few minutes with no code.

Can I connect the native Shopware MCP server to ChatGPT?

The native server authenticates with integration credentials over your shop’s Admin API. ChatGPT’s custom connectors expect a remotely reachable MCP endpoint with a sign-in flow, so check Shopware’s documentation for your client before planning on it. datavessel connects to ChatGPT through its standard connector flow.

Is datavessel’s Shopware MCP server read-only?

No. 14 of the 39 Shopware tools are writes, covering order, delivery and payment state transitions, products, CMS and landing pages, and SEO URLs. Every write pauses for your approval.

Can I use both at the same time?

Yes. Each uses its own integration credentials against the same shop, and neither installs anything. Many agencies will run the native server for development and datavessel for operations.

Which Shopware versions does datavessel support?

Shopware 6 on 6.5 and later, both Shopware Cloud and self-hosted, through the Admin and Store APIs.

The bottom line

Shopware building MCP into the core is good news for everyone, including us: it settles the question of whether Shopware shops belong in AI clients. The native server is the right primitive for developers on 6.7.14+. datavessel’s Shopware MCP server is the operations layer for the people running the shop: every source in one conversation, every write behind an approval, every action in a ledger, on any Shopware 6 shop.

Connect your Shopware shop to Claude or ChatGPT with approvals and a ledger built in: the datavessel MCP server →