Commerce Layer API + MCP vs Saleor API + MCP

Commerce Layer API + MCP

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

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.

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

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