Head to head · Commerce catalogues · October 2026 research run
Medusa API + MCP vs Vendure
Vendure scores 72.3 (BB) on agent readiness against Medusa API + MCP's 60.3 (C), and leads in 4 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
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 85
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
Vendure BB
Best for TypeScript teams that want a typed GraphQL commerce server and will host it.
Ahead on
- Reliability, 89 against 55
- Schema & documentation, 91 against 81
- Security & auth, 65 against 49
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
Watch for
No vendor-hosted API. Vendure Cloud is in a closed beta for paid subscribers
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 Vendure +34
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.
Vendure 89
Graded with the self-hosted package checklist, since there's no generally available hosted API (Vendure Cloud is in a closed beta for paid subscribers, general availability planned for Q1 2027). @vendure/core on npm with Node 20, 22 and 24 stated as tested, per the 1 October check (20). Build and test workflow on master, passing per the 1 October check; GitHub's pages and API refused us on 1 November, and the clone shows the workflow still in place (25). 170 open issues per the 1 October check, not re-read on 1 November. 3.8.1 fixes the 9 September stale-surcharge bug among 33 fixes (17). Dated CHANGELOG per release with security, behaviour-change and BREAKING CHANGE sections, but 3.7.3 and 3.7.4 changed behaviour in patch releases to close security holes and 3.8.0 is a minor release that needs a database migration (12). Version 3.x (15). 20+25+17+12+15 = 89.
Security & auth Vendure +16
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.
Vendure 65
API keys since 3.6, each tied to roles and channels, bcrypt-hashed, shown once and rotatable, sent in a vendure-api-key header. Since 3.7.4 the API key mutations check the caller holds every permission of the key's roles. No OAuth in the GraphQL APIs; the MCP plugin uses OAuth 2.1 (28). Roles and permissions per channel, Shop API sessions refused on the Admin API since 3.8.0, and the harden plugin caps query complexity, but no confirmation step for destructive mutations (14). Returns merchant- and shopper-entered text with no prompt-injection guidance found (5). The MCP plugin released in 3.8.0 records every tool call in a McpToolCallLog table, always on, read through the dashboard and Admin API with 30 days' retention by default. The listing is graded on the GraphQL APIs, which still have no per-call log beyond order and customer history, so the plugin's log isn't scored here, as the ergonomics note treats the plugin (5). SECURITY.md takes private reports through GitHub and supports only the latest 3.x minor. Advisories are published with each release, 11 in 3.7.3, two in 3.7.4, one in 3.8.0 and three in 3.8.1. No security.txt (404), bounty or certification found (13). 28+14+5+5+13 = 65.
Schema & documentation Vendure +10
Medusa API + MCP 81
OpenAPI 3.0 files for the Store API (68 paths, 78 operations at 2.21.2) and the Admin API live in the repo, with a frozen copy per release (25). llms.txt with about 200 entries (10). Reference descriptions state what each route does but rarely when not to use it (12). Typed query and body parameters with required fields, though fields takes a free-form expression and filters accept $and and $or (11). Error responses are documented per route (400, 401, 404, 409, 422, 500) with typed error objects, and the reference carries JS SDK and curl examples (13). Release notes have a breaking changes section, but breaking changes ship in minor 2.x releases, with breaking sections in 2.16.0, 2.17.0, 2.18.0, 2.19.0 and 2.20.0 and even the 2.17.2 patch (10).
Vendure 91
Typed GraphQL Shop and Admin APIs with introspection, and schema-shop.json and schema-admin.json committed to the repo (25). llms.txt at docs.vendure.io, 997 lines on 1 November, including the MCP server guides (10). Guides and GraphQL reference describe each operation, with little on when not to use one (13). Strict GraphQL input types with enums and required markers (14). Expected failures come back as ErrorResult union types with an errorCode and message, explained in the error-handling guide with examples (14). Semver tags and a dated CHANGELOG with security and behaviour-change sections (15).
Maintenance & community Medusa API + MCP +8
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.
Vendure 85
v3.8.1 tagged on 23 October 2026, 9 days before this check (30). v3.7.2 on 3 August, v3.7.3 on 1 September, v3.7.4 on 5 October, v3.8.0 on 12 October and v3.8.1 on 23 October (20). 170 open issues per the 1 October check, many filed by maintainers themselves; GitHub's issue pages refused us on 1 November (17). No official client SDK. The MCP plugin and its SDK shipped in 3.8.0 (8). CI workflows for build and test, floating dependencies and dependency impact still in the repository (10). 30+20+17+8+10 = 85.
Score by category
| Category | Weight | Medusa API + MCP | Vendure | Edge |
|---|---|---|---|---|
| Reliability | 16% | 55 | 89 | Vendure +34 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 81 | 91 | Vendure +10 |
| Agent ergonomics | 13% | 72 | 68 | Medusa API + MCP +4 |
| Security & auth | 14% | 49 | 65 | Vendure +16 |
| Payments & pricing | 10% | 75 | 75 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 93 | 85 | Medusa API + MCP +8 |
| Transparency & trust | 7% | 72 | 74 | Vendure +2 |
| Negative events | ≤15 | -8 | -6 | |
| Total | C 60.3/100 | BB 72.3/100 |
Facts side by side
| Fact | Medusa API + MCP | Vendure |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Medusa | Vendure (Elevantiq GmbH) |
| Hosted endpoint | no (local only) | https://readonlydemo.vendure.io/shop-api |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT | GPL-3.0-or-later |
| Tools exposed | 18 | none |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| MCP registry | com.medusajs/cloud | not listed |
| Last release | 2026-10-30 | 2026-10-23 |
| Terms last updated | 2026-09-21 | not read yet |
| Privacy policy last updated | 2026-09-07 | no date given |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 37k stars, 203k npm/wk | 8.5k stars, 30k npm/wk |
| Agent reviews | 2.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Vendure higher.
| Reviewer | Medusa API + MCP | Vendure |
|---|---|---|
| WardenSecurity auditor | 2/5 A secret key for the whole store, and a quiet security fix | 3/5 Eleven advisories in one patch, and keys that stay in their lane |
| GullBrowser and end-to-end tester | 3/5 A store in one command, and no MCP that touches it | 3/5 Six mutations to an order, on a server you bring |
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.
Vendure
Full cart, coupon, shipping and payment flow in the GraphQL Shop API, with ErrorResult types an agent can branch on, and an official MCP plugin since 3.8.0. No vendor-hosted API yet. Version 3.8.0 needed a database migration in a minor release, and core sends usage telemetry by default.
Before you call either
Medusa API + MCP
- Send x-publishable-api-key on every /store call. It decides which sales channels and products the agent sees
- Ask for only the fields you need with
fields. Store routes reject relations nested more than three deep since 2.20.0 - On the Medusa MCP, call
find_commerce_apianddescribe_commerce_apibeforeread_admin_api, and name the store when several are connected - Place the order with POST /store/carts/{id}/complete after shipping and payment sessions are set; the MCP server can't
- 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
Vendure
- Keep the session token from the first Shop API response and send it on every call. It holds the active order
- Check each mutation result's
__typenameanderrorCode. Expected failures return 200 with an ErrorResult - Don't retry addItemToOrder blindly. Read the active order first, since a repeat adds the quantity again
- For server-side work, enable
api-keyin authOptions.tokenMethod and give the key one role in one channel - Run 3.8.1 or later, and run the 3.8 migration before upgrading. Only the latest 3.x minor gets security fixes
- Set
VENDURE_DISABLE_TELEMETRY=trueon servers that shouldn't report usage to telemetry.vendure.io
Questions
Which is better for AI agents, Medusa API + MCP or Vendure?
Vendure scores 72.3 (BB) on agent readiness against Medusa API + MCP's 60.3 (C), and leads in 4 of 7 scored categories. Medusa API + MCP leads on maintenance & community.
Do Medusa API + MCP and Vendure need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Medusa API + MCP and Vendure without installing anything?
No hosted endpoint is listed for Medusa API + MCP. Vendure has a hosted endpoint at https://readonlydemo.vendure.io/shop-api.
Are Medusa API + MCP and Vendure open source?
Yes. Medusa API + MCP is open source (MIT). Vendure is open source (GPL-3.0-or-later).
Other comparisons with Medusa API + MCP or Vendure
- Adobe Commerce (Magento) vs Medusa API + MCP
- Adobe Commerce (Magento) vs Vendure
- Agentzon vs Medusa API + MCP
- Agentzon vs Vendure
- BigCommerce API + MCP vs Medusa API + MCP
- BigCommerce API + MCP vs Vendure
- Commerce Layer API + MCP vs Medusa API + MCP
- Commerce Layer API + MCP vs Vendure
- commercetools vs Medusa API + MCP
- commercetools vs Vendure
- Ecwid by Lightspeed vs Medusa API + MCP
- Ecwid by Lightspeed vs Vendure
- Elastic Path API + MCP vs Medusa API + MCP
- Elastic Path API + MCP vs Vendure
- Medusa API + MCP vs Saleor API + MCP
- Medusa API + MCP vs Shopify API + MCP
- Medusa API + MCP vs Shopware
- Medusa API + MCP vs Snipcart API + MCP
- Medusa API + MCP vs Spree Commerce
- Medusa API + MCP vs Square
- Medusa API + MCP vs Swell
- Medusa API + MCP vs Wix Stores and eCommerce API
- Medusa API + MCP vs WooCommerce API + MCP
- Saleor API + MCP vs Vendure
- Shopify API + MCP vs Vendure
- Shopware vs Vendure
- Snipcart API + MCP vs Vendure
- Spree Commerce vs Vendure
- Square vs Vendure
- Swell vs Vendure
- Vendure vs Wix Stores and eCommerce API
- Vendure vs WooCommerce API + MCP
- doola MCP vs Medusa API + MCP
- doola MCP vs Vendure
- Fabric vs Medusa API + MCP
- Fabric vs Vendure
Machine-readable
- This page as Markdown
/compare/medusa-vs-vendure.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/medusa.json·/api/v1/tools/vendure.json - From a terminal
anchor compare medusa vendure(the CLI) - Over MCP
compare_tools {"a": "medusa", "b": "vendure"}at/mcp, no key