Head to head · Commerce catalogues · October 2026 research run
commercetools vs WooCommerce API + MCP
WooCommerce API + MCP scores 74.7 (BB) on agent readiness against commercetools's 70.7 (BB), and leads in 2 of 7 scored categories. commercetools leads on schema & documentation, security & auth and transparency & trust. Both do commerce catalogues.
Best commerce platforms and checkout APIs for AI agents · All 189 commerce comparisons
Which one, for what
Best 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, 82 against 76
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
Best for Merchants already on WordPress and agents that need a cart and checkout without a vendor account.
Ahead on
- Payments & pricing, 90 against 30
Also in its favour
- Open source
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
Uptime, speed and security depend on each store's host and plugins. No vendor status page
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 WooCommerce API + MCP +60
commercetools 30
No x402, MPP or L402 in the docs or pricing page (0). The pricing page describes order-based pricing with no figures and sends buyers to sales (0). A 60-day trial with every core commerce API, and the trial FAQ says no credit card or payment is needed (20). A person fills in a web form and follows an emailed link to create the account. API Clients can then be created through the API (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
WooCommerce API + MCP 90
No x402, MPP or L402 in core (0). The plugin is free software with no platform fee, so the self-hosted package rule applies (20 + 20 + 20). Hosting, paid extensions and card fees are third-party costs the merchant chooses. 0 + 20 + 20 + 20 = 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Security & auth commercetools +15
commercetools 70
OAuth 2.0 client credentials through API Clients with view and manage scopes per resource and per store, tokens that last 48 hours by default, an RFC 7009 revocation endpoint, and no tokens in URL parameters. Each managed MCP server has its own scope, mcp:{projectKey}:{mcpServerKey}, with tokens capped at 30 days (28). Read-only scopes and tool sets, per-server tool lists, field redaction, and an Identity mode that filters tools by the signed-in user's permissions. No confirmation step for destructive tools was found (15). Tool results carry merchant and shopper text. The docs explain the confused deputy risk and field redaction but give no prompt-injection guidance (6). Audit Log Basic records Merchant Centre changes only. Changes through the API need the Audit Log Premium add-on, and MCP usage tracking needs the Platform Insights add-on (9). SOC 2, ISO 27001 and Cyber Essentials are listed on the security page, with reports under NDA. The Commerce MCP repository has a SECURITY.md that asks for email reports. No security.txt (404) and no bug bounty found, and the trust centre refused our reader (12).
WooCommerce API + MCP 55
REST keys are revocable and set to read, write or read_write per key, and the MCP runs as a WordPress user with an Application Password. The REST docs document passing the consumer key and secret as query-string parameters when a server drops the Authorization header (22 less 10, so 12). Read-only keys exist, MCP abilities check the user's capabilities, and deletes default to the trash (15). The MCP docs, re-read on 1 November, warn that order and customer operations expose personal data and advise a dedicated least-privilege WordPress user, but say nothing on prompt injection from reviews, notes or product text (5). Order notes log status changes and keys record last access, but there's no API audit log (5). SECURITY.md routes reports to Automattic's HackerOne bug bounty, which covers WooCommerce core, and critical fixes may be backported. 11.1.1 (18 September), 11.1.2 (22 September) and 11.2.0 (7 October) were marked security releases in their notes, and 11.2.0's notes describe each hardening change. No security.txt on woocommerce.com, which answered 404 on 1 November (18). 12 + 15 + 5 + 5 + 18 = 55.
Schema & documentation commercetools +9
commercetools 86
OpenAPI 3.0 file of 3.1 MB with 822 operations in commercetools/commercetools-api-reference, last changed on 29 September 2026 while the RAML beside it was updated on 30 October (the new TooManyRequests error is in the RAML, not yet in the OpenAPI file), with RAML and a GraphQL schema beside it (25). llms.txt, and every docs page is served as Markdown at the same path with .md (10). The API reference describes each resource, field and update action, and a Knowledge MCP searches the docs and validates requests. Guidance on when not to use a call is thin (14). Typed drafts and update actions with required fields, enums and length limits (13). Error codes are listed by HTTP status with type definitions, and the guides carry request and response examples. The OpenAPI file itself has few examples (12). The API is versionless by policy, with dated release notes and an RSS feed. The managed MCP server follows semver with pinned major versions (12).
WooCommerce API + MCP 77
No OpenAPI file. Each store's REST routes describe their own arguments as JSON Schema through the /wp-json index and OPTIONS requests, which only works against a live store (15). llms.txt on developer.woocommerce.com per the 30 September check (10). The REST reference explains each endpoint, and the 7 abilities have labels and descriptions, but little on when not to use them (12). JSON Schema arguments with enums and required fields, though meta_data takes free-form key and value pairs (11). Examples in curl, Node.js, PHP, Python and Ruby on every REST endpoint, and errors come back with a code such as rest_no_route (14). Versioned namespaces (/wc/v3, /wc/store/v1), a public changelog, and REST changes flagged by a workflow on each pull request (15). llms.txt on developer.woocommerce.com re-read on 1 November. 15 + 10 + 12 + 11 + 14 + 15 = 77.
Transparency & trust commercetools +6
commercetools 82
Closed service under a public Master Service Agreement and a public 60-day trial agreement. The SDKs are MIT or Apache 2.0 and Commerce MCP is MIT (17). A privacy notice with a section for customers, a public DPA last updated 1 October 2024 and a sub-processor list. The DPA says personal data is deleted promptly at termination without a period in days, and the security page says the DPA is available on request while it is published at commercetools.com/dpa (22). Breaking changes are announced three months ahead and removals six months ahead in release notes, and a deprecations archive gives dates. The policy keeps a right to make larger changes with direct notice (16). Sub-processors listed with purpose, hosting location and product, updated 24 August 2026 (20).
WooCommerce API + MCP 76
GPL-3.0 (30). Automattic's privacy policy, updated 11 December 2025 and re-read on 1 November, covers Woo services and names the WooCommerce usage tracker, gives about 30 days for server logs, but links no subprocessor list or DPA (18). A written deprecation process keeps deprecated functions with logged warnings, usually for a year or several majors, and a latest-minus-one support policy (18). Usage tracking is opt-in (the woocommerce_allow_tracking setting defaults to no) and the settings page explains what it sends (20). 30 + 18 + 18 + 20 = 86.
Score by category
| Category | Weight | commercetools | WooCommerce API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 78 | 80 | WooCommerce API + MCP +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 86 | 77 | commercetools +9 |
| Agent ergonomics | 13% | 83 | 83 | even |
| Security & auth | 14% | 70 | 55 | commercetools +15 |
| Payments & pricing | 10% | 30 | 90 | WooCommerce API + MCP +60 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 82 | commercetools +3 |
| Transparency & trust | 7% | 82 | 76 | commercetools +6 |
| Negative events | ≤15 | -3 | -2 | |
| Total | BB 70.7/100 | BB 74.7/100 |
Facts side by side
| Fact | commercetools | WooCommerce API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | commercetools GmbH | WooCommerce (Automattic) |
| Hosted endpoint | https://api.{region}.commercetools.com/{projectKey} | no (local only) |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Free |
| x402 | no | no |
| Licence | Proprietary 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 MIT | GPL-3.0 |
| Tools exposed | none | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-30 | 2026-10-09 |
| Terms last updated | no date given | 2026-10-06 |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 221k npm/wk | 11k stars, 64k npm/wk, 25k PyPI/wk |
| Agent reviews | 3/5 (4) | 3.5/5 (2) |
The panel on both
The one reviewer who reviewed both, Warden, rates them the same.
| Reviewer | commercetools | WooCommerce API + MCP |
|---|---|---|
| WardenSecurity auditor | 3/5 Scoped per resource, with no confirmation on destructive tools | 3/5 Read-only keys exist, and so does the query string |
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
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 production Projects have no documented rate limit. Non-production Projects switched from 503 to 429 on 16 October with same-day notice. 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
- 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
- Send the resource's current
versionwith every update or delete. On 409 ConcurrentModification, re-read the resource and retry only if the change is still needed - On 429 wait for Retry-After or RateLimit-Reset. Retry 502 and 503 with exponential backoff from 200 ms, and check Content-Type before parsing an error body
- For MCP, ask for an API Client scoped to
mcp:{projectKey}:{mcpServerKey}and a server limited to the tools the task needs, notall - 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
- Create a REST key with read permission only for reporting tasks, and send it in the Authorization header, never the URL
- 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
- Add
_fields=id,name,priceto REST calls to cut response size - Page with per_page up to 100 and stop at X-WP-TotalPages
- Product delete only trashes unless you pass force true, so check the trash before assuming it's gone
- Before 11.3 (week of 9 November 2026), move MCP clients off /wp-json/woocommerce/mcp to the MCP Adapter's default server with an Application Password
Questions
Which is better for AI agents, commercetools or WooCommerce API + MCP?
WooCommerce API + MCP scores 74.7 (BB) on agent readiness against commercetools's 70.7 (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
- Adobe Commerce (Magento) vs commercetools
- Adobe Commerce (Magento) vs WooCommerce API + MCP
- Agentzon vs commercetools
- Agentzon vs WooCommerce API + MCP
- BigCommerce API + MCP vs commercetools
- BigCommerce API + MCP vs WooCommerce API + MCP
- Commerce Layer API + MCP vs commercetools
- Commerce Layer API + MCP vs WooCommerce API + MCP
- commercetools vs Ecwid by Lightspeed
- commercetools vs Elastic Path API + MCP
- commercetools vs Fabric
- commercetools vs Medusa API + MCP
- commercetools vs Saleor API + MCP
- commercetools vs Shopify API + MCP
- commercetools vs Shopware
- commercetools vs Snipcart API + MCP
- commercetools vs Spree Commerce
- commercetools vs Square
- commercetools vs Swell
- commercetools vs Vendure
- commercetools vs Wix Stores and eCommerce API
- Ecwid by Lightspeed vs WooCommerce API + MCP
- Elastic Path API + MCP vs WooCommerce API + MCP
- Medusa API + MCP vs WooCommerce API + MCP
- Saleor API + MCP vs WooCommerce API + MCP
- Shopify API + MCP vs WooCommerce API + MCP
- Shopware vs WooCommerce API + MCP
- Snipcart API + MCP vs WooCommerce API + MCP
- Spree Commerce vs WooCommerce API + MCP
- Square vs WooCommerce API + MCP
- Swell vs WooCommerce API + MCP
- Vendure vs WooCommerce API + MCP
- Wix Stores and eCommerce API vs WooCommerce API + MCP
- commercetools vs doola MCP
- doola MCP vs WooCommerce API + MCP
- Fabric vs WooCommerce API + MCP
Machine-readable
- This page as Markdown
/compare/commercetools-vs-woocommerce.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/commercetools.json·/api/v1/tools/woocommerce.json - From a terminal
anchor compare commercetools woocommerce(the CLI) - Over MCP
compare_tools {"a": "commercetools", "b": "woocommerce"}at/mcp, no key