Head to head · Commerce checkout · October 2026 research run

doola MCP vs Swell

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

Best commerce platforms and checkout APIs for AI agents · All 189 commerce comparisons

Which one, for what

doola MCP F

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

Also in its favour

  • No incidents deducted, where Swell loses 3 points for them

Watch for

No published tool list, schemas or errors

Swell C

Best for Developers who want a hosted headless store with a flexible data model and an agent that writes server-side.

Ahead on

  • Reliability, 67 against 15
  • Schema & documentation, 71 against 26
  • Agent ergonomics, 65 against 23
  • Security & auth, 42 against 36
  • Payments & pricing, 25 against 10
  • Maintenance & community, 82 against 70
  • Transparency & trust, 60 against 38

Watch for

One full-access secret key per environment, with no scoped or read-only key

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 Swell +52

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.

Swell 67

Atlassian Statuspage at status.swell.store with Backend API, Frontend API, Dashboard, Hosted Checkout, CDN and Storefronts components and a history feed (20). The feed for 6 August to 4 November shows four incidents titled "Experiencing degraded service" (31 August, 3 hours 11 minutes; 3 September, 3 hours 26 minutes; 12 October, 55 minutes; 20 October, 58 minutes), each saying the platform "is currently experiencing degraded performance", labelled impact none on its incident page with no component named, read as minor. Database maintenance on 30 September and 11 and 12 October was announced with windows and is maintenance, not incidents (20; the 1 October 15 rested on a partial window). Throughput and concurrency limits are per store and environment, with the weighting formula documented but the figures unpublished ("contact Swell if you need to know the limits"). Monthly quotas of 100K, 500K and 2M requests are public (5, the earlier partial kept). Requests over the limit queue, a 429 means one waited more than 60 seconds, and the rate limits page says to back off and retry with increasing delays. The transactions page says a failed transaction rolls back completely and to retry transaction_conflict (409) and transaction_throttled (429) with exponential backoff, since the other errors fail the same way again. No Retry-After on API answers or idempotency keys found, so back-off plus safe-retry guidance on writes without keys (12; 8 on 1 October wasn't a checklist value). The pricing page lists a "100% uptime SLA" on Unlimited, but robots.txt disallows /sla and /legal/service-level-agreement, so no SLA document could be read (0). Generally available (10). 20 + 20 + 5 + 12 + 0 + 10 = 67.

Schema & documentation Swell +45

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.

Swell 71

No OpenAPI file. GET /:models returns each store's models with field types and descriptions, which is machine-readable but specific to Swell (15). developers.swell.is/llms.txt now answers (404 on 1 October), lists 378 pages, says every page is served as Markdown at a .md address and links llms-full.txt (10). The docs and the official skills say which API fits which job and list the non-obvious rules, such as PUT deep-merging arrays by element id (15). Field types and validation codes (MINVAL, ENUM with allowed values, READONLY), but write bodies are free-form JSON (9). Status codes and validation objects documented with examples (13). Monthly dated changelog with no API versioning (9). 15 + 10 + 15 + 9 + 13 + 9 = 71.

Agent ergonomics Swell +42

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.

Swell 65

limit (Frontend API maximum raised to 1,000 in December 2025) and expand and include controls, with heavier expands costing rate-limit weight. Field selection not confirmed (15). Page envelopes with count, page and page_count, plus where operators, sort and search (20). Validation errors carry a code per field, but invalid writes return HTTP 200 with an errors object, so an agent that doesn't check them reports success (15). No idempotency keys. Transactions roll back only on request errors, and there's no undo for merges (5). Official JavaScript libraries only (swell-node and swell-js), with simple Basic auth (10).

Transparency & trust Swell +22

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.

Swell 60

Closed platform with published terms, and MIT SDKs and skills (15). The privacy policy, last modified 3 November 2026, gives retention only as long as necessary. The Data Processing Addendum linked from the security page commits to processing only on instructions, a purge after termination with a copy on request within 30 days, and a named sub-processor list. No retention periods by data type (20 of 30; 10 on 1 October before the DPA was read). No deprecation policy or dated notices found (0). The DPA names ten sub-processors with their purpose and headquarters (AWS, Google Cloud Platform and DigitalOcean for hosting, Cloudflare, Twilio, SolarWinds and others) and says EEA personal data is processed in the United States, with no hosting regions beyond that (16 of 20; 6 on 1 October). 15 + 20 + 0 + 16 = 51.

Payments & pricing Swell +15

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.

Swell 25

No x402, MPP or L402 (0). Plan prices are public with per-unit overage, $5 per extra 100K API requests and $5 per extra GB, plus 2 to 0.4 per cent above each sales ceiling (15). No free plan. A free trial on every plan, with the card requirement not stated (10). A person signs up in the browser (0).

Maintenance & community Swell +12

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.

Swell 82

Re-read from depth-200 clones and the changelog on 4 November. swell-js v5.9.3 was tagged on 3 November 2026, the day before (30). In the 90 days from 6 August, dated changelog entries on 31 August and 30 September, swell-js 5.8.2 (24 September), 5.9.0 (28 September), 5.9.1 (29 September), 5.9.2 (7 October) and 5.9.3, and the official skills plugin from 0.7.0 (8 October) to 0.12.0 (2 November) (20). Monthly changelog and email and chat support on every plan (12, kept). swell-js is current; swell-node's last tag is still 6.0.5 from 18 May 2026. No Swell MCP server in the registry (12, kept). Test workflows in both SDK repositories (8). 30 + 20 + 12 + 12 + 8 = 82.

Score by category

CategoryWeight this rundoola MCPSwellEdge
Reliability16%201567Swell +52
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.22671Swell +45
Agent ergonomics13%16.22365Swell +42
Security & auth14%17.53642Swell +6
Payments & pricing10%12.51025Swell +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87082Swell +12
Transparency & trust7%8.83860Swell +22
Negative events≤150-3
TotalF 28/100C 55.4/100

Facts side by side

Factdoola MCPSwell
KindMCP serverHTTP API
VendordoolaSwell
Hosted endpointhttps://mcp.doola.comhttps://api.swell.store
TransportsStreamable HTTPHTTP
AuthOAuthAPI key
PricingPaidPaid
x402nono
LicenceProprietary service. The plugin repository's MIT licence covers the manifestsnone
Read-only variant documentednono
llms.txtnoyes
MCP registryio.github.doolahq/doolanot listed
Last releasenone2026-11-03
Terms last updatednot read yetno date given
Privacy policy last updatednot read yet2026-08-19
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularitynone4.5k npm/wk
Agent reviewsnone2.5/5 (2)

How the scores have moved

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.

Swell

Swell's REST API covers carts, coupons, subscriptions and orders, with a live /:models schema, llms.txt and Markdown docs, and a named sub-processor list. Each environment has one full-access secret key with no scoped or read-only option, rate-limit figures aren't published, and a November 2026 platform fix for cross-origin shopper writes came 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

Swell

  1. Call GET /:models once and cache it. It's the ground truth for custom fields
  2. Check result.errors after every write. A failed validation still returns 200
  3. Use $set to replace an array. A plain PUT merges arrays by element id and never shrinks them
  4. Use an sk_test_ key while testing. A bare sk_ prefix is live
  5. Keep expand and include small. Each level past the first three points adds rate-limit weight

Questions

Which is better for AI agents, doola MCP or Swell?

Swell scores 55.4 (C) on agent readiness against doola MCP's 28 (F), and leads in every scored category.

Do doola MCP and Swell need an API key?

doola MCP uses an OAuth sign-in. Swell needs an API key.

Can an agent call doola MCP and Swell without installing anything?

Yes. doola MCP has a hosted endpoint at https://mcp.doola.com and Swell at https://api.swell.store.

Other comparisons with doola MCP or Swell

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.