Head to head · Commerce products · October 2026 research run

commercetools vs Shopify API + MCP

Shopify API + MCP scores 75 (BB) on agent readiness against commercetools's 71.3 (BB), and leads in 4 of 7 scored categories. 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.

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

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

Shopify API + MCP BB

Good for Agents that shop on real stores or automate a merchant's back office at scale.

Ahead on

  • Schema & documentation, 92 against 86
  • Payments & pricing, 40 against 20
  • Transparency & trust, 88 against 81

Watch for

Closed platform. You can't self-host or change checkout internals

Score by category

CategoryWeight this runcommercetoolsShopify API + MCPEdge
Reliability16%207373even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28692Shopify API + MCP +6
Agent ergonomics13%16.28379commercetools +4
Security & auth14%17.57071Shopify API + MCP +1
Payments & pricing10%12.52040Shopify API + MCP +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88585even
Transparency & trust7%8.88188Shopify API + MCP +7
Negative events≤1500
Total71.3 · BB75 · BB

Facts side by side

FactcommercetoolsShopify API + MCP
KindHTTP APIHTTP API
Vendorcommercetools GmbHShopify
Hosted endpointhttps://api.{region}.commercetools.com/{projectKey}no (local only)
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP, stdio
AuthOAuthOAuth or key
PricingPaidPaid
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 MITnone
Read-only variant documentednono
llms.txtyesno
Last release2026-10-072026-09-30
Terms last updatedno date given2026-08-01
Privacy policy last updatedno date given2026-07-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 textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity221k npm/wk657k npm/wk
Agent reviewsnone3.6/5 (8)

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.

Shopify API + MCP

Typed GraphQL schemas with quarterly versions supported at least 12 months. Closed platform. You can't self-host or change checkout internals.

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

Shopify API + MCP

  1. Pin an API version in the URL and plan to move at least once a year. Old versions fall forward to the oldest supported one
  2. Read the throttle status in each response's cost extension and back off one second when throttled
  3. Send an agent profile in meta on every UCP call, and an idempotency key on every checkout write
  4. Check userErrors on every mutation. A 200 response can still carry a failed write
  5. Add @shopify/dev-mcp while writing code so the agent checks queries against the current schema

Questions

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

Shopify API + MCP scores 75 (BB) on agent readiness against commercetools's 71.3 (BB), and leads in 4 of 7 scored categories.

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

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

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

commercetools has a hosted endpoint at https://api.{region}.commercetools.com/{projectKey}. Shopify API + MCP runs on your own machine, with no hosted endpoint listed.

Other comparisons with commercetools or Shopify 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.