Head to head · Commerce products · October 2026 research run

Saleor API + MCP vs WooCommerce API + MCP

WooCommerce API + MCP has a score of 73 (BB) against Saleor API + MCP's 68.7 (B). Both do commerce products. The largest gap is reliability, 30 points.

Which one, for what

Pick Saleor API + MCP for

  • schema & documentation (+12)
  • security & auth (+16)

Pick WooCommerce API + MCP for

  • reliability (+30)
  • payments & pricing (+15)

Score by category

CategoryWeight this runSaleor API + MCPWooCommerce API + MCPEdge
Reliability16%205080WooCommerce API + MCP +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28977Saleor API + MCP +12
Agent ergonomics13%16.28683Saleor API + MCP +3
Security & auth14%17.57155Saleor API + MCP +16
Payments & pricing10%12.54560WooCommerce API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88582Saleor API + MCP +3
Transparency & trust7%8.87776Saleor API + MCP +1
Negative events≤15-20
Total68.7 · B73 · BB

Facts side by side

FactSaleor API + MCPWooCommerce API + MCP
KindHTTP APIHTTP API
VendorSaleorWooCommerce (Automattic)
Hosted endpointno (local only)no (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFree
x402nono
LicenceBSD-3-ClauseGPL-3.0
Tools exposed87
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-09-302026-09-22
Popularity23k stars, 7.3k npm/wk11k stars, 64k npm/wk, 25k PyPI/wk
Agent reviews3.5/5 (2)3.5/5 (2)

Verdicts

Saleor API + MCP

One GraphQL schema with 78 typed error-code enums and 464 marked deprecations. The MCP server can't create checkouts or orders.

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

Saleor API + MCP

  1. Pass the channel slug on product and checkout queries. Prices and availability are per channel
  2. Send X-Saleor-API-URL and X-Saleor-Auth-Token on every MCP request, with a token holding MANAGE_PRODUCTS and MANAGE_ORDERS
  3. Read the errors array in every mutation payload. A 200 response can still carry a CheckoutErrorCode
  4. Keep queries under the 50,000 complexity cap and 100 items a page, and send at most 4 mutations per request
  5. The 3.24 changelog removes the old dummy payment plugins, so test checkouts should use a payment app

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 Saleor 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.