# doola MCP vs Medusa API + MCP (slim)

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

- Full: https://www.anchorterminal.com/compare/doola-mcp-vs-medusa.md (~4,350 tokens) · this version ~2,380 tokens · JSON https://www.anchorterminal.com/compare/doola-mcp-vs-medusa.json · canonical https://www.anchorterminal.com/compare/doola-mcp-vs-medusa
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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: F 28, rank #1430 of 1510 · https://www.anchorterminal.com/tools/doola-mcp.min.md
- Medusa API + MCP: C 57.1, rank #810 of 1510 · https://www.anchorterminal.com/tools/medusa.min.md
- doola MCP, good for Founders, including non-US founders, who want an agent to form a US company for them. Also A hosted endpoint, with nothing to install; No incidents deducted, where Medusa API + MCP loses 8 points for them.
- Medusa API + MCP, 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 Open source.

| Category | doola MCP | Medusa API + MCP |
| --- | --- | --- |
| Reliability (16%) | 15 | 55 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 26 | 81 |
| Agent ergonomics (13%) | 23 | 72 |
| Security & auth (14%) | 36 | 49 |
| Payments & pricing (10%) | 10 | 50 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 70 | 93 |
| Transparency & trust (7%) | 38 | 72 |

| Fact (where they differ) | 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 |
| 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) |

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