Head to head · Commerce catalogues · October 2026 research run

BigCommerce API + MCP vs Medusa API + MCP

BigCommerce API + MCP scores 69.9 (B) on agent readiness against Medusa API + MCP's 60.3 (C), and leads in 3 of 7 scored categories. Medusa API + MCP leads on schema & documentation, agent ergonomics, payments & pricing and maintenance & community. 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.

Ahead on

  • Reliability, 77 against 55
  • Security & auth, 70 against 49
  • Transparency & trust, 77 against 72

Also in its favour

  • A hosted endpoint, with nothing to install
  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
  • No incidents deducted, where Medusa API + MCP loses 8 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

Medusa API + MCP C

Best for Teams that want to own a TypeScript commerce backend and extend it with their own routes and workflows, and for Cloud merchants who want an assistant to answer questions over store data.

Ahead on

  • Schema & documentation, 81 against 66
  • Agent ergonomics, 72 against 62
  • Payments & pricing, 75 against 60
  • Maintenance & community, 93 against 82

Also in its favour

  • Open source

Watch for

The MCP server can't write and serves only Cloud stores on v2.12.4 or later, rebuilt on or after 8 October 2026

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.

Reliability BigCommerce API + MCP +22

BigCommerce API + MCP 77

Atlassian Statuspage at status.bigcommerce.com with API & Webhooks, Checkout & Payment Processing, Storefront and B2B components, a history page and an Atom feed (20). Read on 2 November, the history holds 36 incidents from 4 August, 8 in August, 8 in September and 20 in October. Seven carry a major or critical label, each partial by its own text. Microsoft single sign-on failed for a subset of stores for 29 minutes (25 August), Modern Import/Export catalogue export failed for 65 minutes (14 September), the Contact Center phone system was down (16 September, not the platform), category pages showed inaccurate stock (23 September), QuickBooks Payments stores couldn't take payments for 3 hours 39 minutes (5 October, one provider), some Chrome on Android shoppers on headless storefronts couldn't reach checkout (26 October), and Bolt payments failed for 2 hours 12 minutes after Bolt changed its domain (27 October, one provider). Search returned HTTP 500s across the platform for 66 minutes on 27 October, search only, and Management API add-to-cart requests failed for 59 minutes on 12 October. The 10 July availability major left the window on 8 October, so with only partial incidents the line is 20 (was 10, cause time). Published limits, 450 requests per 30 seconds on Scale and 150 on Growth and Core, refreshed every 30 seconds (15). A 429 carries X-Rate-Limit-Time-Reset-Ms and the docs advise waiting that long, then backing off exponentially. No idempotency keys for writes found (12). No SLA found (0). REST APIs are generally available, and the storefront MCP pages no longer carry a beta label, with the server switched on from the standard Settings, API and MCP page. The invite-only Store Management MCP beta isn't graded (10).

Medusa API + MCP 55

Graded on Medusa Cloud, the hosted option, by the hosted lines. Atlassian Statuspage at status.medusajs.com with an incident feed (20). Five incidents in the 90 days from 4 August, all partial and short. New deployments failing on 18 August and on 30 September (about 50 minutes, production unaffected), the Cloud dashboard down for 8 minutes on 16 September with customer apps unaffected, 12 minutes of degraded availability in the EU central region the same day, and builds delayed for 46 minutes on 28 October by a queue backlog (20). No API rate limits published, only monthly edge-request quotas per plan (0). No 429 or backoff guidance found (0). A 99.99% uptime guarantee is listed for Enterprise on the pricing page, with no SLA document published (5). Generally available (10). Self-hosted stores have no vendor status at all. 20+20+0+0+5+10 = 55.

Security & auth BigCommerce API + MCP +21

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

Medusa API + MCP 49

Publishable keys scoped to sales channels for the Store API, revocable secret API keys or user JWTs for the Admin API. A secret key has full admin reach. The Cloud MCP server uses OAuth 2.1 with PKCE and rotating refresh tokens that expire after seven days, but its only scopes are openid, email and profile (20). Publishable keys limit what a shopping agent sees, and role-based access is behind an opt-in flag per the 2.20.1 notes. The Medusa MCP server launched in October is read-only (the ten Cloud tools added on 20 October return secret environment variable keys but never their values), the person picks which environments it can reach on the consent page, connections can be narrowed or revoked from the Connections page, and stores with MFA ask the person to confirm before a tool reads store data (14, up from 8). The API and the MCP return merchant- and shopper-entered text with no prompt-injection guidance found (5). The pricing page lists Audit Logs on Enterprise only, with no documentation found, and the Connections page (5 October) shows when each MCP connection was last used (3, up from 0). SECURITY.md with security@medusajs.com and a 3-business-day response promise, but no security.txt on medusajs.com, docs.medusajs.com or cloud.medusajs.com, no bounty, no SOC 2 found outside the Enterprise plan list, and no Medusa-published advisories (OSV holds none for @medusajs packages beyond the malware record) even though releases since September fixed several described flaws, among them MFA routes accepting an incomplete challenge (2.20.0) and field filters not stripping disallowed fields (2.20.1) (7). 20+14+5+3+7 = 49.

Schema & documentation Medusa API + MCP +15

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

Medusa API + MCP 81

OpenAPI 3.0 files for the Store API (68 paths, 78 operations at 2.21.2) and the Admin API live in the repo, with a frozen copy per release (25). llms.txt with about 200 entries (10). Reference descriptions state what each route does but rarely when not to use it (12). Typed query and body parameters with required fields, though fields takes a free-form expression and filters accept $and and $or (11). Error responses are documented per route (400, 401, 404, 409, 422, 500) with typed error objects, and the reference carries JS SDK and curl examples (13). Release notes have a breaking changes section, but breaking changes ship in minor 2.x releases, with breaking sections in 2.16.0, 2.17.0, 2.18.0, 2.19.0 and 2.20.0 and even the 2.17.2 patch (10).

Payments & pricing Medusa API + MCP +15

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.

Medusa API + MCP 75

No x402, MPP or L402 (0). Medusa Cloud plan prices start from $29, $99 and $299 a month with per-unit overage ($0.30 per 1M edge requests, $20 per 100,000 search requests), all public, but each plan is a floor price (15). The MIT core is free to self-host with no card, and since 30 September new Cloud organisations start a free trial without payment details (20). An agent can install and run the core locally with npx create-medusa-app and no account, but Cloud and its MCP server need a person to sign up and approve in a browser (15). 0+15+20+15 = 50. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Maintenance & community Medusa API + MCP +11

BigCommerce API + MCP 82

Changelog entries on 30 October 2026 (30). Entries on 28, 29 and 30 October alone, and many more since 4 August (20). Public changelog and a support centre (12). Neither MCP server is in the official registry. Official API clients updated in March 2026 (PHP), May 2026 (Ruby) and August 2026 (Node), while the Python client's last release was 0.23.4 in January 2024, per the 1 October check (12). Catalyst repo runs end-to-end tests on main, per the 1 October check (8).

Medusa API + MCP 93

v2.22.2 tagged on 30 October 2026, after v2.22.0 (21 October) and v2.22.1 (23 October) (30). Nine releases from 4 August to 2 November, v2.19.0 (13 August) to v2.22.2, read from the repository's tags and the changelog at medusajs.com (20). 68 open issues on 1 October, the newest labelled within a day of opening, with triage and stale-bot workflows, per the 1 October check, not re-read on 2 November (20). Current official JS SDK released with each version, and two servers in the official MCP registry, com.medusajs/medusa-mcp (docs) and com.medusajs/cloud (store data, 0.1.0 on 14 October) (15). CI pipeline on every push to develop and every pull request, plus Dependabot triage. We didn't see run results (8). 30+20+20+15+8 = 93.

Agent ergonomics Medusa API + MCP +10

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

Medusa API + MCP 72

Responses can be trimmed with fields, and store routes cap relation depth at three since 2.20.0 (22). limit, offset, order and per-field filters on list routes (20). Errors carry type, code and message, documented in the spec (15). A 409 example tells the caller to retry with an Idempotency-Key, but no such header is documented on any route (5). Few required parameters and a typed JS SDK, but no second official language (10).

Score by category

CategoryWeightBigCommerce API + MCPMedusa API + MCPEdge
Reliability16%7755BigCommerce API + MCP +22
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6681Medusa API + MCP +15
Agent ergonomics13%6272Medusa API + MCP +10
Security & auth14%7049BigCommerce API + MCP +21
Payments & pricing10%6075Medusa API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8293Medusa API + MCP +11
Transparency & trust7%7772BigCommerce API + MCP +5
Negative events≤150-8
TotalB 69.9/100C 60.3/100

Facts side by side

FactBigCommerce API + MCPMedusa API + MCP
KindHTTP APIHTTP API
VendorBigCommerce (Commerce.com)Medusa
Hosted endpointhttps://api.bigcommerce.comno (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicencenoneMIT
Tools exposed718
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listedcom.medusajs/cloud
Last release2026-10-302026-10-30
Terms last updated2026-06-012026-09-21
Privacy policy last updated2026-01-282026-09-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 textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone37k stars, 203k npm/wk
Agent reviews3/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates BigCommerce 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.

Medusa API + MCP

MIT core you can self-host, with Medusa Cloud running the same APIs and no GMV fee. The Cloud MCP server reads store and Cloud data but can't write. Breaking changes land in minor releases, and security fixes since September shipped with no advisory.

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

Medusa API + MCP

  1. Send x-publishable-api-key on every /store call. It decides which sales channels and products the agent sees
  2. Ask for only the fields you need with fields. Store routes reject relations nested more than three deep since 2.20.0
  3. On the Medusa MCP, call find_commerce_api and describe_commerce_api before read_admin_api, and name the store when several are connected
  4. Place the order with POST /store/carts/{id}/complete after shipping and payment sessions are set; the MCP server can't
  5. Read the release notes before upgrading a minor version. Breaking changes land there, and v2.22.0 needs Node.js 22.22.0 or later

Questions

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

BigCommerce API + MCP scores 69.9 (B) on agent readiness against Medusa API + MCP's 60.3 (C), and leads in 3 of 7 scored categories. Medusa API + MCP leads on schema & documentation, agent ergonomics, payments & pricing and maintenance & community.

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

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

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

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

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

No open-source release is listed for BigCommerce API + MCP. Medusa API + MCP is open source (MIT).

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