Head to head · Commerce products · October 2026 research run

commercetools vs WooCommerce API + MCP

WooCommerce API + MCP scores 72.9 (BB) on agent readiness against commercetools's 71.3 (BB), and leads in 2 of 7 scored categories. commercetools leads on schema & documentation, security & auth and transparency & trust. 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

  • Schema & documentation, 86 against 77
  • Security & auth, 70 against 55
  • Transparency & trust, 81 against 75

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

WooCommerce API + MCP BB

Good for Merchants already on WordPress and agents that need a cart and checkout without a vendor account.

Ahead on

  • Reliability, 80 against 73
  • Payments & pricing, 60 against 20

Also in its favour

  • Open source

Watch for

Uptime, speed and security depend on each store's host and plugins. No vendor status page

Score by category

CategoryWeight this runcommercetoolsWooCommerce API + MCPEdge
Reliability16%207380WooCommerce API + MCP +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28677commercetools +9
Agent ergonomics13%16.28383even
Security & auth14%17.57055commercetools +15
Payments & pricing10%12.52060WooCommerce API + MCP +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88582commercetools +3
Transparency & trust7%8.88175commercetools +6
Negative events≤1500
Total71.3 · BB72.9 · BB

Facts side by side

FactcommercetoolsWooCommerce API + MCP
KindHTTP APIHTTP API
Vendorcommercetools GmbHWooCommerce (Automattic)
Hosted endpointhttps://api.{region}.commercetools.com/{projectKey}no (local only)
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP, stdio
AuthOAuthOAuth or key
PricingPaidFree
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 MITGPL-3.0
Tools exposednone7
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-072026-09-22
Terms last updatedno date given2026-10-06
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
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/wk11k stars, 64k npm/wk, 25k PyPI/wk
Agent reviewsnone3.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.

WooCommerce API + MCP

Free GPL software with no platform fee or revenue share. Uptime, speed and security depend on each store's host and plugins. No vendor status page.

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

WooCommerce API + MCP

  1. Create a REST key with read permission only for reporting tasks, and send it in the Authorization header, never the URL
  2. Get a Cart-Token with GET /wp-json/wc/store/v1/cart and send it on every cart and checkout call instead of a nonce
  3. Add _fields=id,name,price to REST calls to cut response size
  4. Page with per_page up to 100 and stop at X-WP-TotalPages
  5. Product delete only trashes unless you pass force true, so check the trash before assuming it's gone

Questions

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

WooCommerce API + MCP scores 72.9 (BB) on agent readiness against commercetools's 71.3 (BB), and leads in 2 of 7 scored categories. commercetools leads on schema & documentation, security & auth and transparency & trust.

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

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

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

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

Are commercetools and WooCommerce API + MCP open source?

No open-source release is listed for commercetools. WooCommerce API + MCP is open source (GPL-3.0).

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