Head to head · Commerce products · October 2026 research run

Commerce Layer API + MCP vs WooCommerce API + MCP

WooCommerce API + MCP has a score of 73 (BB) against Commerce Layer API + MCP's 63.9 (B). Both do commerce products. The largest gap is payments & pricing, 35 points.

Which one, for what

Pick Commerce Layer API + MCP for

  • security & auth (+9)

Pick WooCommerce API + MCP for

  • reliability (+10)
  • agent ergonomics (+19)
  • payments & pricing (+35)
  • transparency & trust (+17)

Score by category

CategoryWeight this runCommerce Layer API + MCPWooCommerce API + MCPEdge
Reliability16%207080WooCommerce API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27977Commerce Layer API + MCP +2
Agent ergonomics13%16.26483WooCommerce API + MCP +19
Security & auth14%17.56455Commerce Layer API + MCP +9
Payments & pricing10%12.52560WooCommerce API + MCP +35
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88282even
Transparency & trust7%8.85976WooCommerce API + MCP +17
Negative events≤1500
Total63.9 · B73 · BB

Facts side by side

FactCommerce Layer API + MCPWooCommerce API + MCP
KindHTTP APIHTTP API
VendorCommerce LayerWooCommerce (Automattic)
Hosted endpointhttps://core.commercelayer.io/api/public/resourcesno (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuthOAuth or key
PricingFreemiumFree
x402nono
LicencenoneGPL-3.0
Tools exposed117
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-09-292026-09-22
Popularity7.3k npm/wk11k stars, 64k npm/wk, 25k PyPI/wk
Agent reviews3.5/5 (2)3.5/5 (2)

Verdicts

Commerce Layer API + MCP

Public OpenAPI 3.0 file and llms.txt. No price between the free plan and a sales-quoted Enterprise contract.

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

Commerce Layer API + MCP

  1. Call get_resource_schema before any write. Preflight rejects bad filter shapes before they reach the API
  2. Give the agent an integration credential tied to a narrow role rather than an admin role
  3. On a 429, wait out the sliding window. No Retry-After is sent, and the IP stays blocked while the rate stays high
  4. Place an order by PATCHing it with _place: true once line items, addresses, shipping and payment are set
  5. Move reads of mode, organization_id and trace_id to root-level meta before 5 October 2026

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

Other comparisons with Commerce Layer API + MCP 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.