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의 세 기둥
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
- 사용자 의견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는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
직접 입력할 값
- 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
- 이 카테고리의 다른 서버 1754개 중 0%보다 스타가 많아요
- 이 카테고리의 다른 서버 1754개 중 88%보다 최근에 레지스트리에 공개됐어요
- 기본 점검 결과가 이 카테고리의 다른 서버 1754개 중 100%와 같거나 더 좋아요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
자주 묻는 질문
Shopware MCP, 안전한가요?
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
어떤 키나 코드가 필요한가요?
입력해야 할 값: SHOPWARE_URL, SHOPWARE_CLIENT_ID, SHOPWARE_CLIENT_SECRET
내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
아직 관리되고 있나요?
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.11.1)은 그저께 레지스트리에 올라왔어요.
어떤 앱에서 쓸 수 있나요?
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.
대신 쓸 수 있는 건 뭐가 있나요?
같은 카테고리에는: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
대안
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도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
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요