Head to head · Commerce catalogues · October 2026 research run

Saleor API + MCP vs WooCommerce API + MCP

Saleor API + MCP scores 76.5 (BB) on agent readiness against WooCommerce API + MCP's 74.7 (BB), and leads in 4 of 7 scored categories. WooCommerce API + MCP leads on reliability and payments & pricing. Both do commerce catalogues.

Best commerce platforms and checkout APIs for AI agents · All 189 commerce comparisons

Which one, for what

Saleor API + MCP BB

Best for Teams that want an open-source GraphQL backend with multi-channel pricing and an agent that reads store data safely.

Ahead on

  • Schema & documentation, 89 against 77
  • Security & auth, 71 against 55

Watch for

The MCP server can't create checkouts or orders

WooCommerce API + MCP BB

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

Ahead on

  • Reliability, 80 against 75
  • Payments & pricing, 90 against 68

Also in its favour

  • Runs on your own machine

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 +22

Saleor API + MCP 68

No x402, MPP or L402 (0). Cloud plans are public, Select $1,599 a month to $200,000 GMV and Volume $3,999 to $1,000,000, with 0.8% and 0.4% overage, but there's no per-call or per-unit price (10). The BSD core is free to self-host, and Cloud sandboxes are free for non-commercial use with no card mentioned (20). An agent can run the core from the Docker image with no account, but Cloud needs a browser signup (15). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 45 is 68.

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 Saleor API + MCP +16

Saleor API + MCP 71

App tokens limited to named permissions such as MANAGE_PRODUCTS and MANAGE_ORDERS, revocable through the API, and short-lived staff JWTs with refresh. Tokens travel in headers, never the URL (27). The MCP server never runs mutations, and a self-run copy can pin allowed API domains with ALLOWED_DOMAIN_PATTERN (16). Tools return merchant- and shopper-entered text, marked openWorldHint, with no prompt-injection guidance found (5). Observability webhooks can report API calls, but no operator audit log of who did what was found (8). SECURITY.md routes reports through GitHub advisories or security@saleor.io, nine advisories were published between January and July 2026, and the pricing page lists SOC 2, PCI DSS and GDPR. No security.txt and no bounty (15).

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 Saleor API + MCP +12

Saleor API + MCP 89

One GraphQL schema with introspection, and a 954 KB SDL copy in the MCP repo (25). llms.txt split into per-section indexes (10). Fields and mutations carry descriptions, doc categories and deprecation reasons, but rarely say when not to use them (13). Strict GraphQL types with 78 error-code enums and required markers (14). Typed error codes on every mutation payload, with examples in the docs (12). CHANGELOG with a breaking changes section per minor version, GitHub releases, and 464 @deprecated markers in the schema (15).

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.

Reliability WooCommerce API + MCP +5

Saleor API + MCP 75

Graded on Saleor Cloud. Status page at status.saleor.io with an incident feed and history (20). One incident in the 90 days to 1 November, elevated GraphQL error rates, mostly 503s, for some EU stores from 18:01 to 18:23 UTC on 25 October, caused by an OIDC bug fixed in 3.23.45. Partial and 22 minutes, so minor (20). The usage limits page gives sandboxes 120 requests a minute on the free plan and 2,000 on paid plans, with production unlimited, plus a 50,000 query-cost cap, 100 items a page and 4 mutations per request (15). Requests over the limit get HTTP 429, and since 30 October the page says throttled production traffic also gets 429 and should be retried with backoff. Payment transaction mutations take an idempotencyKey, other writes don't, and no Retry-After is documented (10). No SLA on the pricing page (0). Generally available (10).

WooCommerce API + MCP 80

Graded with the self-hosted package checklist, since every store runs on its owner's WordPress host and Woo runs no hosted API. Official plugin on wordpress.org, requiring PHP 7.4 and WordPress 7.0, per the 11.2.1 readme re-read on 1 November (20). CI workflow on trunk, the latest 30 runs all green, per the 1 October check, not re-read on 1 November (25). About 1,300 open issues, with recent bugs such as an 11.1.0 release candidate showing $0 flat-rate shipping as "Free!" in emails (fixed in 11.2.0) and a database connection bug, per the 1 October check (10). Monthly major.minor releases rather than strict semver, with workflows that flag REST API and backwards-compatibility changes for review and pre-release notes about two weeks before each minor (10). Stable 11.x (15). The Store API's optional limiter documents RateLimit headers including RateLimit-Retry-After, and since 11.2.0 answers 429 rather than 400 when the limit is exceeded. 20 + 25 + 10 + 10 + 15 = 80.

Score by category

CategoryWeightSaleor API + MCPWooCommerce API + MCPEdge
Reliability16%7580WooCommerce API + MCP +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8977Saleor API + MCP +12
Agent ergonomics13%8683Saleor API + MCP +3
Security & auth14%7155Saleor API + MCP +16
Payments & pricing10%6890WooCommerce API + MCP +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8582Saleor API + MCP +3
Transparency & trust7%7676even
Negative events≤15-2-2
TotalBB 76.5/100BB 74.7/100

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
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-10-282026-10-09
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 benchmarkingnot found in the textnot 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
Popularity23k stars, 7.3k npm/wk11k stars, 64k npm/wk, 25k PyPI/wk
Agent reviews3.5/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

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

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
  6. On a sandbox stay under 120 requests a minute (2,000 on paid plans), and retry an HTTP 429 with backoff

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
  6. 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, Saleor API + MCP or WooCommerce API + MCP?

Saleor API + MCP scores 76.5 (BB) on agent readiness against WooCommerce API + MCP's 74.7 (BB), and leads in 4 of 7 scored categories. WooCommerce API + MCP leads on reliability and payments & pricing.

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

Both take an API key or an OAuth sign-in.

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

No hosted endpoint is listed for Saleor API + MCP. WooCommerce API + MCP runs on your own machine, with no hosted endpoint listed.

Are Saleor API + MCP and WooCommerce API + MCP open source?

Yes. Saleor API + MCP is open source (BSD-3-Clause). WooCommerce API + MCP is open source (GPL-3.0).

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.