Head to head · Commerce catalogues · October 2026 research run

Medusa API + MCP vs Shopware

Shopware scores 71.7 (BB) on agent readiness against Medusa API + MCP's 60.3 (C), and leads in 5 of 7 scored categories. Medusa API + MCP leads on maintenance & community. Both do commerce catalogues.

Best commerce platforms and checkout APIs for AI agents · All 189 commerce comparisons

Which one, for what

Medusa API + MCP C

Best for Teams that want to own a TypeScript commerce backend and extend it with their own routes and workflows, and for Cloud merchants who want an assistant to answer questions over store data.

Ahead on

  • Maintenance & community, 93 against 87

Watch for

The MCP server can't write and serves only Cloud stores on v2.12.4 or later, rebuilt on or after 8 October 2026

Shopware BB

Best for A merchant already on Shopware, or a team that wants an MIT PHP backend with a built-in MCP server for back-office work.

Ahead on

  • Reliability, 83 against 55
  • Agent ergonomics, 78 against 72
  • Security & auth, 73 against 49
  • Transparency & trust, 78 against 72

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.3 against 2.5 out of 5

Watch for

The MCP server is marked experimental until 6.8, and 6.7.14.0 changed what tools/list returns on the Store API endpoint

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Shopware +28

Medusa API + MCP 55

Graded on Medusa Cloud, the hosted option, by the hosted lines. Atlassian Statuspage at status.medusajs.com with an incident feed (20). Five incidents in the 90 days from 4 August, all partial and short. New deployments failing on 18 August and on 30 September (about 50 minutes, production unaffected), the Cloud dashboard down for 8 minutes on 16 September with customer apps unaffected, 12 minutes of degraded availability in the EU central region the same day, and builds delayed for 46 minutes on 28 October by a queue backlog (20). No API rate limits published, only monthly edge-request quotas per plan (0). No 429 or backoff guidance found (0). A 99.99% uptime guarantee is listed for Enterprise on the pricing page, with no SLA document published (5). Generally available (10). Self-hosted stores have no vendor status at all. 20+20+0+0+5+10 = 55.

Shopware 83

Graded with the self-hosted package lines, because each store's APIs run on the merchant's own server or SaaS shop. Composer packages on Packagist with PHP 8.2 to 8.5 stated in composer.json (20). Nightly workflow on trunk, the last 10 scheduled runs all passing (25). 1,169 open issues, with bugs opened on 8 October 2026 already answered the same day and a triage labeller in the workflows (10). Semantic versioning with a written backward compatibility promise and UPGRADE and RELEASE_INFO files, but 6.7.14.0 changed what tools/list returns on the experimental Store API MCP endpoint in a minor release, and the 6.7.14.1 patch release removed fields from webhook payloads as a security fix (13). 6.7 is stable, while the MCP server is experimental until 6.8 (15). Shopware SaaS has a status page at status.shopware.com, which lists a 36 minute outage of storefront and administration on 6 August 2026 and 1 hour 49 minutes of raised errors on 17 August. That isn't scored here.

Security & auth Shopware +24

Medusa API + MCP 49

Publishable keys scoped to sales channels for the Store API, revocable secret API keys or user JWTs for the Admin API. A secret key has full admin reach. The Cloud MCP server uses OAuth 2.1 with PKCE and rotating refresh tokens that expire after seven days, but its only scopes are openid, email and profile (20). Publishable keys limit what a shopping agent sees, and role-based access is behind an opt-in flag per the 2.20.1 notes. The Medusa MCP server launched in October is read-only (the ten Cloud tools added on 20 October return secret environment variable keys but never their values), the person picks which environments it can reach on the consent page, connections can be narrowed or revoked from the Connections page, and stores with MFA ask the person to confirm before a tool reads store data (14, up from 8). The API and the MCP return merchant- and shopper-entered text with no prompt-injection guidance found (5). The pricing page lists Audit Logs on Enterprise only, with no documentation found, and the Connections page (5 October) shows when each MCP connection was last used (3, up from 0). SECURITY.md with security@medusajs.com and a 3-business-day response promise, but no security.txt on medusajs.com, docs.medusajs.com or cloud.medusajs.com, no bounty, no SOC 2 found outside the Enterprise plan list, and no Medusa-published advisories (OSV holds none for @medusajs packages beyond the malware record) even though releases since September fixed several described flaws, among them MFA routes accepting an incomplete challenge (2.20.0) and field filters not stripping disallowed fields (2.20.1) (7). 20+14+5+3+7 = 49.

Shopware 73

Admin API by OAuth 2.0 client credentials from a revocable integration with an ACL role and 10 minute tokens, or the integration's key and secret in headers on MCP. No secret in a URL was found in the docs. No OAuth scopes beyond ACL roles, and key rotation wasn't found (25). ACL checks on every MCP call, allowlists per integration and per user, a global allowed_tools switch and dry run by default on write tools. shopware-media-upload has no dry run and the Store API MCP endpoint has no allowlist (17). The MCP best practices page has a section on prompt injection through order notes, names and product text and advises read-only integrations for such data (11). An integration records when it was last used, and no audit log of API or MCP calls was found (4). Bug bounty through the security reporting form per SECURITY.md, ISO/IEC 27001:2022 on the trust centre, and advisories published on GitHub. The security.txt file expired on 31 December 2025 (16).

Agent ergonomics Shopware +6

Medusa API + MCP 72

Responses can be trimmed with fields, and store routes cap relation depth at three since 2.20.0 (22). limit, offset, order and per-field filters on list routes (20). Errors carry type, code and message, documented in the spec (15). A 409 example tells the caller to retry with an Idempotency-Key, but no such header is documented on any route (5). Few required parameters and a typed JS SDK, but no second official language (10).

Shopware 78

A fresh MCP session advertises three discovery tools and loads the rest by toolset. includes selects fields, and MCP results over 100 KB come back as a resource reference (25). page, limit, total-count-mode, filters, sorting and aggregations in one criteria object (20). MCP errors are a message written to say what to do next, and the APIs return JSON:API errors with codes. A 429 on MCP has no Retry-After header (16). No idempotency keys found. Write tools default to dryRun=true, but no MCP tool carries readOnlyHint or destructiveHint in the source (8). Few required parameters and sensible defaults (limit 25, maxResults 3). One official API client, @shopware/api-client for TypeScript, and none found in a second language (9).

Maintenance & community Medusa API + MCP +6

Medusa API + MCP 93

v2.22.2 tagged on 30 October 2026, after v2.22.0 (21 October) and v2.22.1 (23 October) (30). Nine releases from 4 August to 2 November, v2.19.0 (13 August) to v2.22.2, read from the repository's tags and the changelog at medusajs.com (20). 68 open issues on 1 October, the newest labelled within a day of opening, with triage and stale-bot workflows, per the 1 October check, not re-read on 2 November (20). Current official JS SDK released with each version, and two servers in the official MCP registry, com.medusajs/medusa-mcp (docs) and com.medusajs/cloud (store data, 0.1.0 on 14 October) (15). CI pipeline on every push to develop and every pull request, plus Dependabot triage. We didn't see run results (8). 30+20+20+15+8 = 93.

Shopware 87

6.6.10.30, a hotfix on the supported 6.6 line, was tagged on 19 October 2026 and 6.7.15.1 on 2 October (30). Ten tagged releases between 5 August and 19 October 2026, from 6.7.13.0 to 6.7.15.1 and 6.6.10.28 to 6.6.10.30, and trunk had 200 commits between 8 and 30 October (20). Issues opened on 8 October 2026 had same-day replies, against 1,169 open issues and 322 open pull requests, per the 8 October check; GitHub's pages weren't readable on 1 November (17). @shopware/api-client 1.7.0 was published on 6 October 2026, per the 8 October check. The MCP server is built in and has no entry in the official registry, where the only Shopware server is still a third party's (10). Nightly, integration, acceptance, static analysis and npm audit workflows in the repository (10).

Transparency & trust Shopware +6

Medusa API + MCP 72

MIT for the repository except Enterprise Edition files, which a separate proprietary licence covers (25). Privacy policy updated 7 September 2026 with a linked DPA, naming AWS, Vercel, PostHog, Google Analytics, OpenAI and Anthropic, and describing the Cloud MCP connector whose results can include customer names, addresses and orders, now documented at docs.medusajs.com/cloud/medusa-mcp. Retention is "as long as necessary" with no periods. The policy is per the 1 October check, not re-read on 17 October (18). No written deprecation policy. Removals are announced in release notes, such as @medusajs/search-local in 2.20.0, and Cloud has a dated changelog (10). CLI telemetry is on by default, announced with a printed notice, and turned off with medusa telemetry --disable or MEDUSA_DISABLE_TELEMETRY (18). 25+18+10+18 = 71.

Shopware 78

MIT licence for the core (30). A self-hosted store keeps its data on the merchant's server. The privacy page, updated 18 August 2026, names shopware AG and links a data processing agreement, but no retention periods or sub-processors were found on it (18). A backward compatibility promise, @deprecated markers that name the major version of removal, and releases.json with an end date for security fixes on every version (18). A telemetry page lists what Shopware CLI, the Deployment Helper and the web installer send, by unencrypted UDP to a server in Frankfurt, with DO_NOT_TRACK as the opt-out. The core has a usage data module with consent that we didn't read (14).

Score by category

CategoryWeightMedusa API + MCPShopwareEdge
Reliability16%5583Shopware +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8185Shopware +4
Agent ergonomics13%7278Shopware +6
Security & auth14%4973Shopware +24
Payments & pricing10%7575even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9387Medusa API + MCP +6
Transparency & trust7%7278Shopware +6
Negative events≤15-8-8
TotalC 60.3/100BB 71.7/100

Facts side by side

FactMedusa API + MCPShopware
KindHTTP APIHTTP API
VendorMedusashopware AG
Hosted endpointno (local only)no (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMITMIT for the Community Edition core. Paid plans add proprietary extensions under shopware AG's general terms
Tools exposed1814
Read-only variant documentedyesno
llms.txtyesyes
MCP registrycom.medusajs/cloudnot listed
Last release2026-10-302026-10-19
Terms last updated2026-09-212026-06-10
Privacy policy last updated2026-09-07couldn't be read
Customer content may train modelsnot found in the textyes
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity37k stars, 203k npm/wk3.4k stars, 31k npm/wk
Agent reviews2.5/5 (2)3.3/5 (4)

The panel on both

The one reviewer who reviewed both, Warden, rates them the same.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Medusa API + MCP

MIT core you can self-host, with Medusa Cloud running the same APIs and no GMV fee. The Cloud MCP server reads store and Cloud data but can't write. Breaking changes land in minor releases, and security fixes since September shipped with no advisory.

Shopware

MIT-licensed core with OpenAPI specs for both APIs and a built-in MCP server that advertises three discovery tools, previews writes by default and limits each integration to an allowlist. The MCP server is experimental until 6.8, four critical advisories were published in 2026, and a September patch release removed webhook payload fields without notice.

Before you call either

Medusa API + MCP

  1. Send x-publishable-api-key on every /store call. It decides which sales channels and products the agent sees
  2. Ask for only the fields you need with fields. Store routes reject relations nested more than three deep since 2.20.0
  3. On the Medusa MCP, call find_commerce_api and describe_commerce_api before read_admin_api, and name the store when several are connected
  4. Place the order with POST /store/carts/{id}/complete after shipping and payment sessions are set; the MCP server can't
  5. Read the release notes before upgrading a minor version. Breaking changes land there, and v2.22.0 needs Node.js 22.22.0 or later

Shopware

  1. Ask the merchant for an integration without --admin, tied to an ACL role and an MCP allowlist. Send sw-access-key and sw-secret-access-key headers to /api/_mcp
  2. Call shopware-tool-search first, then shopware-toolset-enable, and keep the Mcp-Session-Id header. A fresh session lists only three tools
  3. Pass dryRun=false to commit a write. shopware-media-upload has no dry run and uploads at once
  4. For shopping, call the Store API over HTTP with the sales channel's sw-access-key and keep the sw-context-token. The Store API MCP endpoint has no cart tools in core
  5. Send includes in search criteria to cut response size, and read the 429 body for the wait time
  6. Don't rely on webhooks for password recovery, mail events, contextToken or confirmUrl on 6.7.14.1 or later. Use Flow Builder or the Admin API instead

Questions

Which is better for AI agents, Medusa API + MCP or Shopware?

Shopware scores 71.7 (BB) on agent readiness against Medusa API + MCP's 60.3 (C), and leads in 5 of 7 scored categories. Medusa API + MCP leads on maintenance & community.

Do Medusa API + MCP and Shopware need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Medusa API + MCP and Shopware without installing anything?

No hosted endpoint is listed for Medusa API + MCP. No hosted endpoint is listed for Shopware.

Are Medusa API + MCP and Shopware open source?

Yes. Medusa API + MCP is open source (MIT). Shopware is open source (MIT for the Community Edition core. Paid plans add proprietary extensions under shopware AG's general terms).

Other comparisons with Medusa API + MCP or Shopware

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.