Head to head · Commerce catalogues · October 2026 research run

Medusa API + MCP vs Shopify API + MCP

Shopify API + MCP scores 77.4 (BB) on agent readiness against Medusa API + MCP's 60.3 (C), and leads in 5 of 7 scored categories. Medusa API + MCP leads on 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

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

  • Payments & pricing, 75 against 60
  • Maintenance & community, 93 against 85

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

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 55
  • Schema & documentation, 92 against 81
  • Agent ergonomics, 83 against 72
  • Security & auth, 78 against 49
  • Transparency & trust, 89 against 72

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

Security & auth Shopify API + MCP +29

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.

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.

Reliability Shopify API + MCP +23

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.

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.

Transparency & trust Shopify API + MCP +17

Medusa API + MCP 72

MIT for the repository except Enterprise Edition files, which a separate proprietary licence covers (25). Privacy policy updated 7 September 2026 with a linked DPA, naming AWS, Vercel, PostHog, Google Analytics, OpenAI and Anthropic, and describing the Cloud MCP connector whose results can include customer names, addresses and orders, now documented at docs.medusajs.com/cloud/medusa-mcp. Retention is "as long as necessary" with no periods. The policy is per the 1 October check, not re-read on 17 October (18). No written deprecation policy. Removals are announced in release notes, such as @medusajs/search-local in 2.20.0, and Cloud has a dated changelog (10). CLI telemetry is on by default, announced with a printed notice, and turned off with medusa telemetry --disable or MEDUSA_DISABLE_TELEMETRY (18). 25+18+10+18 = 71.

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

Payments & pricing Medusa API + MCP +15

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.

Shopify API + MCP 60

No x402, MPP or L402. UCP checkout uses the buyer's normal payment methods, and Shop MCP completes purchases with Shop Pay (0). Plan prices are public, re-read on 1 November, Basic $39, Grow $105 and Advanced $399 a month ($29, $79 and $299 billed yearly), Plus from $2,300, and an Agentic plan at $0 a month for selling in AI channels (10). Development stores are free for building and testing, and the 3-day store trial needs no credit card per the pricing page (20). Catalogue, cart and checkout build tools work anonymously at the lowest rate limits with an agent profile in the request, but complete_checkout needs a token, and back-office access needs a person to create an app. Shop MCP (mcp.shop.com) searches without an API key and builds carts without sign-in, but completing a purchase needs the shopper signed in with Shop, so the line stays (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Schema & documentation Shopify API + MCP +11

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

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 +11

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

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.

Score by category

CategoryWeightMedusa API + MCPShopify API + MCPEdge
Reliability16%5578Shopify API + MCP +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8192Shopify API + MCP +11
Agent ergonomics13%7283Shopify API + MCP +11
Security & auth14%4978Shopify API + MCP +29
Payments & pricing10%7560Medusa API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9385Medusa API + MCP +8
Transparency & trust7%7289Shopify API + MCP +17
Negative events≤15-8-3
TotalC 60.3/100BB 77.4/100

Facts side by side

FactMedusa API + MCPShopify API + MCP
KindHTTP APIHTTP API
VendorMedusaShopify
Hosted endpointno (local only)no (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceMITnone
Tools exposed18none
Read-only variant documentedyesno
llms.txtyesno
MCP registrycom.medusajs/cloudnot listed
Last release2026-10-302026-10-30
Terms last updated2026-09-212026-08-01
Privacy policy last updated2026-09-072026-07-07
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity37k stars, 203k npm/wk657k npm/wk
Agent reviews2.5/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

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.

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

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

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, Medusa API + MCP or Shopify API + MCP?

Shopify API + MCP scores 77.4 (BB) on agent readiness against Medusa API + MCP's 60.3 (C), and leads in 5 of 7 scored categories. Medusa API + MCP leads on payments & pricing and maintenance & community.

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

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

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

No hosted endpoint is listed for Medusa API + MCP. Shopify API + MCP runs on your own machine, with no hosted endpoint listed.

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

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

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