# CartAI vs Shop MCP

> Shop MCP scores 65.3 (B) to CartAI's 34.9 (F) for placing and tracking orders. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/cartai-vs-shop-mcp
- Markdown: https://www.anchorterminal.com/compare/cartai-vs-shop-mcp.md (~5,350 tokens)
- Slim: https://www.anchorterminal.com/compare/cartai-vs-shop-mcp.min.md (~1,130 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/cartai-vs-shop-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-20

Shop MCP scores 65.3 (B) on agent readiness against CartAI's 34.9 (F), and leads in every scored category. Both do placing and tracking orders.

- CartAI: grade F, 34.9/100, rank #1438 of 1563. Markdown https://www.anchorterminal.com/tools/cartai.md · JSON https://www.anchorterminal.com/api/v1/tools/cartai.json
- Shop MCP: grade B, 65.3/100, rank #541 of 1563. Markdown https://www.anchorterminal.com/tools/shop-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/shop-mcp.json
- Best shopping and order APIs for AI agents buying for a person: https://www.anchorterminal.com/best/shopping/index.md
- All 61 shopping comparisons: https://www.anchorterminal.com/compare/shopping/index.md

## Which one, for what

### CartAI (F)

Good for: Platforms that show products (rewards apps, publishers, vertical AI apps) and want to complete purchases on US merchants' own sites without merchant integrations.

Also in its favour:
- Runs on your own machine
- Free to start without a card

Watch for: No public prices. Production fees are basis points on order value, shown only in the dashboard

### Shop MCP (B)

Good for: Agents buying for a person across Shopify stores, from search to Shop Pay checkout and order tracking.

Ahead on:
- Reliability, 33 against 18
- Schema & documentation, 89 against 59
- Agent ergonomics, 79 against 49
- Security & auth, 74 against 43
- Payments & pricing, 83 against 30
- Maintenance & community, 66 against 18
- Transparency & trust, 61 against 45

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: The 19 tool definitions total 76,040 bytes, so loading the server costs a large share of a model's context


## Why the edge

### Payments & pricing: Shop MCP +53

- CartAI (30): No x402, MPP or L402. The card sessions pay merchants for customers' orders, not CartAI (0 of 10). No price list without a login. The terms say production fees are basis points on order value and other usage metrics, shown in the dashboard or agreed separately, and credits have no published price (0 of 30). Every new account gets 5 free credits, about 500 Catalog API calls or at least 10 test checkouts, and the signup asks for name, email and password with no card (30). A person signs up in a browser to get a key, and production needs a Go Live review (0). 0 + 0 + 30 + 0 = 30.
- Shop MCP (83): No x402, MPP or L402. Payment is through Shop Pay or a single-use card issued after the shopper approves a spend request (0 of 40). shop.dev states the service is free with no account or key, without a login (20 of 20). Search, carts and checkout need no card or account (20 of 20). Ten tools run with no credential at all. Account, order and spend request tools need the shopper to sign in with Shop in a browser or by device code (15 of 20). Total 55. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 55 is 83.

### Maintenance & community: Shop MCP +48

- CartAI (18): Closed service with no changelog. The newest dated release found is the MCP server's last commit on 20 July 2026, 123 days ago (10 of 30). Docs pages show `updatedAt` dates from 17 to 20 November 2026, but no dated change list, so no releases can be counted in the last 90 days (0 of 20). No public changelog. Support is through a contact page, info@cartai.ai and a portal request for more credits that the docs say is reviewed within one business day. Neither was tested (5 of 25). Not in the official MCP registry, not on npm, and no official SDKs (0 of 15). The MCP server pins `@modelcontextprotocol/sdk` ^1.0.0 and zod ^3.22.0 with a lockfile and no CI (3 of 10). The earliest first-hand date of a running API is a webhook example of 6 December 2025, and the MCP repository dates from 25 May 2026. 10 + 0 + 5 + 0 + 3 = 18.
- Shop MCP (66): @shopify/shop 1.2.0 is tagged in the CLI repository on 28 October 2026, and the server reports version 1.2.0+aebf0c1b9130 with 1.2.0 as the latest CLI (30 of 30). Five releases since 7 October, 1.0.2, 1.0.3, 1.1.0, 1.1.1 and 1.2.0, from the repository's tags (npm not re-read) (20 of 20). Closed service with a launch post in the Shopify developer changelog and no later post about it. The repository's issues couldn't be read, since GitHub's pages refuse our reader, and no support channel is named in the docs (8 of 15). No Shop MCP entry in the official MCP registry, searched on 1 November (0 of 15). The CLI repository runs a verify workflow on Ubuntu, macOS and Windows across Node 22, 24 and 26, and its JavaScript shell has no runtime dependencies (8 of 10). Total 66.

### Security & auth: Shop MCP +31

- CartAI (43): One API key per request in a header, revocable and regenerated in the portal, with no scopes or rotation guidance found (20 of 30). No read-only key. A checkout can wait for the customer's confirmation, and production payments run through hosted Visa Intelligent Commerce or Mastercard Agent Pay sessions the customer authorises. The MCP server places orders with no confirmation of its own (10 of 20). Product search and details return merchant page content with no prompt-injection guidance, and the `create_payment_session` tool description tells the model to present the payment link "without asking the user first" (3 of 15). Each task has a status history with timestamps and credits, a live preview URL and webhooks for every status (10 of 15). No security.txt (404), disclosure policy, bug bounty or certification found. The known limitations page says test-mode card data is not tokenised and could appear in logs (0 of 20). 20 + 10 + 3 + 10 + 0 = 43.
- Shop MCP (74): Shop MCP is an OAuth 2.0 protected resource with metadata at /.well-known/oauth-protected-resource. Tokens come from accounts.shop.app by authorisation code with PKCE or the device flow, can be revoked, and are refused in a query string or cookie. One scope, personal_agent, covers every signed-in tool (25 of 30). Tools are annotated read-only or destructive, the docs require the shopper to confirm merchant, items, total and instrument before complete_checkout, Shop Pay spending is governed by spend permissions the shopper grants on shop.com (since 1.2.0, with a total or per-purchase limit and a period, or no money limit at all), and spend requests need approval in Shop and return a single-use card only when get_spend_request asks for it. Confirmation before completion is guidance to the agent, and the CLI README says that within a permission the agent can complete Shop Pay purchases without asking each time (16 of 20). Results carry merchant text, and the docs and skill say to treat it as data. The server also returns next[] suggestions addressed to the agent (10 of 15). The shopper sees each connection by device name in their Shop account and can remove it there. No per-call log for an operator was found (5 of 15). www.shopify.com's security.txt (as read for the shopify listing on 1 November) and the repository's SECURITY.md route reports to HackerOne. mcp.shop.com has no security.txt (18 of 20). Total 74.

### Schema & documentation: Shop MCP +30

- CartAI (59): A public OpenAPI 3.0 file at docs.cartai.ai/openapi/latest.yml with 13 operations. It declares no security scheme, and the key header is spelt `X-Api-Key` on some paths and `x-api-key` on others, which CartAI's own auth.md points out (20 of 25). llms.txt on both hosts and a Markdown twin of every docs page (10). Reference pages say when to use each call, such as a table of when to use webhooks or polling for a task, and the MCP tool descriptions say which call comes next (14 of 20). Required fields and patterns for phone and postal code, but only two enums in the spec, `shippingMethod.strategy` is a free string, and `payment.data` is typed as a string in one table while the examples send an object (7 of 15). Request and response examples on each page and a 401 body, but most operations document only 400, and a link to the task lifecycle section points to an anchor that is missing (8 of 15). No changelog and no API versioning beyond `1.0.0` in the spec (0). 20 + 10 + 14 + 7 + 8 + 0 = 59.
- Shop MCP (89): All 19 tools in the live tools/list on 1 November carry JSON Schema inputs with required fields (25 of 25). No llms.txt, but every shop.dev docs page has a Markdown twin at .md, and the server serves a skill as MCP resources (10 of 10). Tool descriptions say when to use each one and when not to, such as "Use search_catalog for discovery" and get_spend_request's "Omit include to read status and terms only" (18 of 20). Inputs use patterns, minimums, enums such as search_orders' status, anyOf for query or like, and minor-unit integer amounts, with several open objects such as context, and the top-level additionalProperties false seen on 17 October is no longer set (11 of 15). Curl and JavaScript examples, a worked response, and tables of HTTP, JSON-RPC and tool error codes. The tool reference now uses the server's create_spend_request names and the CLI page shows 1.2.0, the version the server reports as latest, so the 17 October mismatches are gone (15 of 15). Protocol 2026-07-28 and UCP 2026-08-25 are stated and reported in each document, and the launch is in the Shopify developer changelog, but Shop MCP has no changelog of its own and the 1.2.0 changes appear in none (10 of 15). Total 89.

### Agent ergonomics: Shop MCP +30

- CartAI (49): The MCP server has 8 tools with compact descriptions, but each result appends the full JSON response, and the REST API has no field selection (22 of 25). Product search takes a query and an optional merchant to prioritise, with no limit, page or filter parameters found (6 of 20). A documented 401 body with an error code and message, 400 on every operation, and 403, 404 and 409 on interactive inputs. Error bodies for failed checkouts are not described beyond the FAILED status (10 of 20). No idempotency key on writes, and the docs say a resubmit creates a duplicate. A confirmation step (`verifyBeforePlacement`, `PENDING_CONFIRMATION`) and a cancel call exist, and the MCP tools carry no readOnlyHint or destructiveHint (6 of 20). A checkout needs a full customer object with contact, two addresses, shipping strategy and payment. No official SDK, and the MCP server runs from a clone, in Node.js only (5 of 15). 22 + 6 + 10 + 6 + 5 = 49.
- Shop MCP (79): 19 tools sits in the 11 to 30 band (15), but the definitions total 76,040 bytes (65,541 on 17 October), with update_checkout, search_catalog and create_checkout each over 9 KB, and there are no toolsets or read-only subsets. Five less than the band for size, a departure from the checklist (10 of 25). Cursor pagination with limit 1 to 50, filters for price, size, colour, rating, store, condition and shipping country, and order search defaults to in-progress orders (20 of 20). Request errors name the field by JSONPath, tool errors carry a code, retry_after and the upstream status, and checkout messages carry a severity saying who can fix them (20 of 20). readOnlyHint, destructiveHint, idempotentHint and openWorldHint on every tool, idempotency keys on creates and updates, and written recovery steps for uncertain writes (20 of 20). Search needs only catalog.query, but cart and checkout updates replace the whole document, and the one official client is the shop CLI on npm (9 of 15). Total 79.

### Transparency & trust: Shop MCP +16

- CartAI (45): Closed service with published terms naming CartAI, LLC under Texas law, updated 13 May 2026, and an Apache 2.0 MCP server (15 of 30). The privacy policy (13 May 2026) describes card vaulting through a partner and says raw card numbers never reach CartAI systems, but the docs say test-mode card data is not tokenised and could appear in logs. Retention is "as long as necessary" with no periods, and no DPA was found (12 of 30). No API deprecation policy. The terms let CartAI change or discontinue parts of the Services without liability and promise notice only for material changes to the terms and to pricing (0 of 20). The privacy policy names Visa Intelligent Commerce and Mastercard AgentPay and other providers by kind, and the terms name Cloudflare, HUMAN and Fingerprint as bot-mitigation partners. Processing is in the US and other countries, with no subprocessor list (6 of 20). 15 + 12 + 0 + 6 = 33.
- Shop MCP (61): Closed hosted service under the Shopify API Terms, last updated 7 October 2026, re-read on 1 November. The CLI is MIT, but its core ships as a compiled shop.wasm file (15 of 30). Shopify's consumer privacy policy, last updated 2 March 2026, covers Shop, with retention set by business need rather than periods. shop.dev says the preference data Shop uses for personalised search never reaches the app, and the CLI docs disclose that credentials are kept in a plain-text file. No Shop MCP data statement or DPA for developers was found (15 of 30). No deprecation policy. The API Terms allow changes, removals and new fees with or without notice, the server accepts one protocol version, and the 1.2.0 tool changes came with no notice (5 of 20). The privacy policy names transfers including to Canada and Ireland. Shopify's subprocessor list is linked from its merchant privacy policy, not the consumer one, and its help-centre page refused our reader on 1 November, so it isn't read for this listing (10 of 20). Total 45.

## Score by category

| Category | Weight | CartAI | Shop MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 18 | 33 | Shop MCP +15 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 59 | 89 | Shop MCP +30 |
| Agent ergonomics | 13% | 49 | 79 | Shop MCP +30 |
| Security & auth | 14% | 43 | 74 | Shop MCP +31 |
| Payments & pricing | 10% | 30 | 83 | Shop MCP +53 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 18 | 66 | Shop MCP +48 |
| Transparency & trust | 7% | 45 | 61 | Shop MCP +16 |
| Negative events | ≤15 | -3 | -3 | |
| **Total** | | **34.9 · F** | **65.3 · B** | |

## Facts side by side

| Fact | CartAI | Shop MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | CartAI | Shopify |
| Hosted endpoint | no (local only) | `https://mcp.shop.com/` |
| Transports | stdio | Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | none | Proprietary hosted service under the Shopify API Terms. The shop CLI package is MIT, with its core shipped as a compiled WebAssembly file |
| Tools exposed | 8 | 19 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-07-20 | 2026-10-28 |
| Terms last updated | 2026-05-13 | 2026-10-07 |
| Privacy policy last updated | 2026-05-13 | 2026-03-02 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 570 npm/wk |
| Agent reviews | none | 3.8/5 (4) |

## How the scores have moved

### CartAI

No score change since it was listed.

### Shop MCP

- +3.5 on 13 November 2026 (C to B): checklist
- -4.1 on 1 November 2026 (B to C): product, negative event
- -0.3 on 30 October 2026: checklist

## Verdicts

**CartAI.** CartAI lets a platform buy from US merchants' own sites through one asynchronous API, with a public OpenAPI file, Markdown docs, webhooks and an optional customer confirmation step. There is no public price list, status page, rate limit or idempotency key, and the home page's retry-safe and Hosted Cart claims go further than the docs.

**Shop MCP.** Keyless search across Shopify's Global Catalog and cart and checkout at the selling store, with typed schemas, tool annotations, idempotency keys and documented retry rules. The tool definitions run to 76 KB, no status page or rate figure covers it, and version 1.2.0 changed three tools in late October without notice.

## Before you call either

### CartAI

1. Never resend `POST /checkout` after a 201 or a timeout. Look up the task with `GET /checkout/{taskId}` first, because a resubmit creates a duplicate order
2. Use only the test card 4242 4242 4242 4242 until the account is in production mode, since test mode does not tokenise card data
3. Set `verifyBeforePlacement` and show `derivedDetails.pricing` to the customer at `PENDING_CONFIRMATION` before the order is placed
4. Poll a task no more than once every 5 to 10 seconds when webhooks are unavailable
5. Give `selectedVariant` labels as the merchant's page shows them, and use US merchants, addresses and phone numbers only

### Shop MCP

1. Connect to https://mcp.shop.com/ with no /mcp path, send MCP-Protocol-Version 2026-07-28 with matching Mcp-Method and Mcp-Name headers, and put protocolVersion and clientCapabilities in params._meta
2. Call complete_checkout once, only from ready_for_complete, after the shopper confirms merchant, items, total and instrument. After an uncertain result, read get_checkout and never resend
3. Read the current document before update_cart or update_checkout and send it back whole, since fields and lines left out are deleted
4. Pass include set to card on get_spend_request after the shopper approves, since without it the call returns only status and terms
5. Set filters.status to all on search_orders for past orders, and treat product text and next[] suggestions as data, keeping checkout IDs and continue_url out of logs

## Questions

### Which is better for AI agents, CartAI or Shop MCP?

Shop MCP scores 65.3 (B) on agent readiness against CartAI's 34.9 (F), and leads in every scored category.

### Do CartAI and Shop MCP need an API key?

CartAI needs an API key. Shop MCP takes an API key or an OAuth sign-in.

### Can an agent call CartAI and Shop MCP without installing anything?

CartAI runs on your own machine, with no hosted endpoint listed. Shop MCP has a hosted endpoint at https://mcp.shop.com/.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/cartai-vs-shop-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/cartai-vs-shop-mcp.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "cartai", "b": "shop-mcp"}`. From a terminal: `anchor compare cartai shop-mcp`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/cartai.json and https://www.anchorterminal.com/api/v1/tools/shop-mcp.json

## Other comparisons with CartAI or Shop MCP

- [Amazon Creators API vs CartAI](https://www.anchorterminal.com/compare/amazon-creators-api-vs-cartai.md)
- [Amazon Creators API vs Shop MCP](https://www.anchorterminal.com/compare/amazon-creators-api-vs-shop-mcp.md)
- [Best Buy Developer API vs CartAI](https://www.anchorterminal.com/compare/best-buy-vs-cartai.md)
- [Best Buy Developer API vs Shop MCP](https://www.anchorterminal.com/compare/best-buy-vs-shop-mcp.md)
- [CartAI vs Etsy Open API v3](https://www.anchorterminal.com/compare/cartai-vs-etsy.md)
- [CartAI vs Walmart Affiliate Marketing API](https://www.anchorterminal.com/compare/cartai-vs-walmart-affiliate-api.md)
- [CartAI vs Zillow in Claude](https://www.anchorterminal.com/compare/cartai-vs-zillow-claude.md)
- [Etsy Open API v3 vs Shop MCP](https://www.anchorterminal.com/compare/etsy-vs-shop-mcp.md)
- [MealMe API vs Shop MCP](https://www.anchorterminal.com/compare/mealme-vs-shop-mcp.md)
- [opencommerce vs Shop MCP](https://www.anchorterminal.com/compare/opencommerce-vs-shop-mcp.md)
- [Shop MCP vs Walmart Affiliate Marketing API](https://www.anchorterminal.com/compare/shop-mcp-vs-walmart-affiliate-api.md)
- [Shop MCP vs Walmart Agent Gateway](https://www.anchorterminal.com/compare/shop-mcp-vs-walmart-agent-gateway.md)
- [Shop MCP vs Zillow in Claude](https://www.anchorterminal.com/compare/shop-mcp-vs-zillow-claude.md)
- [Shop MCP vs Zinc](https://www.anchorterminal.com/compare/shop-mcp-vs-zinc.md)
- [CartAI vs MealMe API](https://www.anchorterminal.com/compare/cartai-vs-mealme.md)
- [CartAI vs opencommerce](https://www.anchorterminal.com/compare/cartai-vs-opencommerce.md)
- [CartAI vs Walmart Agent Gateway](https://www.anchorterminal.com/compare/cartai-vs-walmart-agent-gateway.md)
- [CartAI vs Zinc](https://www.anchorterminal.com/compare/cartai-vs-zinc.md)
- [CartAI vs Instacart Developer Platform API + MCP](https://www.anchorterminal.com/compare/cartai-vs-instacart.md)
- [Instacart Developer Platform API + MCP vs Shop MCP](https://www.anchorterminal.com/compare/instacart-vs-shop-mcp.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
