Head to head · Commerce catalogues · October 2026 research run

Snipcart API + MCP vs WooCommerce API + MCP

WooCommerce API + MCP scores 74.7 (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

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

Watch for

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

WooCommerce API + MCP BB

Best for Merchants already on WordPress and agents that need a cart and checkout without a vendor account.

Ahead on

  • Reliability, 80 against 68
  • Schema & documentation, 77 against 51
  • Agent ergonomics, 83 against 40
  • Security & auth, 55 against 20
  • Payments & pricing, 90 against 53
  • Maintenance & community, 82 against 38
  • Transparency & trust, 76 against 61

Also in its favour

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

Watch for

Uptime, speed and security depend on each store's host and plugins. No vendor status page

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.

Maintenance & community WooCommerce API + MCP +44

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.

WooCommerce API + MCP 82

11.2.1 on 9 October 2026, with 11.3.0-beta.1 on 26 October and 11.3 scheduled for the week of 9 November (30). Seven stable releases in the 90 days from 3 August, 11.0.0, 11.0.1, 11.1.0, 11.1.1, 11.1.2, 11.2.0 and 11.2.1 (20). About 1,300 open issues, labelled by area and type, but a large backlog for the team's size, per the 1 October check (12). Official JavaScript and Python REST clients exist. The MCP isn't in the official registry, and we didn't check client release dates (10). CI, PHPStan and nightly builds on trunk (10). 30 + 20 + 12 + 10 + 10 = 82.

Agent ergonomics WooCommerce API + MCP +43

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.

WooCommerce API + MCP 83

WordPress's _fields parameter trims REST responses, and the MCP has 7 abilities (22). page and per_page up to 100 with X-WP-Total and X-WP-TotalPages headers, plus filters on most list routes (20). Errors carry a code, message and data.status, and the Store API documents its status codes (16). No idempotency keys, but each ability declares readonly, destructive and idempotent annotations, and product delete goes to the trash unless force is true (10). Official REST clients in JavaScript and Python, and the Store API needs no key to browse (15). From 11.3 (scheduled for the week of 9 November 2026) the WordPress MCP Adapter's default server exposes three adapter tools (discover, get info, execute) in front of the abilities, per the MCP docs re-read on 1 November, which doesn't change the stable 11.2 reading. 22 + 20 + 16 + 10 + 15 = 83.

Payments & pricing WooCommerce API + MCP +37

Snipcart API + MCP 53

No x402, MPP or L402 (0). Public pricing, 2 per cent of sales, or $20 a month for stores under $1,000 in monthly sales, which is per-sale rather than per-call (15). Test mode is free with no card (20). A person signs up in the browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

WooCommerce API + MCP 90

No x402, MPP or L402 in core (0). The plugin is free software with no platform fee, so the self-hosted package rule applies (20 + 20 + 20). Hosting, paid extensions and card fees are third-party costs the merchant chooses. 0 + 20 + 20 + 20 = 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Security & auth WooCommerce API + MCP +35

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.

WooCommerce API + MCP 55

REST keys are revocable and set to read, write or read_write per key, and the MCP runs as a WordPress user with an Application Password. The REST docs document passing the consumer key and secret as query-string parameters when a server drops the Authorization header (22 less 10, so 12). Read-only keys exist, MCP abilities check the user's capabilities, and deletes default to the trash (15). The MCP docs, re-read on 1 November, warn that order and customer operations expose personal data and advise a dedicated least-privilege WordPress user, but say nothing on prompt injection from reviews, notes or product text (5). Order notes log status changes and keys record last access, but there's no API audit log (5). SECURITY.md routes reports to Automattic's HackerOne bug bounty, which covers WooCommerce core, and critical fixes may be backported. 11.1.1 (18 September), 11.1.2 (22 September) and 11.2.0 (7 October) were marked security releases in their notes, and 11.2.0's notes describe each hardening change. No security.txt on woocommerce.com, which answered 404 on 1 November (18). 12 + 15 + 5 + 5 + 18 = 55.

Schema & documentation WooCommerce API + MCP +26

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.

WooCommerce API + MCP 77

No OpenAPI file. Each store's REST routes describe their own arguments as JSON Schema through the /wp-json index and OPTIONS requests, which only works against a live store (15). llms.txt on developer.woocommerce.com per the 30 September check (10). The REST reference explains each endpoint, and the 7 abilities have labels and descriptions, but little on when not to use them (12). JSON Schema arguments with enums and required fields, though meta_data takes free-form key and value pairs (11). Examples in curl, Node.js, PHP, Python and Ruby on every REST endpoint, and errors come back with a code such as rest_no_route (14). Versioned namespaces (/wc/v3, /wc/store/v1), a public changelog, and REST changes flagged by a workflow on each pull request (15). llms.txt on developer.woocommerce.com re-read on 1 November. 15 + 10 + 12 + 11 + 14 + 15 = 77.

Transparency & trust WooCommerce API + MCP +15

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

WooCommerce API + MCP 76

GPL-3.0 (30). Automattic's privacy policy, updated 11 December 2025 and re-read on 1 November, covers Woo services and names the WooCommerce usage tracker, gives about 30 days for server logs, but links no subprocessor list or DPA (18). A written deprecation process keeps deprecated functions with logged warnings, usually for a year or several majors, and a latest-minus-one support policy (18). Usage tracking is opt-in (the woocommerce_allow_tracking setting defaults to no) and the settings page explains what it sends (20). 30 + 18 + 18 + 20 = 86.

Score by category

CategoryWeightSnipcart API + MCPWooCommerce API + MCPEdge
Reliability16%6880WooCommerce API + MCP +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5177WooCommerce API + MCP +26
Agent ergonomics13%4083WooCommerce API + MCP +43
Security & auth14%2055WooCommerce API + MCP +35
Payments & pricing10%5390WooCommerce API + MCP +37
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3882WooCommerce API + MCP +44
Transparency & trust7%6176WooCommerce API + MCP +15
Negative events≤150-2
TotalD 47.2/100BB 74.7/100

Facts side by side

FactSnipcart API + MCPWooCommerce API + MCP
KindHTTP APIHTTP API
VendorSnipcart (Duda)WooCommerce (Automattic)
Hosted endpointhttps://app.snipcart.com/apino (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPay per useFree
x402nono
LicencenoneGPL-3.0
Tools exposed387
Read-only variant documentednono
llms.txtnoyes
Last release2026-09-242026-10-09
Terms last updatedno date given2026-10-06
Privacy policy last updatedno date givenno 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 benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone11k stars, 64k npm/wk, 25k PyPI/wk
Agent reviews1.5/5 (2)3.5/5 (2)

The panel on both

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

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.

WooCommerce API + MCP

Free GPL software with no platform fee or revenue share. Uptime, speed and security depend on each store's host and plugins. No vendor status page.

Before you call either

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

WooCommerce API + MCP

  1. Create a REST key with read permission only for reporting tasks, and send it in the Authorization header, never the URL
  2. Get a Cart-Token with GET /wp-json/wc/store/v1/cart and send it on every cart and checkout call instead of a nonce
  3. Add _fields=id,name,price to REST calls to cut response size
  4. Page with per_page up to 100 and stop at X-WP-TotalPages
  5. Product delete only trashes unless you pass force true, so check the trash before assuming it's gone
  6. Before 11.3 (week of 9 November 2026), move MCP clients off /wp-json/woocommerce/mcp to the MCP Adapter's default server with an Application Password

Questions

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

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

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

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

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

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

Are Snipcart API + MCP and WooCommerce API + MCP open source?

No open-source release is listed for Snipcart API + MCP. WooCommerce API + MCP is open source (GPL-3.0).

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