Head to head · Commerce catalogues · October 2026 research run

BigCommerce API + MCP vs Saleor API + MCP

Saleor API + MCP scores 76.5 (BB) on agent readiness against BigCommerce API + MCP's 69.9 (B), and leads in 5 of 7 scored categories. Both do commerce catalogues.

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

Which one, for what

BigCommerce API + MCP B

Best for Agents working with existing BigCommerce stores, for back-office automation through REST or guest shopping through the MCP.

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

The storefront MCP has no back-office tools and documents no tool annotations; back-office tools are only in an invite-only closed beta

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 66
  • Agent ergonomics, 86 against 62
  • Payments & pricing, 68 against 60

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

The MCP server can't create checkouts or orders

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.

Agent ergonomics Saleor API + MCP +24

BigCommerce API + MCP 62

The B2C storefront MCP reference lists 7 compact, shopping-only tools, and search_products pages with a cursor (23). REST listings take page and limit, with filters such as id:in, type and severity on the store logs endpoint, and the GraphQL Storefront API documents pagination (16). 429 handling is documented, but we found no error-format reference in the docs index (10). No idempotency keys, and the MCP reference documents no tool annotations (0). Guest MCP needs no key. Official API clients for Python, PHP, Ruby and Node, three updated in 2026 and the Python client last in January 2024 (13).

Saleor API + MCP 86

GraphQL field selection sizes every response, and the MCP server has 8 compact tools (25). Cursor pagination capped at 100, with filter, where, search and sort inputs (20). Mutations return typed errors with a code, field and message (18). Payment transaction mutations take an idempotencyKey, and 7 of the 8 MCP tools declare readOnlyHint and idempotentHint (the eighth only returns the API URL) (15). MCP tools default to 100 items and need only a channel. The official SDK is a TypeScript app SDK, with no general client in a second language (8).

Schema & documentation Saleor API + MCP +23

BigCommerce API + MCP 66

Reference pages are built from API specs (a 29 September changelog entry corrected twenty of them), but the public spec repo was archived in December 2023 and its successor, bigcommerce/docs, still asked git for credentials on 2 October, so no current spec file was found (10). llms.txt hub linking a developer index of about 500 Markdown pages, plus a docs MCP server (10). Reference descriptions say what each call does, and the MCP tools are guest shopping steps (12). Typed REST parameters in the reference (11). Examples in the reference, but the developer index has no page on error responses (10). Dated changelog with entries almost daily, v2 and v3 REST paths, and a Deprecations and Sunsets page, though it gives no notice period (13).

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

Payments & pricing Saleor API + MCP +8

BigCommerce API + MCP 60

No x402, MPP or L402 (0). Plan prices public, Core $39, Growth $105 and Scale $399 a month with GMV caps and 2.0, 1.0 and 0.6 per cent on orders through non-embedded providers, but nothing per call (10). 15-day free trial, and the pricing page says no credit card is needed (20). An agent can shop any store that has switched on the MCP as a guest with no key, but back-office access needs a person to create an API account (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

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.

Score by category

CategoryWeightBigCommerce API + MCPSaleor API + MCPEdge
Reliability16%7775BigCommerce API + MCP +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6689Saleor API + MCP +23
Agent ergonomics13%6286Saleor API + MCP +24
Security & auth14%7071Saleor API + MCP +1
Payments & pricing10%6068Saleor API + MCP +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8285Saleor API + MCP +3
Transparency & trust7%7776BigCommerce API + MCP +1
Negative events≤150-2
TotalB 69.9/100BB 76.5/100

Facts side by side

FactBigCommerce API + MCPSaleor API + MCP
KindHTTP APIHTTP API
VendorBigCommerce (Commerce.com)Saleor
Hosted endpointhttps://api.bigcommerce.comno (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicencenoneBSD-3-Clause
Tools exposed78
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-302026-10-28
Terms last updated2026-06-01no date given
Privacy policy last updated2026-01-28no 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 benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone23k stars, 7.3k npm/wk
Agent reviews3/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Saleor API + MCP higher.

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

BigCommerce API + MCP

Rate limits are published per plan, and every 429 carries X-Rate-Limit-Time-Reset-Ms. Status incidents since August were partial. The storefront MCP lets a guest agent shop with no key but documents no tool annotations, back-office MCP tools are in an invite-only beta, and REST tokens never expire.

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

BigCommerce API + MCP

  1. Give the agent a store-level API account with only the scopes the task needs, and delete it when done
  2. On a 429, wait X-Rate-Limit-Time-Reset-Ms before retrying
  3. Expect up to 10 minutes after a store owner enables the MCP before the URL answers
  4. The MCP stops at a checkout URL. Payment happens in the shopper's browser
  5. Point a coding agent at the docs MCP at https://docs.bigcommerce.com/_mcp/server
  6. Store Management MCP is invite-only; if granted, call get_refund_quote and confirm with a person before create_refund, which the docs say is never safe to retry

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

Questions

Which is better for AI agents, BigCommerce API + MCP or Saleor API + MCP?

Saleor API + MCP scores 76.5 (BB) on agent readiness against BigCommerce API + MCP's 69.9 (B), and leads in 5 of 7 scored categories.

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

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

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

BigCommerce API + MCP has a hosted endpoint at https://api.bigcommerce.com. No hosted endpoint is listed for Saleor API + MCP.

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

No open-source release is listed for BigCommerce API + MCP. Saleor API + MCP is open source (BSD-3-Clause).

Other comparisons with BigCommerce 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.