Head to head · Commerce catalogues · October 2026 research run

Medusa API + MCP vs Swell

Medusa API + MCP scores 60.3 (C) on agent readiness against Swell's 57 (C), and leads in 6 of 7 scored categories. Swell leads on reliability. 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

  • Schema & documentation, 81 against 71
  • Agent ergonomics, 72 against 65
  • Security & auth, 49 against 42
  • Payments & pricing, 75 against 38
  • Maintenance & community, 93 against 82
  • Transparency & trust, 72 against 60

Also in its favour

  • Open source

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

Swell C

Best for Developers who want a hosted headless store with a flexible data model and an agent that writes server-side.

Ahead on

  • Reliability, 67 against 55

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

One full-access secret key per environment, with no scoped or read-only key

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.

Payments & pricing Medusa API + MCP +37

Medusa API + MCP 75

No x402, MPP or L402 (0). Medusa Cloud plan prices start from $29, $99 and $299 a month with per-unit overage ($0.30 per 1M edge requests, $20 per 100,000 search requests), all public, but each plan is a floor price (15). The MIT core is free to self-host with no card, and since 30 September new Cloud organisations start a free trial without payment details (20). An agent can install and run the core locally with npx create-medusa-app and no account, but Cloud and its MCP server need a person to sign up and approve in a browser (15). 0+15+20+15 = 50. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Swell 38

No x402, MPP or L402 (0). Plan prices are public with per-unit overage, $5 per extra 100K API requests and $5 per extra GB, plus 2 to 0.4 per cent above each sales ceiling (15). No free plan. A free trial on every plan, with the card requirement not stated (10). A person signs up in the browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Reliability Swell +12

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.

Swell 67

Atlassian Statuspage at status.swell.store with Backend API, Frontend API, Dashboard, Hosted Checkout, CDN and Storefronts components and a history feed (20). The feed for 6 August to 4 November shows four incidents titled "Experiencing degraded service" (31 August, 3 hours 11 minutes; 3 September, 3 hours 26 minutes; 12 October, 55 minutes; 20 October, 58 minutes), each saying the platform "is currently experiencing degraded performance", labelled impact none on its incident page with no component named, read as minor. Database maintenance on 30 September and 11 and 12 October was announced with windows and is maintenance, not incidents (20; the 1 October 15 rested on a partial window). Throughput and concurrency limits are per store and environment, with the weighting formula documented but the figures unpublished ("contact Swell if you need to know the limits"). Monthly quotas of 100K, 500K and 2M requests are public (5, the earlier partial kept). Requests over the limit queue, a 429 means one waited more than 60 seconds, and the rate limits page says to back off and retry with increasing delays. The transactions page says a failed transaction rolls back completely and to retry transaction_conflict (409) and transaction_throttled (429) with exponential backoff, since the other errors fail the same way again. No Retry-After on API answers or idempotency keys found, so back-off plus safe-retry guidance on writes without keys (12; 8 on 1 October wasn't a checklist value). The pricing page lists a "100% uptime SLA" on Unlimited, but robots.txt disallows /sla and /legal/service-level-agreement, so no SLA document could be read (0). Generally available (10). 20 + 20 + 5 + 12 + 0 + 10 = 67.

Transparency & trust Medusa API + MCP +12

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.

Swell 60

Closed platform with published terms, and MIT SDKs and skills (15). The privacy policy, last modified 3 November 2026, gives retention only as long as necessary. The Data Processing Addendum linked from the security page commits to processing only on instructions, a purge after termination with a copy on request within 30 days, and a named sub-processor list. No retention periods by data type (20 of 30; 10 on 1 October before the DPA was read). No deprecation policy or dated notices found (0). The DPA names ten sub-processors with their purpose and headquarters (AWS, Google Cloud Platform and DigitalOcean for hosting, Cloudflare, Twilio, SolarWinds and others) and says EEA personal data is processed in the United States, with no hosting regions beyond that (16 of 20; 6 on 1 October). 15 + 20 + 0 + 16 = 51.

Maintenance & community Medusa API + MCP +11

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.

Swell 82

Re-read from depth-200 clones and the changelog on 4 November. swell-js v5.9.3 was tagged on 3 November 2026, the day before (30). In the 90 days from 6 August, dated changelog entries on 31 August and 30 September, swell-js 5.8.2 (24 September), 5.9.0 (28 September), 5.9.1 (29 September), 5.9.2 (7 October) and 5.9.3, and the official skills plugin from 0.7.0 (8 October) to 0.12.0 (2 November) (20). Monthly changelog and email and chat support on every plan (12, kept). swell-js is current; swell-node's last tag is still 6.0.5 from 18 May 2026. No Swell MCP server in the registry (12, kept). Test workflows in both SDK repositories (8). 30 + 20 + 12 + 12 + 8 = 82.

Schema & documentation Medusa API + MCP +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).

Swell 71

No OpenAPI file. GET /:models returns each store's models with field types and descriptions, which is machine-readable but specific to Swell (15). developers.swell.is/llms.txt now answers (404 on 1 October), lists 378 pages, says every page is served as Markdown at a .md address and links llms-full.txt (10). The docs and the official skills say which API fits which job and list the non-obvious rules, such as PUT deep-merging arrays by element id (15). Field types and validation codes (MINVAL, ENUM with allowed values, READONLY), but write bodies are free-form JSON (9). Status codes and validation objects documented with examples (13). Monthly dated changelog with no API versioning (9). 15 + 10 + 15 + 9 + 13 + 9 = 71.

Agent ergonomics Medusa API + MCP +7

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).

Swell 65

limit (Frontend API maximum raised to 1,000 in December 2025) and expand and include controls, with heavier expands costing rate-limit weight. Field selection not confirmed (15). Page envelopes with count, page and page_count, plus where operators, sort and search (20). Validation errors carry a code per field, but invalid writes return HTTP 200 with an errors object, so an agent that doesn't check them reports success (15). No idempotency keys. Transactions roll back only on request errors, and there's no undo for merges (5). Official JavaScript libraries only (swell-node and swell-js), with simple Basic auth (10).

Score by category

CategoryWeightMedusa API + MCPSwellEdge
Reliability16%5567Swell +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8171Medusa API + MCP +10
Agent ergonomics13%7265Medusa API + MCP +7
Security & auth14%4942Medusa API + MCP +7
Payments & pricing10%7538Medusa API + MCP +37
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9382Medusa API + MCP +11
Transparency & trust7%7260Medusa API + MCP +12
Negative events≤15-8-3
TotalC 60.3/100C 57/100

Facts side by side

FactMedusa API + MCPSwell
KindHTTP APIHTTP API
VendorMedusaSwell
Hosted endpointno (local only)https://api.swell.store
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
x402nono
LicenceMITnone
Tools exposed18none
Read-only variant documentedyesno
llms.txtyesyes
MCP registrycom.medusajs/cloudnot listed
Last release2026-10-302026-11-03
Terms last updated2026-09-21no date given
Privacy policy last updated2026-09-072026-08-19
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
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/wk4.5k npm/wk
Agent reviews2.5/5 (2)2.5/5 (2)

The panel on both

The 2 reviewers who reviewed both rate 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.

Swell

Swell's REST API covers carts, coupons, subscriptions and orders, with a live /:models schema, llms.txt and Markdown docs, and a named sub-processor list. Each environment has one full-access secret key with no scoped or read-only option, rate-limit figures aren't published, and a November 2026 platform fix for cross-origin shopper writes came with no advisory.

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

Swell

  1. Call GET /:models once and cache it. It's the ground truth for custom fields
  2. Check result.errors after every write. A failed validation still returns 200
  3. Use $set to replace an array. A plain PUT merges arrays by element id and never shrinks them
  4. Use an sk_test_ key while testing. A bare sk_ prefix is live
  5. Keep expand and include small. Each level past the first three points adds rate-limit weight

Questions

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

Medusa API + MCP scores 60.3 (C) on agent readiness against Swell's 57 (C), and leads in 6 of 7 scored categories. Swell leads on reliability.

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

Medusa API + MCP takes an API key or an OAuth sign-in. Swell needs an API key.

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

No hosted endpoint is listed for Medusa API + MCP. Swell has a hosted endpoint at https://api.swell.store.

Are Medusa API + MCP and Swell open source?

Medusa API + MCP is open source (MIT). No open-source release is listed for Swell.

Other comparisons with Medusa API + MCP or Swell

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.