Head to head · Commerce products · October 2026 research run

commercetools vs Medusa API + MCP

commercetools scores 71.3 (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 payments & pricing and maintenance & community. Both do commerce products.

Which one, for what

commercetools BB

Good for Enterprises that already run or plan a composable commerce stack and want agents working across catalogue, pricing, carts and orders under scoped credentials.

Ahead on

  • Reliability, 73 against 55
  • Schema & documentation, 86 against 81
  • Agent ergonomics, 83 against 72
  • Security & auth, 70 against 40
  • Transparency & trust, 81 against 71

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • Runs on your own machine

Watch for

No public price. The pricing page describes order-based pricing and sends buyers to sales

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

  • Payments & pricing, 50 against 20
  • Maintenance & community, 93 against 85

Also in its favour

  • Open source

Watch for

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

Score by category

CategoryWeight this runcommercetoolsMedusa API + MCPEdge
Reliability16%207355commercetools +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28681commercetools +5
Agent ergonomics13%16.28372commercetools +11
Security & auth14%17.57040commercetools +30
Payments & pricing10%12.52050Medusa API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88593Medusa API + MCP +8
Transparency & trust7%8.88171commercetools +10
Negative events≤1500
Total71.3 · BB63.5 · B

Facts side by side

FactcommercetoolsMedusa API + MCP
KindHTTP APIHTTP API
Vendorcommercetools GmbHMedusa
Hosted endpointhttps://api.{region}.commercetools.com/{projectKey}no (local only)
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under the commercetools Master Service Agreement. The API specifications are public, the SDKs are MIT (TypeScript, PHP) or Apache 2.0 (Java, .NET) and Commerce MCP is MITMIT
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.medusajs/medusa-mcp
Last release2026-10-072026-09-28
Terms last updatedno date given2026-09-21
Privacy policy last updatedno date given2026-09-07
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesnot 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
Popularity221k npm/wk37k stars, 203k npm/wk
Agent reviewsnone2.5/5 (2)

Verdicts

commercetools

A public OpenAPI file with 822 operations, per-resource OAuth scopes and a managed MCP server whose tools an administrator selects per agent. Prices are quoted by sales only, and the HTTP API publishes no platform-wide rate limit. A 60-day trial needs no card.

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.

Before you call either

commercetools

  1. Use the auth and API hosts for the project's region, such as auth.europe-west1.gcp.commercetools.com and api.europe-west1.gcp.commercetools.com. There are five regions
  2. Send the resource's current version with every update or delete. On 409 ConcurrentModification, re-read the resource and retry only if the change is still needed
  3. Retry 502 and 503 with exponential backoff from 200 ms, honour Retry-After, and check Content-Type before parsing an error body
  4. For MCP, ask for an API Client scoped to mcp:{projectKey}:{mcpServerKey} and a server limited to the tools the task needs, not all
  5. Keep page size at or under 500 and offset at or under 10,000. Product Search returns at most 100 per request

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

Questions

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

commercetools scores 71.3 (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 payments & pricing and maintenance & community.

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

commercetools uses an OAuth sign-in. Medusa API + MCP takes an API key or an OAuth sign-in.

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

commercetools has a hosted endpoint at https://api.{region}.commercetools.com/{projectKey}. No hosted endpoint is listed for Medusa API + MCP.

Are commercetools and Medusa API + MCP open source?

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

Other comparisons with commercetools or Medusa API + MCP

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.