{ "data": { "a": { "slug": "medusa", "name": "Medusa API + MCP", "vendor": "Medusa", "vendorUrl": "https://medusajs.com", "kind": "http-api", "category": "commerce", "summary": "Open-source headless commerce backend in TypeScript, self-hosted or run on Medusa Cloud.", "url": "https://www.anchorterminal.com/tools/medusa", "markdownUrl": "https://www.anchorterminal.com/tools/medusa.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/medusa.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/medusa.json", "repo": "https://github.com/medusajs/medusa", "license": "MIT", "transports": [ "http", "streamable-http" ], "packages": [ { "registry": "npm", "name": "@medusajs/js-sdk" }, { "registry": "npm", "name": "@medusajs/medusa" } ], "auth": "mixed", "authNotes": "Store API calls need a publishable API key in the x-publishable-api-key header, and customer routes add a customer JWT or session. Admin API calls take a user JWT, a session cookie or a secret API key. The docs MCP at https://docs.medusajs.com/mcp takes Medusa Cloud OAuth or a Cloud personal access key as a Bearer token.", "pricing": "freemium", "pricingNotes": "Self-hosting the MIT core is free. Medusa Cloud Develop from $29 a month, Launch from $99, Scale from $299, Enterprise custom, with no GMV fee on any plan. Plans include 1M, 5M or 10M edge requests a month, then $0.30 per 1M. Search includes 10,000 requests a month, then $20 per 100,000 (https://medusajs.com/pricing/).", "priceSummary": "$29 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402. Payments go through payment provider modules such as Stripe.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 36514, "npmWeekly": 202809, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.medusajs.com", "llmsTxt": "https://docs.medusajs.com/llms.txt", "openapi": "https://raw.githubusercontent.com/medusajs/medusa/develop/www/apps/api-reference/specs/store/openapi.full.yaml", "registryName": "com.medusajs/medusa-mcp", "capabilities": [ "commerce.products", "commerce.cart", "commerce.checkout", "commerce.orders", "commerce.headless" ], "tags": [ "open-source", "self-hosted", "local", "hosted", "mcp", "llms-txt", "typescript", "webhooks", "freemium" ], "lastRelease": "2026-09-28", "graded": true, "anchor": { "graded": true, "score": 63.5, "grade": "B", "agentReady": false, "rank": 389, "ranked": true, "rankOf": 950, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 93, "payments": 50, "reliability": 55, "schema": 81, "security": 40, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "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.", "bestFor": "Teams that want to own a TypeScript commerce backend and extend it with their own routes and workflows.", "strengths": [ "MIT core you can self-host, with Medusa Cloud running the same APIs and no GMV fee", "Public OpenAPI 3.0 files for the Store and Admin APIs, frozen per release", "Field selection, pagination and documented error types on every list route", "Seven releases between 23 July and 28 September 2026, and 68 open issues triaged within a day" ], "weaknesses": [ "The official MCP server is docs-only and limited to Cloud accounts", "Breaking changes ship in minor releases, listed in 2.16.0, 2.17.0, 2.18.0, 2.19.0 and 2.20.0", "No rate limits, retry guidance or documented idempotency header", "No public security advisories, security.txt or audit log", "Some files sit under a proprietary Enterprise Edition licence" ], "agentNotes": [ "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", "Read the store's regions before creating a cart, since prices and shipping options depend on region", "Place the order with POST /store/carts/{id}/complete after shipping and payment sessions are set", "Read the release notes before upgrading a minor version. Breaking changes land there" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.5 } ], "editorialScores": { "ergonomics": 72, "maintenance": 93, "payments": 50, "reliability": 55, "schema": 81, "security": 40, "transparency": 71 }, "provenanceScore": 71 }, "connect": { "http": "curl \"$MEDUSA_BACKEND_URL/store/products?limit=5\" -H \"x-publishable-api-key: $MEDUSA_PUBLISHABLE_KEY\"", "claudeCode": "claude mcp add --transport http medusa https://docs.medusajs.com/mcp", "config": { "mcpServers": { "medusa": { "type": "streamable-http", "url": "https://docs.medusajs.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/commerce.products", "tool": "https://letme.dev/medusa" }, "area": "business", "unitPrices": [ { "item": "Cloud Develop", "unit": "month", "usd": 29, "note": "from, 1M edge requests a month" }, { "item": "Cloud Launch", "unit": "month", "usd": 99, "note": "from, 5M edge requests, webhook events, backups" }, { "item": "Cloud Scale", "unit": "month", "usd": 299, "note": "from, 10M edge requests, background workers" }, { "item": "Cloud GMV fee", "unit": "pct", "usd": 0, "note": "on every plan" }, { "item": "Self-hosted", "unit": "month", "usd": 0, "note": "MIT core, you pay for your own servers" } ], "provenance": { "legalEntity": "MedusaJS, Inc.", "domain": "medusajs.com", "domainRegistered": "2011-04-06", "domainNote": "medusajs.com was registered in 2011, years before the Medusa project started.", "endpointOnVendorDomain": false, "terms": "https://medusajs.com/terms-of-service/", "privacy": "https://medusajs.com/privacy-policy/", "statusPage": "https://status.medusajs.com", "changelog": "https://medusajs.com/changelog/", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The API runs on your own server or your Medusa Cloud project URL" ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/medusa.json", "live": { "slug": "medusa", "vendorStatus": { "page": "https://status.medusajs.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T03:58:27.945614692Z" }, "versions": [ { "registry": "github", "name": "medusajs/medusa", "version": "v2.21.2", "released": "2026-09-28", "seenAt": "2026-10-09T17:04:32.721112374Z" }, { "registry": "mcp-registry", "name": "com.medusajs/medusa-mcp", "version": "1.0.0", "seenAt": "2026-10-10T03:11:32.438759038Z" }, { "registry": "npm", "name": "@medusajs/js-sdk", "version": "2.21.2", "seenAt": "2026-10-09T17:04:30.449422328Z" }, { "registry": "npm", "name": "@medusajs/medusa", "version": "2.21.2", "seenAt": "2026-10-09T17:04:31.341202642Z" } ], "githubStars": 36670, "npmWeekly": 236753, "securityTxt": { "url": "https://medusajs.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:39:44.846918877Z" }, "llmsTxt": { "url": "https://docs.medusajs.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:17.031201387Z" }, "domain": { "domain": "medusajs.com", "registered": "2011-04-06", "source": "https://rdap.verisign.com/com/v1/domain/medusajs.com", "checkedAt": "2026-10-04T13:05:58.741633559Z" }, "pages": [ { "url": "https://medusajs.com/changelog/", "kind": "changelog", "status": 304, "checkedAt": "2026-10-09T18:41:52.368484596Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c94e48b9121e" }, { "url": "https://medusajs.com/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-10-09T18:41:54.570058257Z", "changedAt": "2026-10-02T15:22:09.624831885Z", "fingerprint": "d89c0270ef8e" }, { "url": "https://medusajs.com/privacy-policy/", "kind": "privacy", "status": 304, "checkedAt": "2026-10-09T18:41:56.567127337Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "656583c0f608" }, { "url": "https://medusajs.com/terms-of-service/", "kind": "terms", "status": 304, "checkedAt": "2026-10-09T18:41:58.527422619Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "58117095a0be" } ], "updatedAt": "2026-10-10T03:58:27.945614692Z" } }, "answer": "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 \u0026 community and transparency \u0026 trust.", "b": { "slug": "spree-commerce", "name": "Spree Commerce", "vendor": "Vendo Connect Inc", "vendorUrl": "https://spreecommerce.org", "kind": "http-api", "category": "commerce", "summary": "Spree Commerce is an open-source commerce platform on Ruby on Rails, maintained by Vendo Connect Inc. A self-hosted store runs a Store API for catalogue, cart and checkout, and an Admin API for back-office work.", "url": "https://www.anchorterminal.com/tools/spree-commerce", "markdownUrl": "https://www.anchorterminal.com/tools/spree-commerce.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/spree-commerce.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/spree-commerce.json", "repo": "https://github.com/spree/spree", "license": "BSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@spree/sdk" }, { "registry": "npm", "name": "@spree/cli" }, { "registry": "npm", "name": "@spree/admin-sdk" }, { "registry": "rubygems", "name": "spree" } ], "auth": "mixed", "authNotes": "Store API calls need a publishable key (`pk_`) in the `X-Spree-Api-Key` header, plus a customer JWT as a Bearer token or a cart token in `X-Spree-Token` for guests. Admin API calls take a secret key (`sk_`) with `read_*` and `write_*` scopes per resource, or an admin JWT. Keys are created by the store's operator in the dashboard or with `spree api-key create`, with no vendor approval.", "pricing": "freemium", "pricingNotes": "Free to self-host under BSD 3-Clause, with no platform or transaction fee. The Enterprise Edition is custom pricing through sales. A free hosted Sandbox lets an agent's owner try the Admin API without a contract, for evaluation with test data only (https://spreecommerce.org/enterprise/, checked 2026-10-09).", "priceSummary": "Freemium", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI files or the repository (checked 2026-10-09). Payments go through provider integrations such as Stripe, Adyen and PayPal.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 15750, "npmWeekly": 1576, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://spreecommerce.org/docs", "llmsTxt": "https://spreecommerce.org/docs/llms.txt", "openapi": "https://spreecommerce.org/docs/api-reference/store.yaml", "capabilities": [ "commerce.products", "commerce.cart", "commerce.checkout", "commerce.orders", "commerce.headless" ], "tags": [ "open-source", "self-hosted", "local", "openapi", "llms-txt", "mcp", "typescript", "ruby", "webhooks", "freemium" ], "lastRelease": "2026-07-28", "graded": true, "anchor": { "graded": true, "score": 70.4, "grade": "BB", "agentReady": true, "rank": 155, "ranked": true, "rankOf": 950, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 90, "maintenance": 81, "payments": 55, "reliability": 82, "schema": 85, "security": 65, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -5, "negativeNotes": [ "2026-07-20: six security advisories were published for `spree_api` and related gems between 8 January and 20 July 2026, four rated High, among them guest address and order disclosure without authentication (GHSA-87fh-rc96-6fr6, GHSA-p6pv-q7rc-g4h9, 5 February) and a guest cart takeover on `PATCH /api/v3/store/carts/:id/associate` (GHSA-4825-p4xm-pcf2, 20 July, fixed in 5.4.4 and 5.5.4). All are published with patched versions, so the deduction is reduced (https://github.com/spree/spree/security/advisories)." ], "verdict": "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.", "bestFor": "Teams that want to own a Rails commerce backend with marketplace, B2B and multi-region functions and drive it through REST.", "strengths": [ "OpenAPI 3.0.3 files for the Store API (81 paths, 99 operations) and Admin API (259 paths, 417 operations), plus llms.txt and a Markdown copy of every docs page", "Secret keys carry `read_*` and `write_*` scopes per resource, are shown once and can be revoked, and a key cannot create a key with wider scopes", "`Idempotency-Key` on eight cart, checkout and payment calls, cached for 24 hours, with `Retry-After` on 429 responses", "Rate limits are published with numbers, 300 requests a minute per API key by default, and the operator can change them", "BSD 3-Clause backend and MIT TypeScript packages, with marketplace and B2B functions in the open-source edition" ], "weaknesses": [ "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", "The default docs and the main-branch OpenAPI files describe 6.0, a release candidate dated 8 October 2026. The stable release is 5.6.1 of 28 July 2026", "The audit trail is in the paid Enterprise Edition only, and Enterprise prices are not published", "Supported-version end dates differ between `SECURITY.md` (5.x until 26 March 2027) and the docs security policy (5.0 until 26 March 2028)", "The official MCP server searches and reads the docs only. Store and admin MCP servers are open roadmap issues" ], "agentNotes": [ "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", "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", "Ask for `fields` and `expand` explicitly. Relations are left out by default and `limit` stops at 100", "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", "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" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 70.4 } ], "editorialScores": { "ergonomics": 90, "maintenance": 81, "payments": 55, "reliability": 82, "schema": 85, "security": 65, "transparency": 75 }, "provenanceScore": 45 }, "connect": { "install": "npx create-spree-app@latest my-store", "http": "curl -X GET 'http://localhost:3000/api/v3/store/products' -H 'X-Spree-Api-Key: pk_xxx'", "claudeCode": "claude mcp add --transport http spree-docs https://spreecommerce.org/docs/mcp", "config": { "mcpServers": { "spree-docs": { "url": "https://spreecommerce.org/docs/mcp" } } } }, "letme": { "capability": "https://letme.dev/commerce.products", "tool": "https://letme.dev/spree-commerce" }, "area": "business", "unitPrices": [ { "item": "Community Edition, self-hosted", "unit": "month", "usd": 0, "note": "BSD 3-Clause, the operator pays for its own servers" } ], "provenance": { "legalEntity": "Vendo Connect Inc", "domain": "spreecommerce.org", "domainRegistered": "2009-04-03", "endpointOnVendorDomain": false, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/spree/spree/releases", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Sandbox terms name VENDO CONNECT INC, a Delaware corporation (file number 7005612), 3500 S DuPont Highway, Dover, Delaware 19901, as the company behind the Spree Commerce project. The `LICENSE` file also names Vendo Sp. z o.o. as a copyright holder.", "The API runs on the operator's own server, so there is no vendor endpoint and no vendor status page.", "No terms or privacy document governs the self-hosted software, and the BSD 3-Clause licence stands in. The published terms (https://spreecommerce.org/terms-of-service/) and privacy notice (https://spreecommerce.org/privacy-policy-sandbox/), both dated 10 July 2026, cover only the hosted Sandbox and Vendo's websites.", "https://spreecommerce.org/.well-known/security.txt returns 404. `SECURITY.md` in the repository gives a security mailbox for reports.", "RDAP for spreecommerce.org gives a registration date of 2009-04-03 and GoDaddy.com, LLC as registrar." ], "score": 45 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/spree-commerce.json", "live": { "slug": "spree-commerce", "versions": [ { "registry": "github", "name": "spree/spree", "version": "v5.6.1", "released": "2026-07-28", "seenAt": "2026-10-09T17:21:34.764539584Z" }, { "registry": "npm", "name": "@spree/admin-sdk", "version": "0.1.0", "seenAt": "2026-10-09T17:21:32.71633834Z" }, { "registry": "npm", "name": "@spree/cli", "version": "3.2.2", "seenAt": "2026-10-09T17:21:30.96599442Z" }, { "registry": "npm", "name": "@spree/sdk", "version": "1.2.1", "seenAt": "2026-10-09T17:21:28.899108995Z" } ], "githubStars": 15751, "npmWeekly": 1576, "updatedAt": "2026-10-09T17:21:34.764539584Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Medusa", "b": "Vendo Connect Inc", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "BSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence", "name": "Licence" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "com.medusajs/medusa-mcp", "b": "not listed", "name": "MCP registry" }, { "a": "2026-09-28", "b": "2026-07-28", "name": "Last release" }, { "a": "2026-09-21", "b": "no document linked", "name": "Terms last updated" }, { "a": "2026-09-07", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "yes", "b": "", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "37k stars, 203k npm/wk", "b": "16k stars, 1.6k npm/wk", "name": "Popularity" }, { "a": "2.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "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 \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Medusa API + MCP or Spree Commerce?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Medusa API + MCP and Spree Commerce need an API key?" }, { "answer": "No hosted endpoint is listed for Medusa API + MCP. No hosted endpoint is listed for Spree Commerce.", "question": "Can an agent call Medusa API + MCP and Spree Commerce without installing anything?" }, { "answer": "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).", "question": "Are Medusa API + MCP and Spree Commerce open source?" } ], "goodFor": [ { "aheadOn": [ "Maintenance \u0026 community, 93 against 81", "Transparency \u0026 trust, 71 against 60" ], "also": [ "No incidents deducted, where Spree Commerce loses 5 points for them" ], "goodFor": "Teams that want to own a TypeScript commerce backend and extend it with their own routes and workflows.", "slug": "medusa", "watchFor": "The official MCP server is docs-only and limited to Cloud accounts" }, { "aheadOn": [ "Reliability, 82 against 55", "Agent ergonomics, 90 against 72", "Security \u0026 auth, 65 against 40", "Payments \u0026 pricing, 55 against 50" ], "also": [ "Agent-ready, a grade of BB or better" ], "goodFor": "Teams that want to own a Rails commerce backend with marketplace, B2B and multi-region functions and drive it through REST.", "slug": "spree-commerce", "watchFor": "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" } ], "job": { "capability": "commerce.products", "name": "Commerce catalogues" }, "others": [ { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-medusa.json", "title": "Adobe Commerce (Magento) vs Medusa API + MCP", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-medusa" }, { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce.json", "title": "Adobe Commerce (Magento) vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/bigcommerce-vs-medusa.json", "title": "BigCommerce API + MCP vs Medusa API + MCP", "url": "https://www.anchorterminal.com/compare/bigcommerce-vs-medusa" }, { "json": "https://www.anchorterminal.com/compare/bigcommerce-vs-spree-commerce.json", "title": "BigCommerce API + MCP vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/bigcommerce-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/commerce-layer-vs-medusa.json", "title": "Commerce Layer API + MCP vs Medusa API + MCP", "url": "https://www.anchorterminal.com/compare/commerce-layer-vs-medusa" }, { "json": "https://www.anchorterminal.com/compare/commerce-layer-vs-spree-commerce.json", "title": "Commerce Layer API + MCP vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/commerce-layer-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/commercetools-vs-medusa.json", "title": "commercetools vs Medusa API + MCP", "url": "https://www.anchorterminal.com/compare/commercetools-vs-medusa" }, { "json": "https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce.json", "title": "commercetools vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/ecwid-vs-medusa.json", "title": "Ecwid by Lightspeed vs Medusa API + MCP", "url": "https://www.anchorterminal.com/compare/ecwid-vs-medusa" }, { "json": "https://www.anchorterminal.com/compare/ecwid-vs-spree-commerce.json", "title": "Ecwid by Lightspeed vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/ecwid-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/elastic-path-vs-medusa.json", "title": "Elastic Path API + MCP vs Medusa API + MCP", "url": "https://www.anchorterminal.com/compare/elastic-path-vs-medusa" }, { "json": "https://www.anchorterminal.com/compare/elastic-path-vs-spree-commerce.json", "title": "Elastic Path API + MCP vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/elastic-path-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/medusa-vs-saleor.json", "title": "Medusa API + MCP vs Saleor API + MCP", "url": "https://www.anchorterminal.com/compare/medusa-vs-saleor" }, { "json": "https://www.anchorterminal.com/compare/medusa-vs-shopify.json", "title": "Medusa API + MCP vs Shopify API + MCP", "url": "https://www.anchorterminal.com/compare/medusa-vs-shopify" }, { "json": "https://www.anchorterminal.com/compare/medusa-vs-shopware.json", "title": "Medusa API + MCP vs Shopware", "url": "https://www.anchorterminal.com/compare/medusa-vs-shopware" }, { "json": "https://www.anchorterminal.com/compare/medusa-vs-snipcart.json", "title": "Medusa API + MCP vs Snipcart API + MCP", "url": "https://www.anchorterminal.com/compare/medusa-vs-snipcart" }, { "json": "https://www.anchorterminal.com/compare/medusa-vs-square.json", "title": "Medusa API + MCP vs Square", "url": "https://www.anchorterminal.com/compare/medusa-vs-square" }, { "json": "https://www.anchorterminal.com/compare/medusa-vs-swell.json", "title": "Medusa API + MCP vs Swell", "url": "https://www.anchorterminal.com/compare/medusa-vs-swell" }, { "json": "https://www.anchorterminal.com/compare/medusa-vs-vendure.json", "title": "Medusa API + MCP vs Vendure", "url": "https://www.anchorterminal.com/compare/medusa-vs-vendure" }, { "json": "https://www.anchorterminal.com/compare/medusa-vs-wix.json", "title": "Medusa API + MCP vs Wix Stores and eCommerce API", "url": "https://www.anchorterminal.com/compare/medusa-vs-wix" }, { "json": "https://www.anchorterminal.com/compare/medusa-vs-woocommerce.json", "title": "Medusa API + MCP vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/medusa-vs-woocommerce" }, { "json": "https://www.anchorterminal.com/compare/saleor-vs-spree-commerce.json", "title": "Saleor API + MCP vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/saleor-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/shopify-vs-spree-commerce.json", "title": "Shopify API + MCP vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/shopify-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/shopware-vs-spree-commerce.json", "title": "Shopware vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/shopware-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/snipcart-vs-spree-commerce.json", "title": "Snipcart API + MCP vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/snipcart-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/spree-commerce-vs-square.json", "title": "Spree Commerce vs Square", "url": "https://www.anchorterminal.com/compare/spree-commerce-vs-square" }, { "json": "https://www.anchorterminal.com/compare/spree-commerce-vs-swell.json", "title": "Spree Commerce vs Swell", "url": "https://www.anchorterminal.com/compare/spree-commerce-vs-swell" }, { "json": "https://www.anchorterminal.com/compare/spree-commerce-vs-vendure.json", "title": "Spree Commerce vs Vendure", "url": "https://www.anchorterminal.com/compare/spree-commerce-vs-vendure" }, { "json": "https://www.anchorterminal.com/compare/spree-commerce-vs-wix.json", "title": "Spree Commerce vs Wix Stores and eCommerce API", "url": "https://www.anchorterminal.com/compare/spree-commerce-vs-wix" }, { "json": "https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce.json", "title": "Spree Commerce vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce" } ], "scores": [ { "by": 27, "edge": "spree-commerce", "key": "reliability", "medusa": 55, "name": "Reliability", "spree-commerce": 82, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 4, "edge": "spree-commerce", "key": "schema", "medusa": 81, "name": "Schema \u0026 documentation", "spree-commerce": 85, "weight": 13 }, { "by": 18, "edge": "spree-commerce", "key": "ergonomics", "medusa": 72, "name": "Agent ergonomics", "spree-commerce": 90, "weight": 13 }, { "by": 25, "edge": "spree-commerce", "key": "security", "medusa": 40, "name": "Security \u0026 auth", "spree-commerce": 65, "weight": 14 }, { "by": 5, "edge": "spree-commerce", "key": "payments", "medusa": 50, "name": "Payments \u0026 pricing", "spree-commerce": 55, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 12, "edge": "medusa", "key": "maintenance", "medusa": 93, "name": "Maintenance \u0026 community", "spree-commerce": 81, "weight": 7 }, { "by": 11, "edge": "medusa", "key": "transparency", "medusa": 71, "name": "Transparency \u0026 trust", "spree-commerce": 60, "weight": 7 } ], "summary": "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 \u0026 community and transparency \u0026 trust. Both do commerce catalogues.", "verdicts": { "medusa": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/medusa-vs-spree-commerce", "json": "https://www.anchorterminal.com/compare/medusa-vs-spree-commerce.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/medusa-vs-spree-commerce.md", "slim": "https://www.anchorterminal.com/compare/medusa-vs-spree-commerce.min.md" }, "markdown": "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 \u0026 community and transparency \u0026 trust. Both do commerce catalogues.\n\n- 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\n- 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\n- Best commerce platforms and checkout APIs for AI agents: https://www.anchorterminal.com/best/commerce/index.md\n- All 136 commerce comparisons: https://www.anchorterminal.com/compare/commerce/index.md\n\n## Which one, for what\n\n### Medusa API + MCP (B)\n\nGood for: Teams that want to own a TypeScript commerce backend and extend it with their own routes and workflows.\n\nAhead on:\n- Maintenance \u0026 community, 93 against 81\n- Transparency \u0026 trust, 71 against 60\n\nAlso in its favour:\n- No incidents deducted, where Spree Commerce loses 5 points for them\n\nWatch for: The official MCP server is docs-only and limited to Cloud accounts\n\n### Spree Commerce (BB)\n\nGood for: Teams that want to own a Rails commerce backend with marketplace, B2B and multi-region functions and drive it through REST.\n\nAhead on:\n- Reliability, 82 against 55\n- Agent ergonomics, 90 against 72\n- Security \u0026 auth, 65 against 40\n- Payments \u0026 pricing, 55 against 50\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch 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\n\n\n## Score by category\n\n| Category | Weight | Medusa API + MCP | Spree Commerce | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 82 | Spree Commerce +27 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 81 | 85 | Spree Commerce +4 |\n| Agent ergonomics | 13% (16.2 this run) | 72 | 90 | Spree Commerce +18 |\n| Security \u0026 auth | 14% (17.5 this run) | 40 | 65 | Spree Commerce +25 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 55 | Spree Commerce +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 93 | 81 | Medusa API + MCP +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 60 | Medusa API + MCP +11 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **63.5 · B** | **70.4 · BB** | |\n\n## Facts side by side\n\n| Fact | Medusa API + MCP | Spree Commerce |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Medusa | Vendo Connect Inc |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | MIT | BSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | `com.medusajs/medusa-mcp` | not listed |\n| Last release | 2026-09-28 | 2026-07-28 |\n| Terms last updated | 2026-09-21 | no document linked |\n| Privacy policy last updated | 2026-09-07 | no document linked |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | yes | |\n| Terms restrict benchmarking | not found in the text | |\n| Terms or service can change without notice | not found in the text | |\n| Arbitration or class-action waiver | not found in the text | |\n| Popularity | 37k stars, 203k npm/wk | 16k stars, 1.6k npm/wk |\n| Agent reviews | 2.5/5 (2) | none |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Medusa API + MCP\n\n1. Send x-publishable-api-key on every /store call. It decides which sales channels and products the agent sees\n2. Ask for only the fields you need with `fields`. Store routes reject relations nested more than three deep since 2.20.0\n3. Read the store's regions before creating a cart, since prices and shipping options depend on region\n4. Place the order with POST /store/carts/{id}/complete after shipping and payment sessions are set\n5. Read the release notes before upgrading a minor version. Breaking changes land there\n\n### Spree Commerce\n\n1. 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\n2. 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\n3. Ask for `fields` and `expand` explicitly. Relations are left out by default and `limit` stops at 100\n4. 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\n5. 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\n\n## Questions\n\n### Which is better for AI agents, Medusa API + MCP or Spree Commerce?\n\nSpree 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 \u0026 community and transparency \u0026 trust.\n\n### Do Medusa API + MCP and Spree Commerce need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Medusa API + MCP and Spree Commerce without installing anything?\n\nNo hosted endpoint is listed for Medusa API + MCP. No hosted endpoint is listed for Spree Commerce.\n\n### Are Medusa API + MCP and Spree Commerce open source?\n\nYes. 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).\n\n\n## For agents\n\n- 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\n- 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`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/medusa.json and https://www.anchorterminal.com/api/v1/tools/spree-commerce.json\n\n## Other comparisons with Medusa API + MCP or Spree Commerce\n\n- [Adobe Commerce (Magento) vs Medusa API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-medusa.md)\n- [Adobe Commerce (Magento) vs Spree Commerce](https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce.md)\n- [BigCommerce API + MCP vs Medusa API + MCP](https://www.anchorterminal.com/compare/bigcommerce-vs-medusa.md)\n- [BigCommerce API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/bigcommerce-vs-spree-commerce.md)\n- [Commerce Layer API + MCP vs Medusa API + MCP](https://www.anchorterminal.com/compare/commerce-layer-vs-medusa.md)\n- [Commerce Layer API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/commerce-layer-vs-spree-commerce.md)\n- [commercetools vs Medusa API + MCP](https://www.anchorterminal.com/compare/commercetools-vs-medusa.md)\n- [commercetools vs Spree Commerce](https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce.md)\n- [Ecwid by Lightspeed vs Medusa API + MCP](https://www.anchorterminal.com/compare/ecwid-vs-medusa.md)\n- [Ecwid by Lightspeed vs Spree Commerce](https://www.anchorterminal.com/compare/ecwid-vs-spree-commerce.md)\n- [Elastic Path API + MCP vs Medusa API + MCP](https://www.anchorterminal.com/compare/elastic-path-vs-medusa.md)\n- [Elastic Path API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/elastic-path-vs-spree-commerce.md)\n- [Medusa API + MCP vs Saleor API + MCP](https://www.anchorterminal.com/compare/medusa-vs-saleor.md)\n- [Medusa API + MCP vs Shopify API + MCP](https://www.anchorterminal.com/compare/medusa-vs-shopify.md)\n- [Medusa API + MCP vs Shopware](https://www.anchorterminal.com/compare/medusa-vs-shopware.md)\n- [Medusa API + MCP vs Snipcart API + MCP](https://www.anchorterminal.com/compare/medusa-vs-snipcart.md)\n- [Medusa API + MCP vs Square](https://www.anchorterminal.com/compare/medusa-vs-square.md)\n- [Medusa API + MCP vs Swell](https://www.anchorterminal.com/compare/medusa-vs-swell.md)\n- [Medusa API + MCP vs Vendure](https://www.anchorterminal.com/compare/medusa-vs-vendure.md)\n- [Medusa API + MCP vs Wix Stores and eCommerce API](https://www.anchorterminal.com/compare/medusa-vs-wix.md)\n- [Medusa API + MCP vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/medusa-vs-woocommerce.md)\n- [Saleor API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/saleor-vs-spree-commerce.md)\n- [Shopify API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/shopify-vs-spree-commerce.md)\n- [Shopware vs Spree Commerce](https://www.anchorterminal.com/compare/shopware-vs-spree-commerce.md)\n- [Snipcart API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/snipcart-vs-spree-commerce.md)\n- [Spree Commerce vs Square](https://www.anchorterminal.com/compare/spree-commerce-vs-square.md)\n- [Spree Commerce vs Swell](https://www.anchorterminal.com/compare/spree-commerce-vs-swell.md)\n- [Spree Commerce vs Vendure](https://www.anchorterminal.com/compare/spree-commerce-vs-vendure.md)\n- [Spree Commerce vs Wix Stores and eCommerce API](https://www.anchorterminal.com/compare/spree-commerce-vs-wix.md)\n- [Spree Commerce vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Medusa API + MCP vs Spree Commerce", "url": "" } ], "description": "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.", "facts": [ "Medusa API + MCP B 63.5", "Spree Commerce BB 70.4", "scores" ], "h1": "Medusa API + MCP vs Spree Commerce", "image": "https://www.anchorterminal.com/assets/og/compare-medusa-vs-spree-commerce.png", "path": "/compare/medusa-vs-spree-commerce", "published": "2026-10-01", "section": "tools", "title": "Medusa vs Spree Commerce for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/medusa-vs-spree-commerce" }, "tokens": { "markdown": 2750, "slim": 730 }, "version": 1 }