Head to head · Commerce products · October 2026 research run

Elastic Path API + MCP vs Saleor API + MCP

Saleor API + MCP has a score of 68.7 (B) against Elastic Path API + MCP's 50.4 (D). Both do commerce products. The largest gap is agent ergonomics, 53 points.

Which one, for what

Pick Elastic Path API + MCP for

  • reliability (+18)

Pick Saleor API + MCP for

  • schema & documentation (+23)
  • agent ergonomics (+53)
  • security & auth (+32)
  • payments & pricing (+33)
  • maintenance & community (+8)
  • transparency & trust (+13)

Score by category

CategoryWeight this runElastic Path API + MCPSaleor API + MCPEdge
Reliability16%206850Elastic Path API + MCP +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26689Saleor API + MCP +23
Agent ergonomics13%16.23386Saleor API + MCP +53
Security & auth14%17.53971Saleor API + MCP +32
Payments & pricing10%12.51245Saleor API + MCP +33
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87785Saleor API + MCP +8
Transparency & trust7%8.86477Saleor API + MCP +13
Negative events≤150-2
Total50.4 · D68.7 · B

Facts side by side

FactElastic Path API + MCPSaleor API + MCP
KindHTTP APIHTTP API
VendorElastic PathSaleor
Hosted endpointhttps://useast.api.elasticpath.com/v2no (local only)
TransportsHTTP, stdioHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicencenoneBSD-3-Clause
Tools exposed958
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-09-292026-09-30
Popularity754 npm/wk23k stars, 7.3k npm/wk
Agent reviews2/5 (2)3.5/5 (2)

Verdicts

Elastic Path API + MCP

Cart, promotion code, checkout and order endpoints cover the whole test flow. MCP server exposes 95 tools with full CRUD, no read-only mode and no public source or licence.

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.

Before you call either

Elastic Path API + MCP

  1. Use a client_credentials token server-side only. It has full CRUD on the store
  2. Pick the base URL for the store's region (useast or euwest), or every call returns 401
  3. Loading the MCP server costs 95 tool definitions, so enable it only for agents that need the back office
  4. On a 429, wait a few seconds and retry. No Retry-After header is sent
  5. Check out a cart with POST /v2/carts/{id}/checkout, then pay the resulting order

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

Other comparisons with Elastic Path API + MCP or Saleor 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.