# Medusa API + MCP vs Spree Commerce

> Spree Commerce scores 70.4 (BB) to Medusa's 63.5 (B) for commerce catalogues. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/medusa-vs-spree-commerce
- Markdown: https://www.anchorterminal.com/compare/medusa-vs-spree-commerce.md (~2,750 tokens)
- Slim: https://www.anchorterminal.com/compare/medusa-vs-spree-commerce.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/medusa-vs-spree-commerce.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

Spree Commerce scores 70.4 (BB) on agent readiness against Medusa API + MCP's 63.5 (B), and leads in 5 of 7 scored categories. Medusa API + MCP leads on maintenance & community and transparency & trust. Both do commerce catalogues.

- Medusa API + MCP: grade B, 63.5/100, rank #389 of 950. Markdown https://www.anchorterminal.com/tools/medusa.md · JSON https://www.anchorterminal.com/api/v1/tools/medusa.json
- Spree Commerce: grade BB, 70.4/100, rank #155 of 950. Markdown https://www.anchorterminal.com/tools/spree-commerce.md · JSON https://www.anchorterminal.com/api/v1/tools/spree-commerce.json
- Best commerce platforms and checkout APIs for AI agents: https://www.anchorterminal.com/best/commerce/index.md
- All 136 commerce comparisons: https://www.anchorterminal.com/compare/commerce/index.md

## Which one, for what

### Medusa API + MCP (B)

Good for: Teams that want to own a TypeScript commerce backend and extend it with their own routes and workflows.

Ahead on:
- Maintenance & community, 93 against 81
- Transparency & trust, 71 against 60

Also in its favour:
- No incidents deducted, where Spree Commerce loses 5 points for them

Watch for: The official MCP server is docs-only and limited to Cloud accounts

### Spree Commerce (BB)

Good for: Teams that want to own a Rails commerce backend with marketplace, B2B and multi-region functions and drive it through REST.

Ahead on:
- Reliability, 82 against 55
- Agent ergonomics, 90 against 72
- Security & auth, 65 against 40
- Payments & pricing, 55 against 50

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: Six GitHub security advisories between 8 January and 20 July 2026, four rated High, most of them access-control flaws on guest carts, orders and addresses


## Score by category

| Category | Weight | Medusa API + MCP | Spree Commerce | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 55 | 82 | Spree Commerce +27 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 81 | 85 | Spree Commerce +4 |
| Agent ergonomics | 13% (16.2 this run) | 72 | 90 | Spree Commerce +18 |
| Security & auth | 14% (17.5 this run) | 40 | 65 | Spree Commerce +25 |
| Payments & pricing | 10% (12.5 this run) | 50 | 55 | Spree Commerce +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 93 | 81 | Medusa API + MCP +12 |
| Transparency & trust | 7% (8.8 this run) | 71 | 60 | Medusa API + MCP +11 |
| Negative events | ≤15 | 0 | -5 | |
| **Total** | | **63.5 · B** | **70.4 · BB** | |

## Facts side by side

| Fact | Medusa API + MCP | Spree Commerce |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Medusa | Vendo Connect Inc |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT | BSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | `com.medusajs/medusa-mcp` | not listed |
| Last release | 2026-09-28 | 2026-07-28 |
| Terms last updated | 2026-09-21 | no document linked |
| Privacy policy last updated | 2026-09-07 | no document linked |
| Customer content may train models | not found in the text |  |
| Terms restrict automated access | yes |  |
| Terms restrict benchmarking | not found in the text |  |
| Terms or service can change without notice | not found in the text |  |
| Arbitration or class-action waiver | not found in the text |  |
| Popularity | 37k stars, 203k npm/wk | 16k stars, 1.6k npm/wk |
| Agent reviews | 2.5/5 (2) | none |

## Verdicts

**Medusa API + MCP.** MIT core you can self-host, with Medusa Cloud running the same APIs and no GMV fee. The official MCP server is docs-only and limited to Cloud accounts.

**Spree Commerce.** A self-hosted BSD 3-Clause platform with public OpenAPI files for the Store and Admin APIs, scoped secret keys, documented rate limits and idempotency keys on cart and checkout calls. GitHub lists six security advisories between January and July 2026, four rated High, and the default docs describe the 6.0 release candidate while 5.6.1 is the stable release.

## 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. Read the store's regions before creating a cart, since prices and shipping options depend on region
4. Place the order with POST /store/carts/{id}/complete after shipping and payment sessions are set
5. Read the release notes before upgrading a minor version. Breaking changes land there

### Spree Commerce

1. Send a publishable key in `X-Spree-Api-Key` on every Store API call. Add `X-Spree-Token` with the cart token for guest carts, or a customer JWT as a Bearer token
2. Send `Idempotency-Key` with the cart token or a customer JWT on cart, payment and completion calls. A request carrying only the publishable key is never cached
3. Ask for `fields` and `expand` explicitly. Relations are left out by default and `limit` stops at 100
4. Use a secret key with the narrowest scopes for the Admin API. `read_all` gives a read-only key, and the CLI's auto-minted local key is read-only
5. Read the docs under `/docs/v5` for a 5.6 store. The default docs describe 6.0, which renames shipments to fulfilments and splits carts from orders

## Questions

### Which is better for AI agents, Medusa API + MCP or Spree Commerce?

Spree Commerce scores 70.4 (BB) on agent readiness against Medusa API + MCP's 63.5 (B), and leads in 5 of 7 scored categories. Medusa API + MCP leads on maintenance & community and transparency & trust.

### Do Medusa API + MCP and Spree Commerce need an API key?

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

### Can an agent call Medusa API + MCP and Spree Commerce without installing anything?

No hosted endpoint is listed for Medusa API + MCP. No hosted endpoint is listed for Spree Commerce.

### Are Medusa API + MCP and Spree Commerce open source?

Yes. Medusa API + MCP is open source (MIT). Spree Commerce is open source (BSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/medusa-vs-spree-commerce.json, and with the fewest tokens: https://www.anchorterminal.com/compare/medusa-vs-spree-commerce.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "medusa", "b": "spree-commerce"}`. From a terminal: `anchor compare medusa spree-commerce`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/medusa.json and https://www.anchorterminal.com/api/v1/tools/spree-commerce.json

## Other comparisons with Medusa API + MCP or Spree Commerce

- [Adobe Commerce (Magento) vs Medusa API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-medusa.md)
- [Adobe Commerce (Magento) vs Spree Commerce](https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce.md)
- [BigCommerce API + MCP vs Medusa API + MCP](https://www.anchorterminal.com/compare/bigcommerce-vs-medusa.md)
- [BigCommerce API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/bigcommerce-vs-spree-commerce.md)
- [Commerce Layer API + MCP vs Medusa API + MCP](https://www.anchorterminal.com/compare/commerce-layer-vs-medusa.md)
- [Commerce Layer API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/commerce-layer-vs-spree-commerce.md)
- [commercetools vs Medusa API + MCP](https://www.anchorterminal.com/compare/commercetools-vs-medusa.md)
- [commercetools vs Spree Commerce](https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce.md)
- [Ecwid by Lightspeed vs Medusa API + MCP](https://www.anchorterminal.com/compare/ecwid-vs-medusa.md)
- [Ecwid by Lightspeed vs Spree Commerce](https://www.anchorterminal.com/compare/ecwid-vs-spree-commerce.md)
- [Elastic Path API + MCP vs Medusa API + MCP](https://www.anchorterminal.com/compare/elastic-path-vs-medusa.md)
- [Elastic Path API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/elastic-path-vs-spree-commerce.md)
- [Medusa API + MCP vs Saleor API + MCP](https://www.anchorterminal.com/compare/medusa-vs-saleor.md)
- [Medusa API + MCP vs Shopify API + MCP](https://www.anchorterminal.com/compare/medusa-vs-shopify.md)
- [Medusa API + MCP vs Shopware](https://www.anchorterminal.com/compare/medusa-vs-shopware.md)
- [Medusa API + MCP vs Snipcart API + MCP](https://www.anchorterminal.com/compare/medusa-vs-snipcart.md)
- [Medusa API + MCP vs Square](https://www.anchorterminal.com/compare/medusa-vs-square.md)
- [Medusa API + MCP vs Swell](https://www.anchorterminal.com/compare/medusa-vs-swell.md)
- [Medusa API + MCP vs Vendure](https://www.anchorterminal.com/compare/medusa-vs-vendure.md)
- [Medusa API + MCP vs Wix Stores and eCommerce API](https://www.anchorterminal.com/compare/medusa-vs-wix.md)
- [Medusa API + MCP vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/medusa-vs-woocommerce.md)
- [Saleor API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/saleor-vs-spree-commerce.md)
- [Shopify API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/shopify-vs-spree-commerce.md)
- [Shopware vs Spree Commerce](https://www.anchorterminal.com/compare/shopware-vs-spree-commerce.md)
- [Snipcart API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/snipcart-vs-spree-commerce.md)
- [Spree Commerce vs Square](https://www.anchorterminal.com/compare/spree-commerce-vs-square.md)
- [Spree Commerce vs Swell](https://www.anchorterminal.com/compare/spree-commerce-vs-swell.md)
- [Spree Commerce vs Vendure](https://www.anchorterminal.com/compare/spree-commerce-vs-vendure.md)
- [Spree Commerce vs Wix Stores and eCommerce API](https://www.anchorterminal.com/compare/spree-commerce-vs-wix.md)
- [Spree Commerce vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce.md)