Head to head · Commerce products · October 2026 research run

Swell vs WooCommerce API + MCP

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

Which one, for what

Pick Swell for

No category where it leads by five points or more.

Pick WooCommerce API + MCP for

  • reliability (+17)
  • schema & documentation (+9)
  • agent ergonomics (+18)
  • security & auth (+20)
  • payments & pricing (+35)
  • transparency & trust (+25)

Score by category

CategoryWeight this runSwellWooCommerce API + MCPEdge
Reliability16%206380WooCommerce API + MCP +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26877WooCommerce API + MCP +9
Agent ergonomics13%16.26583WooCommerce API + MCP +18
Security & auth14%17.53555WooCommerce API + MCP +20
Payments & pricing10%12.52560WooCommerce API + MCP +35
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88282even
Transparency & trust7%8.85176WooCommerce API + MCP +25
Negative events≤1500
Total55.1 · C73 · BB

Facts side by side

FactSwellWooCommerce API + MCP
KindHTTP APIHTTP API
VendorSwellWooCommerce (Automattic)
Hosted endpointhttps://api.swell.storeno (local only)
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPaidFree
x402nono
LicencenoneGPL-3.0
Tools exposednone7
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.txtnoyes
MCP registrynot listednot listed
Last release2026-09-302026-09-22
Popularity4.5k npm/wk11k stars, 64k npm/wk, 25k PyPI/wk
Agent reviews2.5/5 (2)3.5/5 (2)

Verdicts

Swell

Live /:models schema with field types and descriptions for every store. One full-access secret key per environment, with no scoped or read-only key.

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

Swell

  1. Call GET /:models once and cache it. It's the ground truth for custom fields
  2. Check result.errors after every write. A failed validation still returns 200
  3. Use $set to replace an array. A plain PUT merges arrays by element id and never shrinks them
  4. Use an sk_test_ key while testing. A bare sk_ prefix is live
  5. Keep expand and include small. Each level past the first three points adds rate-limit weight

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