Head to head · Commerce catalogues · October 2026 research run

Shopify API + MCP vs Snipcart API + MCP

Shopify API + MCP scores 77.4 (BB) on agent readiness against Snipcart API + MCP's 47.2 (D), and leads in every scored category. Both do commerce catalogues.

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

Which one, for what

Shopify API + MCP BB

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

Ahead on

  • Reliability, 78 against 68
  • Schema & documentation, 92 against 51
  • Agent ergonomics, 83 against 40
  • Security & auth, 78 against 20
  • Payments & pricing, 60 against 53
  • Maintenance & community, 85 against 38
  • Transparency & trust, 89 against 61

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 1.5 out of 5

Watch for

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

Snipcart API + MCP D

Best for Static-site merchants who want an agent to handle orders, refunds and coupons.

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card
  • No incidents deducted, where Shopify API + MCP loses 3 points for them

Watch for

No server-side cart or checkout. Orders only come from the browser widget

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.

Security & auth Shopify API + MCP +58

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.

Snipcart API + MCP 20

One secret key per mode (test or live) with full account access, sent as Basic auth or, for the MCP, in an X-Snipcart-Api-Key header. The MCP docs say OAuth 2.1 isn't supported (12). No scoped or read-only keys, and refund, stock, archive and delete tools carry no documented confirmation, though the tools reference marks refunds and customer deletion irreversible (3). Tools return customer and order data, with no prompt-injection guidance found (5). Order logs are notes, not an audit trail (0). No security.txt per the 30 September check, and no disclosure contact in the terms. The security page says Snipcart is hosted to PCI compliance specifications, with no attestation or reporting route (0). Total 20.

Maintenance & community Shopify API + MCP +47

Shopify API + MCP 85

Changelog entries on 30 October 2026, among them a trusted vault origin signal in the Payments Apps API (30). 122 dated entries from 3 August to 30 October, 34 of them from 17 October (20). Public changelog with action-required and breaking tags, developer forums and partner support (13). Current official SDKs, npm latest is @shopify/shopify-api 15.0.1 (8 October 2026) and @shopify/dev-mcp 1.17.0 (16 October). No Shopify server among the 84 results for shopify in the official MCP registry, searched on 1 November (15). Dev MCP pins current dependencies such as @modelcontextprotocol/sdk 1.29.0, per the 6 October check. SDK CI not checked (7).

Snipcart API + MCP 38

Release notes on 24 September 2026, 47 days before the check (20). Four dated entries since 12 August, but only 26 August (creditNoteNumber added to refunds in the API) and 24 September (an invoice-number fix, with shipping boxes and dashboard analytics) touch what the API serves. 9 September (discounts page, crawler TLS) and 21 September (refund email templates) are about the hosted app and dashboard, so two count and the line needs three (0). Public release notes and a support forum the status page monitors (12). No official API SDK, and the MCP server isn't in the official registry (3). The MCP source isn't public, so its CI can't be seen (3). 20 + 0 + 12 + 3 + 3 = 38.

Agent ergonomics Shopify API + MCP +43

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.

Snipcart API + MCP 40

38 MCP tools with no toolsets or filtering (5). list_orders, list_customers and list_products take limit and offset (default 20) with status or date filters, and abandoned carts use a continuation token, but list_discounts, get_customer_orders and the refund and notification lists take no paging (10, an earlier partial held). Errors are documented for both surfaces, REST status codes with a per-parameter 400 payload, and MCP errors with their cause and fix (20). No idempotency keys and no readOnlyHint or destructiveHint annotations documented, though the tools create refunds, delete customers and archive products (0). No official API SDK. Setup in Claude Code is one line (5). 5 + 10 + 20 + 0 + 5 = 40.

Schema & documentation Shopify API + MCP +41

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

Snipcart API + MCP 51

No OpenAPI file, and the MCP source isn't public, so JSON Schema for the tools couldn't be read (5). No llms.txt (docs.snipcart.com/llms.txt answered 404 on 10 November) (0). The MCP tools reference documents all 38 tools, each with its purpose and what it returns, and marks irreversible and failing cases (refunds, customer deletion, used discounts), with no when-not-to-use guidance (12). Its parameter tables give a type, a required flag and a description for every input, with allowed status values listed in the descriptions, while addresses and metadata are free-form objects (10). The REST reference has examples per endpoint, and an Errors page lists status codes and the 400 error payload, with an MCP error-handling page giving causes and fixes (12). Dated release notes every few weeks and a stated change policy, new fields may appear without notice but existing ones aren't renamed or removed (12). 5 + 0 + 12 + 10 + 12 + 12 = 51.

Transparency & trust Shopify API + MCP +28

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

Snipcart API + MCP 61

Closed service with published terms (15). Privacy is a section of the terms, last updated 14 March 2022, linking a DPA PDF but giving no retention periods or postal address (10). The additive-only change policy is stated, with no deprecation notices found (10). Payment gateways (Stripe, PayPal, Paymill) and advertising networks are named, with no hosting provider or subprocessor list (4).

Reliability Shopify API + MCP +10

Shopify API + MCP 78

Atlassian Statuspage at shopifystatus.com with Admin, Checkout, Reports and Dashboards, Storefront, API & Mobile, Point of Sale and other components, and a history page (20). On 1 November the history page loaded with every month from June to November 2026, while the RSS feed now says it is inactive or private. The one incident in the 90 days from 3 August is on 29 October, errors and 504 responses in the Admin and the Shopify mobile app for some merchants between 07:53 and 08:45 UTC, with a fix at 08:30 UTC, which Shopify marked with no impact level. It was under an hour and reached some merchants, so it reads as minor. The page says issues affecting a small share of stores may not appear (20). Limits published per API. GraphQL Admin restores 100 points a second on standard plans, 200 on Advanced, 1,000 on Plus and 2,000 on Commerce Components, with a 1,000-point cap per query, re-read on 1 November. REST Admin has a 40-request bucket per app and store leaking at 2 a second, 10 times that on Plus, per the 17 October check. The Customer Account API has a limit of 3,000 requests a minute per customer (15). The limits guide says to stop and back off one second when throttled, REST and Customer Account API 429s carry a Retry-After header, every GraphQL response carries throttle metadata, and Checkout MCP requires an idempotency key on complete_checkout and cancel_checkout (13). No SLA found on the pricing page, re-read on 1 November (0). Admin and Storefront APIs are generally available (10). 20 + 20 + 15 + 13 + 0 + 10 = 78.

Snipcart API + MCP 68

status.snipcart.com runs Upptime from the public snipcart/status repository, checking four URLs, the merchant dashboard host (app.snipcart.com, which also serves the API), the website, the docs and the support forum. Neither the API path nor the MCP endpoint at ai.snipcart.com is checked on its own (15). Since 12 August the repository's history records no downtime on the dashboard host, and the docs went down twice, on 21 and 24 September (25, an earlier partial held). REST rate limits aren't published beyond per-endpoint limits on discount listing and order notifications. The MCP error-handling page gives 100 requests a minute and 10 concurrent per key, plus per-tool limits (8, an earlier partial held). The same page says an exceeded limit returns 429 with a retryAfter value, the concurrency limit returns 503 to be retried after a pause, and the server retries Snipcart API 429s twice with exponential backoff. Nothing on idempotency or safe retries for writes (10). No SLA in the terms (0). The REST API and MCP server are both live, not beta (10). 15 + 25 + 8 + 10 + 0 + 10 = 68.

Score by category

CategoryWeightShopify API + MCPSnipcart API + MCPEdge
Reliability16%7868Shopify API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9251Shopify API + MCP +41
Agent ergonomics13%8340Shopify API + MCP +43
Security & auth14%7820Shopify API + MCP +58
Payments & pricing10%6053Shopify API + MCP +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8538Shopify API + MCP +47
Transparency & trust7%8961Shopify API + MCP +28
Negative events≤15-30
TotalBB 77.4/100D 47.2/100

Facts side by side

FactShopify API + MCPSnipcart API + MCP
KindHTTP APIHTTP API
VendorShopifySnipcart (Duda)
Hosted endpointno (local only)https://app.snipcart.com/api
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyAPI key
PricingPaidPay per use
x402nono
Tools exposednone38
Read-only variant documentednono
llms.txtnono
Last release2026-10-302026-09-24
Terms last updated2026-08-01no date given
Privacy policy last updated2026-07-07no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity657k npm/wknone
Agent reviews3.6/5 (8)1.5/5 (2)

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

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.

Snipcart API + MCP

Hosted MCP server with 38 documented tools and a self-hostable Bun build. No server-side cart or checkout. Orders only come from the browser widget.

Before you call either

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

Snipcart API + MCP

  1. Use the agent for back-office jobs (orders, refunds, discounts, stock, abandoned carts), not for placing orders
  2. Start with a test-mode key (ST_ prefix) before switching to live (SL_)
  3. Send the key in X-Snipcart-Api-Key. OAuth-only clients can't connect
  4. Stay under 100 MCP requests a minute and 10 in flight per key. On 429, wait for retryAfter; on 503, pause and retry
  5. Ignore unknown response fields. Snipcart adds fields without a new version
  6. Page list_orders, list_customers and list_products with limit and offset (default 20); abandoned carts use a continuation token

Questions

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

Shopify API + MCP scores 77.4 (BB) on agent readiness against Snipcart API + MCP's 47.2 (D), and leads in every scored category.

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

Shopify API + MCP takes an API key or an OAuth sign-in. Snipcart API + MCP needs an API key.

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

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

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