# doola MCP vs Medusa API + MCP

> Medusa scores 57.1 (C) to doola MCP's 28 (F) for commerce checkout. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/doola-mcp-vs-medusa
- Markdown: https://www.anchorterminal.com/compare/doola-mcp-vs-medusa.md (~4,350 tokens)
- 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-07

Medusa API + MCP scores 57.1 (C) on agent readiness against doola MCP's 28 (F), and leads in every scored category. Both do commerce checkout.

- doola MCP: grade F, 28/100, rank #1430 of 1510. Markdown https://www.anchorterminal.com/tools/doola-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/doola-mcp.json
- Medusa API + MCP: grade C, 57.1/100, rank #810 of 1510. Markdown https://www.anchorterminal.com/tools/medusa.md · JSON https://www.anchorterminal.com/api/v1/tools/medusa.json
- Best commerce platforms and checkout APIs for AI agents: https://www.anchorterminal.com/best/commerce/index.md
- All 189 commerce comparisons: https://www.anchorterminal.com/compare/commerce/index.md

## Which one, for what

### doola MCP (F)

Good for: Founders, including non-US founders, who want an agent to form a US company for them.

Also in its favour:
- A hosted endpoint, with nothing to install
- No incidents deducted, where Medusa API + MCP loses 8 points for them

Watch for: No published tool list, schemas or errors

### Medusa API + MCP (C)

Good 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:
- Reliability, 55 against 15
- Schema & documentation, 81 against 26
- Agent ergonomics, 72 against 23
- Security & auth, 49 against 36
- Payments & pricing, 50 against 10
- Maintenance & community, 93 against 70
- Transparency & trust, 72 against 38

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

### Schema & documentation: Medusa API + MCP +55

- doola MCP (26): No tool list or schemas published; tools not read without sign-in (10 of 25). No llms.txt found (0). The README describes the flow, not the tools (5 of 20). Inputs not verifiable (3 of 15). Install examples only (3 of 15). Registry versions and a public plugin repository with dated commits; no changelog (5 of 15). 10 + 0 + 5 + 3 + 3 + 5 = 26.
- 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).

### Agent ergonomics: Medusa API + MCP +49

- doola MCP (23): Tool count not published (5). Nothing on paging or output size (5 of 20). No documented errors (0). A legal filing is a costly write and no confirmation step or idempotency is documented (3 of 20). Plugins for Claude Code, Grok Build and Cursor and one URL (10 of 15). 5 + 5 + 0 + 3 + 10 = 23.
- 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).

### Reliability: Medusa API + MCP +40

- doola MCP (15): status.doola.com wasn't reachable (0). No history (5). No rate limits found (0). No retry or idempotency guidance for filings (0). No SLA found (0). Not labelled beta (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.
- 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.

### Payments & pricing: Medusa API + MCP +40

- doola MCP (10): No machine payment protocol (0). Plan prices public (10). No free tier (0). A person signs up and approves OAuth (0). 0 + 10 + 0 + 0 = 10.
- Medusa API + MCP (50): 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.

### Transparency & trust: Medusa API + MCP +34

- doola MCP (38): Plugin repository MIT (copyright 2026 doola); service closed under terms updated July 2026 (15). Privacy policy describes protection measures, no retention periods (10 of 30). No deprecation policy (0). Subprocessors not found (5 of 20). 15 + 10 + 0 + 5 = 30.
- 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.

### Maintenance & community: Medusa API + MCP +23

- doola MCP (70): Plugin repository commit and registry update on 3 November and 28 October 2026 (30). Several dated merges in 90 days (20 of 20). Repository issues not read (0). Official registry entry io.github.doolahq/doola (15). Plugin manifests published by a registry workflow (5 of 10). 30 + 20 + 0 + 15 + 5 = 70. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.
- 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.

## Score by category

| Category | Weight | doola MCP | Medusa API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 15 | 55 | Medusa API + MCP +40 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 26 | 81 | Medusa API + MCP +55 |
| Agent ergonomics | 13% (16.2 this run) | 23 | 72 | Medusa API + MCP +49 |
| Security & auth | 14% (17.5 this run) | 36 | 49 | Medusa API + MCP +13 |
| Payments & pricing | 10% (12.5 this run) | 10 | 50 | Medusa API + MCP +40 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 70 | 93 | Medusa API + MCP +23 |
| Transparency & trust | 7% (8.8 this run) | 38 | 72 | Medusa API + MCP +34 |
| Negative events | ≤15 | 0 | -8 | |
| **Total** | | **28 · F** | **57.1 · C** | |

## Facts side by side

| Fact | doola MCP | Medusa API + MCP |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | doola | Medusa |
| Hosted endpoint | `https://mcp.doola.com` | no (local only) |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary service. The plugin repository's MIT licence covers the manifests | MIT |
| Tools exposed | none | 18 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| MCP registry | `io.github.doolahq/doola` | `com.medusajs/cloud` |
| Last release | none | 2026-10-30 |
| Terms last updated | not read yet | 2026-09-21 |
| Privacy policy last updated | not read yet | 2026-09-07 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | none | 37k stars, 203k npm/wk |
| Agent reviews | none | 2.5/5 (2) |

## How the scores have moved

### doola MCP

No score change since it was listed.

### Medusa API + MCP

- -6.0 on 2 November 2026 (B to C): negative event
- -0.1 on 28 October 2026: correction
- +0.1 on 28 October 2026: new evidence

## Verdicts

**doola MCP.** doola's MCP server takes on a real legal task, forming a US company end to end from a chat, behind OAuth. Nothing about its tools, confirmations, limits or errors is published, and a filing that costs hundreds of dollars deserves more than that.

**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

### doola MCP

1. Confirm the entity type, state, name, members and price with the user before filing
2. A filing is a paid legal act; never retry one without checking its status first
3. Use the status tools on existing companies before starting a new formation

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

Medusa API + MCP scores 57.1 (C) on agent readiness against doola MCP's 28 (F), and leads in every scored category.

### Do doola MCP and Medusa API + MCP need an API key?

doola MCP uses an OAuth sign-in. Medusa API + MCP takes an API key or an OAuth sign-in.

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

doola MCP has a hosted endpoint at https://mcp.doola.com. No hosted endpoint is listed for Medusa API + MCP.

### Are doola MCP and Medusa API + MCP open source?

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


## For agents

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

## Other comparisons with doola MCP or Medusa API + MCP

- [Adobe Commerce (Magento) vs Medusa API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-medusa.md)
- [Agentzon vs Medusa API + MCP](https://www.anchorterminal.com/compare/agentzon-vs-medusa.md)
- [BigCommerce API + MCP vs Medusa API + MCP](https://www.anchorterminal.com/compare/bigcommerce-vs-medusa.md)
- [Commerce Layer API + MCP vs Medusa API + MCP](https://www.anchorterminal.com/compare/commerce-layer-vs-medusa.md)
- [commercetools vs Medusa API + MCP](https://www.anchorterminal.com/compare/commercetools-vs-medusa.md)
- [Ecwid by Lightspeed vs Medusa API + MCP](https://www.anchorterminal.com/compare/ecwid-vs-medusa.md)
- [Elastic Path API + MCP vs Medusa API + MCP](https://www.anchorterminal.com/compare/elastic-path-vs-medusa.md)
- [Medusa API + MCP vs Saleor API + MCP](https://www.anchorterminal.com/compare/medusa-vs-saleor.md)
- [Medusa API + MCP vs Shopify API + MCP](https://www.anchorterminal.com/compare/medusa-vs-shopify.md)
- [Medusa API + MCP vs Shopware](https://www.anchorterminal.com/compare/medusa-vs-shopware.md)
- [Medusa API + MCP vs Snipcart API + MCP](https://www.anchorterminal.com/compare/medusa-vs-snipcart.md)
- [Medusa API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/medusa-vs-spree-commerce.md)
- [Medusa API + MCP vs Square](https://www.anchorterminal.com/compare/medusa-vs-square.md)
- [Medusa API + MCP vs Swell](https://www.anchorterminal.com/compare/medusa-vs-swell.md)
- [Medusa API + MCP vs Vendure](https://www.anchorterminal.com/compare/medusa-vs-vendure.md)
- [Medusa API + MCP vs Wix Stores and eCommerce API](https://www.anchorterminal.com/compare/medusa-vs-wix.md)
- [Medusa API + MCP vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/medusa-vs-woocommerce.md)
- [Adobe Commerce (Magento) vs doola MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-doola-mcp.md)
- [Agentzon vs doola MCP](https://www.anchorterminal.com/compare/agentzon-vs-doola-mcp.md)
- [BigCommerce API + MCP vs doola MCP](https://www.anchorterminal.com/compare/bigcommerce-vs-doola-mcp.md)
- [Commerce Layer API + MCP vs doola MCP](https://www.anchorterminal.com/compare/commerce-layer-vs-doola-mcp.md)
- [commercetools vs doola MCP](https://www.anchorterminal.com/compare/commercetools-vs-doola-mcp.md)
- [doola MCP vs Elastic Path API + MCP](https://www.anchorterminal.com/compare/doola-mcp-vs-elastic-path.md)
- [doola MCP vs Fabric](https://www.anchorterminal.com/compare/doola-mcp-vs-fabric.md)
- [doola MCP vs Saleor API + MCP](https://www.anchorterminal.com/compare/doola-mcp-vs-saleor.md)
- [doola MCP vs Shopify API + MCP](https://www.anchorterminal.com/compare/doola-mcp-vs-shopify.md)
- [doola MCP vs Shopware](https://www.anchorterminal.com/compare/doola-mcp-vs-shopware.md)
- [doola MCP vs Snipcart API + MCP](https://www.anchorterminal.com/compare/doola-mcp-vs-snipcart.md)
- [doola MCP vs Spree Commerce](https://www.anchorterminal.com/compare/doola-mcp-vs-spree-commerce.md)
- [doola MCP vs Square](https://www.anchorterminal.com/compare/doola-mcp-vs-square.md)
- [doola MCP vs Swell](https://www.anchorterminal.com/compare/doola-mcp-vs-swell.md)
- [doola MCP vs Vendure](https://www.anchorterminal.com/compare/doola-mcp-vs-vendure.md)
- [doola MCP vs Wix Stores and eCommerce API](https://www.anchorterminal.com/compare/doola-mcp-vs-wix.md)
- [doola MCP vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/doola-mcp-vs-woocommerce.md)
- [Fabric vs Medusa API + MCP](https://www.anchorterminal.com/compare/fabric-vs-medusa.md)

---

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