Head to head · Commerce catalogues · October 2026 research run

BigCommerce API + MCP vs Shopify API + MCP

Shopify API + MCP scores 77.4 (BB) on agent readiness against BigCommerce API + MCP's 69.9 (B), and leads in 6 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
  • No incidents deducted, where Shopify API + MCP loses 3 points for them

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

Shopify API + MCP BB

Best for Agents that shop on real stores or automate a merchant's back office at scale.

Ahead on

  • Schema & documentation, 92 against 66
  • Agent ergonomics, 83 against 62
  • Security & auth, 78 against 70
  • Transparency & trust, 89 against 77

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.6 against 3.0 out of 5

Watch for

Closed platform. You can't self-host or change checkout internals

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.

Schema & documentation Shopify API + MCP +26

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

Shopify API + MCP 92

Fully typed GraphQL Admin and Storefront schemas with introspection, and UCP tools defined by published JSON schemas (25). shopify.dev/llms.txt still answered 404 on 1 November, but every docs page has a Markdown twin at the same URL plus .md, served as text/markdown (10). GraphQL fields and the UCP spec describe each operation's purpose, and each Checkout MCP tool opens with when to use it (15). Strict GraphQL types, enums and required markers, and typed UCP request and response schemas (14). Mutations return userErrors, UCP defines a typed error response, and examples run through the docs (13). Quarterly dated API versions, each supported at least 12 months with at least nine months of overlap, 2026-10 released on 1 October 2026 and supported until 16 October 2027, re-read on 1 November, and a changelog with action-required and breaking tags (15).

Agent ergonomics Shopify API + MCP +21

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

Shopify API + MCP 83

GraphQL field selection sizes every Admin and Storefront response. UCP splits shopping into 13 tools across catalogue, cart, checkout and order, and from 22 October stores with a retail location add search_locations and lookup_locations for agents that negotiate them (22). Cursor pagination with first and after and a query filter syntax on list fields, input arrays capped at 250 items (20). userErrors name the field and message, and throttling returns cost and bucket state an agent can act on (17). Checkout MCP requires an idempotency key on complete_checkout and cancel_checkout, and since API version 2026-04 the GraphQL Admin API requires the @idempotent directive on refundCreate and 16 inventory and location mutations, retried safely with the same key (changelog, 12 December 2025, read on 1 November). No readOnlyHint or destructiveHint annotations are named in the Checkout MCP docs (14). Official libraries are JavaScript packages in this listing. Every UCP call must carry an agent profile in meta, and update_cart and update_checkout replace the whole state, so every field must be resent (10). 22 + 20 + 17 + 14 + 10 = 83.

Transparency & trust Shopify API + MCP +12

BigCommerce API + MCP 77

Closed platform with published terms, now on commerce.com, and an open-source Catalyst storefront (15). The trust centre lists a DPA and a subprocessor document. The commerce.com privacy policy wasn't read in either pass (22). A Deprecations and Sunsets page lists deprecated v2 endpoints and three dated sunsets, the last on 3 June 2024, but the current deprecations carry no sunset dates and no notice period is stated (10). Subprocessor document listed and Google Cloud named as the host (18).

Shopify API + MCP 89

Closed platform with published terms, and open-source client libraries (15). Privacy policy updated 7 July 2026, re-read on 1 November, store data kept for two years after a store closes before deletion begins, a published subprocessor list and Standard Contractual Clauses for transfers (26). Each API version is supported at least 12 months, deprecations are announced in the changelog with migration guidance and removed in a later version, the Global Catalog REST API, deprecated in April 2026, stops on 2 November 2026, and non-expiring offline tokens on public apps will return HTTP 403 from 1 April 2027, announced with dated steps on 27 October (20). Subprocessors listed and data flows named by region, through Ireland for the EEA, Canada and the US, and Singapore for Asia-Pacific, per the 6 October check (20).

Security & auth Shopify API + MCP +8

BigCommerce API + MCP 70

API accounts issue a token limited by OAuth scopes chosen at creation and revocable by deleting the account, but tokens never expire and can't be rotated in place (24). Read-only scope variants, and the storefront MCP has no back-office tools, so a guest agent can only shop. The invite-only Store Management MCP beta adds OAuth 2.1 with PKCE, per-scope grants that start at none, products and promotions created hidden or disabled, and refunds only after a quote, but it isn't generally available, so it moves no line (16). The MCP returns merchant product content with no prompt-injection guidance found (5). The store logs API (GET /v3/store/systemlogs) keeps storefront events such as order status changes for 365 days, and the control panel keeps staff action logs (a status incident on 8 July names them). No per-call API log found (8). Trust centre lists PCI DSS Level 1 as merchant and service provider, SOC 1, SOC 2 and SOC 3, ISO/IEC 27001:2022 with 27017, 27018 and 27701, and a vulnerability disclosure programme run through Inspectiv. No security.txt (404 on 2 November) (17).

Shopify API + MCP 78

Per-app access tokens limited by granular read and write scopes, OAuth for public apps, separate storefront tokens, and token exchange for offline tokens. Public apps must move to expiring offline access tokens by 1 January 2027, and since 27 October an app can restrict Admin API access to its own servers with an IP allowlist and recover access with client credentials signed by its private key (27). Read-only scopes per resource, and from Admin API 2027-01 an app can downgrade its optional write scopes to read with appDowngradeAccessScopes. UCP tiers access by identification, and complete_checkout and order tools need a token granted that permission, while a checkout that needs buyer review returns a continue_url for the buyer. The Dev MCP server only reads docs and schemas (16). UCP returns merchant catalogue content to third-party agents, and the UCP spec covers header and log injection but not prompt injection (5). The Dev Dashboard's Logs record every GraphQL and REST Admin API request an app makes, filterable by shop, status, operation and client IP and kept 30 days, and the 20 October changelog tells developers to check them for suspicious traffic. Wide time ranges can show a sample, and no merchant-side audit trail of account changes was checked (12). security.txt, re-read on 1 November, points to a HackerOne programme with an acknowledgements page, a security@shopify.com contact and a PGP key, but still has no Expires field. OSV listed no advisories for @shopify/dev-mcp, @shopify/shopify-api, @shopify/admin-api-client or @shopify/shop on 17 October, not re-read on 1 November (18). 27 + 16 + 5 + 12 + 18 = 78.

Score by category

CategoryWeightBigCommerce API + MCPShopify API + MCPEdge
Reliability16%7778Shopify API + MCP +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6692Shopify API + MCP +26
Agent ergonomics13%6283Shopify API + MCP +21
Security & auth14%7078Shopify API + MCP +8
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8285Shopify API + MCP +3
Transparency & trust7%7789Shopify API + MCP +12
Negative events≤150-3
TotalB 69.9/100BB 77.4/100

Facts side by side

FactBigCommerce API + MCPShopify API + MCP
KindHTTP APIHTTP API
VendorBigCommerce (Commerce.com)Shopify
Hosted endpointhttps://api.bigcommerce.comno (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
Tools exposed7none
Read-only variant documentednono
llms.txtyesno
Last release2026-10-302026-10-30
Terms last updated2026-06-012026-08-01
Privacy policy last updated2026-01-282026-07-07
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesnot found in the text
Popularitynone657k npm/wk
Agent reviews3/5 (2)3.6/5 (8)

The panel on both

2 of the 2 reviewers who reviewed both rate Shopify 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.

Shopify API + MCP

Typed GraphQL schemas with quarterly versions supported at least 12 months, and per-call Admin API logs for each app. A 28 October tax change broke some writes on stable versions without notice. Closed platform, so you can't self-host or change checkout internals.

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

Shopify API + MCP

  1. Pin an API version in the URL and plan to move at least once a year. Old versions fall forward to the oldest supported one
  2. Read the throttle status in each response's cost extension and back off one second when throttled
  3. Send an agent profile in meta on every UCP call, and an idempotency key on complete_checkout and cancel_checkout
  4. Resend every field on update_cart and update_checkout. Each call replaces the whole state
  5. Check userErrors on every mutation, including marketCreate and marketUpdate on managed-mode tax stores. A 200 response can still carry a failed write
  6. Add the @idempotent directive to refundCreate and inventory mutations from API version 2026-04, or they fail at runtime

Questions

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

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

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

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

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

BigCommerce API + MCP has a hosted endpoint at https://api.bigcommerce.com. Shopify API + MCP runs on your own machine, with no hosted endpoint listed.

Other comparisons with BigCommerce API + MCP or Shopify 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.