Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
クラウドで動く★ 15,812BSD-3-Clause8 日前更新
インストール
Shopware MCP
概要
作者による説明（英語の原文）
Query and safely manage a Shopware 6 shop: products, orders, customers, stock, audits, reports.
PopNx MCPの3つの柱
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
- 利用者の声iレビューはまだありませんレビューは今後のステップで、アカウント機能と一緒に始まります
- 私たちの基本チェックi1項目中1項目に合格公開情報からチェック。コードはまだスキャンしていません
- 利用状況i未計測★ –
できること
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
- 接続方法: パソコンで動く
- トランスポート: stdio
- カテゴリ: ネットショップ・決済
- 入力が必要なもの：SHOPWARE_URL, SHOPWARE_CLIENT_ID, SHOPWARE_CLIENT_SECRET
インストール
使っているAIアプリを選んで、設定をコピーしてください。
インストールの前に
- 基本チェック：1項目中1項目に合格
- あなたのパソコンで、あなたのユーザーと同じ権限（ファイル、ネットワーク、アプリ）で動きます。
- 自分で入力するもの：
SHOPWARE_URL,SHOPWARE_CLIENT_ID,SHOPWARE_CLIENT_SECRET,SHOPWARE_MCP_ALLOW_WRITE
「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
- npmNode.jsのインストール（npxコマンドに必要）
どのアプリを使っていますか？
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"shopware": {
"command": "npx",
"args": [
"-y",
"shopware-mcp"
],
"env": {
"SHOPWARE_URL": "your-value",
"SHOPWARE_CLIENT_ID": "your-value",
"SHOPWARE_CLIENT_SECRET": "your-value",
"SHOPWARE_MCP_ALLOW_WRITE": "your-value"
}
}
}
}ターミナルでこれを実行します
claude mcp add shopware --env SHOPWARE_URL=your-value --env SHOPWARE_CLIENT_ID=your-value --env SHOPWARE_CLIENT_SECRET=your-value --env SHOPWARE_MCP_ALLOW_WRITE=your-value -- npx -y shopware-mcp動かす前に、空欄の値を入力してください。
または、設定を自分でコピーする
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"shopware": {
"command": "npx",
"args": [
"-y",
"shopware-mcp"
],
"env": {
"SHOPWARE_URL": "your-value",
"SHOPWARE_CLIENT_ID": "your-value",
"SHOPWARE_CLIENT_SECRET": "your-value",
"SHOPWARE_MCP_ALLOW_WRITE": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
または、設定を自分でコピーする
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"shopware": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"shopware-mcp"
],
"env": {
"SHOPWARE_URL": "your-value",
"SHOPWARE_CLIENT_ID": "your-value",
"SHOPWARE_CLIENT_SECRET": "your-value",
"SHOPWARE_MCP_ALLOW_WRITE": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
自分で入力する値
- Shop base URL, e.g. https://shop.example.com
- Integration access key ID
- Integration secret access key
SHOPWARE_MCP_ALLOW_WRITEenvSet to true to register the guarded write tools
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
できること
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
基本チェックi
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック
- ✓ 合格
作者とリポジトリが一致
レジストリ名は、リポジトリを所有するGitHubアカウント bnymnDev で確認済みです
- … 未チェック
今もメンテナンスされている
このリポジトリはまだGitHubから読み取っていません
- … 未チェック
ライセンスがある
このリポジトリはまだGitHubから読み取っていません
- – 対象外
エンドポイントが応答する
これはパソコンで動くため、インターネット上のエンドポイントはありません
- – 対象外
OAuthでサインイン
パソコンで動き、代わりにローカルの設定を使います
- … 未チェック
ツールの説明に隠れた指示がない
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
ネットショップ・決済のほかのサーバーとの比較i
- このカテゴリのほかの1755件のうち0%よりスターが多い
- このカテゴリのほかの1755件のうち88%より最近レジストリに公開
- 基本チェックの結果が、このカテゴリのほかの1755件のうち100%と同じかそれ以上
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
よくある質問
Shopware MCPは安全ですか？
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
どんなキーやコードが必要ですか？
入力が必要なもの：SHOPWARE_URL, SHOPWARE_CLIENT_ID, SHOPWARE_CLIENT_SECRET
パソコンで動きますか、それともクラウドですか？
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません（サーバー自体がオンラインサービスを呼び出す場合を除きます）。
今もメンテナンスされていますか？
GitHubリポジトリの最終更新は–、最新バージョン（0.11.1）がレジストリに届いたのは3 日前です。
どのアプリで使えますか？
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。
代わりに使えるものは？
同じカテゴリには：Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
代わりの候補
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方：★ GitHubスターi3つの柱：レビュー · チェック · 利用状況i更新＝最新バージョンをレジストリに公開した日i
Stripe MCP
作者：stripe
MCP server integrating with Stripe - tools for customers, products, payments, and more.
クラウドで動く★ 2,043MIT12 か月前更新
インストール
MCP Cn Commerce
作者：TonyWang-hub
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
パソコンで動く★ 96MIT28 日前更新
インストール
作者のREADME
READMEを開く
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
Why · Demo · Install · Tools · Safety · Docs · Website · Deutsch
Introducing shopware-mcp
A Shopware 6 shop is about two hundred entities behind one Admin API. Ask an assistant "is everything okay with the shop?" and the honest answer takes seven searches with Criteria filters, three state machines by their technical names, a couple of aggregations, and an OAuth token it must never repeat back to you. Wire a model straight to that API and it gets all of it, including the right to PATCH a price because a prompt said so.
The Model Context Protocol turned "give the model real tools" into a one-line config change. It says nothing about what a good tool for a *shop* looks like: which of the two hundred entities matter on a Tuesday morning, what "stuck order" means, or that a stock correction should be shown before it is sent.
shopware-mcp is that layer. One small server that speaks MCP to the host and the Admin API to the shop, and knows Shopware well enough to answer in one call what used to take an afternoon in the admin. It also notices when orders stop coming, and tries the checkout the way a customer would to find out why:
| Curated tools | Products, orders and their history, documents, customers, categories, promotions, reviews, payment and shipping methods, plugins, stock, sales channels, scheduled tasks, the shop's trading settings: twenty tools that return compact JSON with exact totals, descriptions written for a model, and Shopware's own Criteria filters. No invented query language. |
| The customer's view | checkout_simulate puts products and codes into a throwaway cart through Shopware's own Store API, as a guest shipping anywhere or as a given customer with their group, prices and rules, and explains every cart error in plain words: a country the channel does not ship to, a code that expired, a payment method hidden by a rule, a parent product that needs a variant, a customer who cannot log in there. storefront_search searches like a customer and says why a product does not show up. Nothing is ordered; the cart is deleted. |
| A pulse | shop_pulse puts today next to the same hours of the same weekday in recent weeks and weighs the current quiet spell: how many orders those hours usually bring and how likely it is to see none by chance. "No order for six hours, when three to seven always came" is a broken checkout, not a slow Sunday. On a campaign day it compares with the same weekday last year, or with what the day should bring. |
| Ready for the campaign | promotions_check looks at every promotion that runs or starts before a date, switched on or not, and names what would stop it: inactive at its start, no discount, no channel or only channels in maintenance, no code left, the redemption limit, 60 % that was meant to be 6 %, two automatic discounts that add up. The campaign_ready prompt adds the checkout, stock and the plan for the day. |
| A watch that says why | shopware-mcp watch looks at orders and payments every few minutes and writes to Slack only when something changes: orders stop, payments fail, the shop stops answering, and when it is back to normal. The alarm comes with the likely cause: shop_diagnose looks at the usual suspects in one go (a storefront in maintenance, a test purchase of the best seller, an extension updated an hour ago, errors in Shopware's log, a stopped worker). Public holidays in the compared weeks are left out of "usual". On Black Friday: --baseline last-year --expect 3. |
| Synthetic customers | journeys_run walks fixed buying paths through the real cart, "Swiss guest with code SUMMER26", "regular customer pays by invoice", and names the one that broke and why. watch --journeys journeys.json runs them on every look, so a payment method that vanished after a plugin update raises the alarm before the first customer gives up. |
| Ready for AI shoppers | agent_readiness builds the product feed that AI shopping agents read (the Agentic Commerce feed of OpenAI and Stripe, field for field like Google Merchant) and says what keeps products out: no brand, no image, a GTIN with a wrong check digit, no weight, a storefront without HTTPS or without the privacy, terms and revocation pages an agent checkout links to. shopware-mcp feed --out feed.jsonl writes the whole feed. |
| Before the next update | update_check asks Shopware's own update service what comes next, which security issues it fixes, and for every extension whether it works with it: compatible, update the extension first, a compatible version announced, or not compatible. For 6.8 and every major after it. |
| Pages in the chat | In hosts that show MCP Apps (Claude, ChatGPT, VS Code), shop_brief, shop_pulse, shop_audit and sales_report come with an interactive page next to the answer: tiles, charts and findings, in the host's light or dark theme. The model still gets compact JSON. |
| Hosted, nothing to install | shopware-mcp hosted serves many shops from one address: an assistant adds the URL as a connector, the person connects their shop with an Integration's keys through OAuth, and that is it. Read-only, keys sealed with AES-256-GCM, tokens stored only as hashes. Try it at https://p-h07rka.project.space/mcp. |
| What a discount costs | promotion_impact replays a discount, or an existing promotion, on the real orders of the last weeks: what it would have cost on every eligible order and at the shop's usual code uptake, and how often a cap kicks in. margin_check finds products sold below their purchase price, thin margins, and what the running automatic discount leaves of them. |
| An audit | shop_audit runs eighteen checks in one call, plus ready-made rule packs for the GPSR, the accessibility act and shopping feeds, and the shop's own rules from a JSON file of Shopware filters, no code needed: a checkout that went unusually silent, promotions in the next two weeks that will not work, paid orders that never shipped or never got an invoice, unpaid orders going stale, shipped orders never completed, products out of stock, running out at the current sales pace, without a cover, without a delivery time or invisible in every sales channel, promotions past their end date, channels in maintenance, storefronts missing a legal page, reviews waiting for moderation, scheduled tasks that stopped running, extensions with updates waiting, and which EU duties look covered, including whether Shopware itself is set up for ZUGFeRD e-invoices. Prioritised, with samples and a hint per finding. The same audit runs as shopware-mcp audit from cron or CI, no MCP host needed. |
| Reports and a forecast | sales_report asks Shopware to aggregate: gross, net, average order, revenue per currency and channel, orders per state, a day/week/month timeline, the top products and, on request, the change against the period before. customer_report does the same for people: new accounts, guest share, repeat share, top customers by revenue. stock_forecast turns sales velocity and stock into days of cover, run-out dates and reorder quantities. returns_report says how many orders came back and which products come back most, from Shopware's own delivery states. The figures were checked against SQL on the same database. |
| An escape hatch | entity_schema describes any of the 200+ entities, a plugin's custom entities included, and entity_search queries them with the same filters and lets Shopware aggregate over the match: orders per payment method, revenue per month, anything a terms, sum or histogram can say. Entities that hold credentials are refused, secrets in the rest are scrubbed. |
| A brake | Read-only unless you start it with --allow-write. Even then every write is a dry run that shows the exact request first, and a write budget can cap how many real writes a process may make. Ship, mark paid, remind, refund, correct stock, note, generate a document, create a product or a promotion, give a product a picture, moderate a review, update a customer, invoice fifty orders in one go, tag a record: fifteen narrow writes, nothing else. Secrets never appear in output, logs or errors. |
Shops are not identical, so the tool list is not either: at startup the server looks up which extensions are installed and registers extra tools for the ones it knows. A plain shop gets the core set. A shop with more plugins gets a bigger agent, without configuration.
See it work
Six hours without an order, and why. Sunday evening. The pulse compares the silence with the same hours of the last eight Sundays, which always brought three to seven orders, and puts the odds of chance at about one in 170. The agent then tries to buy something the way a customer would and finds the storefront in maintenance mode. Nothing was ordered, nothing changed.
The checkout as a customer sees it. A customer in Switzerland says a code does not work. A throwaway cart through Shopware's own Store API explains both problems at once: Switzerland is not a country of that channel, and the code's promotion ended in August. Then the search explains why a product never shows up.
Every morning, one page. shopware-mcp brief --html brief.html writes the pulse, the audit and the last seven days as one self-contained page that loads nothing from anywhere and follows the reader's dark mode. From cron, with --slack for a one-paragraph summary in a channel. [Ope
冒頭だけを表示しています。続きはリポジトリで読めます