# BigCommerce API + MCP vs doola MCP (slim)

> BigCommerce scores 67.4 (B) 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/bigcommerce-vs-doola-mcp.md (~4,550 tokens) · this version ~2,480 tokens · JSON https://www.anchorterminal.com/compare/bigcommerce-vs-doola-mcp.json · canonical https://www.anchorterminal.com/compare/bigcommerce-vs-doola-mcp
- 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)

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

- BigCommerce API + MCP: B 67.4, rank #330 of 1510 · https://www.anchorterminal.com/tools/bigcommerce.min.md
- doola MCP: F 28, rank #1430 of 1510 · https://www.anchorterminal.com/tools/doola-mcp.min.md
- BigCommerce API + MCP, good for Agents working with existing BigCommerce stores, for back-office automation through REST or guest shopping through the MCP. Ahead on Reliability, 77 against 15; Schema & documentation, 66 against 26; Agent ergonomics, 62 against 23; Security & auth, 70 against 36; Payments & pricing, 40 against 10; Maintenance & community, 82 against 70; Transparency & trust, 77 against 38.
- doola MCP, good for Founders, including non-US founders, who want an agent to form a US company for them.

| Category | BigCommerce API + MCP | doola MCP |
| --- | --- | --- |
| Reliability (16%) | 77 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 66 | 26 |
| Agent ergonomics (13%) | 62 | 23 |
| Security & auth (14%) | 70 | 36 |
| Payments & pricing (10%) | 40 | 10 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 70 |
| Transparency & trust (7%) | 77 | 38 |

| Fact (where they differ) | BigCommerce API + MCP | doola MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | BigCommerce (Commerce.com) | doola |
| Hosted endpoint | `https://api.bigcommerce.com` | `https://mcp.doola.com` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Licence | none | Proprietary service. The plugin repository's MIT licence covers the manifests |
| Tools exposed | 7 | none |
| llms.txt | yes | no |
| MCP registry | not listed | `io.github.doolahq/doola` |
| Last release | 2026-10-30 | none |
| Terms last updated | 2026-06-01 | not read yet |
| Privacy policy last updated | 2026-01-28 | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Reliability, BigCommerce API + MCP +62: BigCommerce API + MCP 77 (Atlassian Statuspage at status.bigcommerce.com with API & Webhooks, Checkout & Payment Processing, Storefront and B2B components, a history page and an Atom feed (20). Read on 2 November, the history holds 36 incidents from 4 August, 8 in August, 8 in September and 20 in October. Seven carry a major or critical label, each partial by its own text. Microsoft single sign-on failed for a subset of stores for 29 minutes (25 August), Modern Import/Export catalogue export failed for 65 minutes (14 September), the Contact Center phone system was down (16 September, not the platform), category pages showed inaccurate stock (23 September), QuickBooks Payments stores couldn't take payments for 3 hours 39 minutes (5 October, one provider), some Chrome on Android shoppers on headless storefronts couldn't reach checkout (26 October), and Bolt payments failed for 2 hours 12 minutes after Bolt changed its domain (27 October, one provider). Search returned HTTP 500s across the platform for 66 minutes on 27 October, search only, and Management API add-to-cart requests failed for 59 minutes on 12 October. The 10 July availability major left the window on 8 October, so with only partial incidents the line is 20 (was 10, cause time). Published limits, 450 requests per 30 seconds on Scale and 150 on Growth and Core, refreshed every 30 seconds (15). A 429 carries X-Rate-Limit-Time-Reset-Ms and the docs advise waiting that long, then backing off exponentially. No idempotency keys for writes found (12). No SLA found (0). REST APIs are generally available, and the storefront MCP pages no longer carry a beta label, with the server switched on from the standard Settings, API and MCP page. The invite-only Store Management MCP beta isn't graded (10).); 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.)
- Schema & documentation, BigCommerce API + MCP +40: BigCommerce API + MCP 66 (Reference pages are built from API specs (a 29 September changelog entry corrected twenty of them), but the public spec repo was archived in December 2023 and its successor, bigcommerce/docs, still asked git for credentials on 2 October, so no current spec file was found (10). llms.txt hub linking a developer index of about 500 Markdown pages, plus a docs MCP server (10). Reference descriptions say what each call does, and the MCP tools are guest shopping steps (12). Typed REST parameters in the reference (11). Examples in the reference, but the developer index has no page on error responses (10). Dated changelog with entries almost daily, v2 and v3 REST paths, and a Deprecations and Sunsets page, though it gives no notice period (13).); 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.)
- Agent ergonomics, BigCommerce API + MCP +39: BigCommerce API + MCP 62 (The B2C storefront MCP reference lists 7 compact, shopping-only tools, and search_products pages with a cursor (23). REST listings take page and limit, with filters such as id:in, type and severity on the store logs endpoint, and the GraphQL Storefront API documents pagination (16). 429 handling is documented, but we found no error-format reference in the docs index (10). No idempotency keys, and the MCP reference documents no tool annotations (0). Guest MCP needs no key. Official API clients for Python, PHP, Ruby and Node, three updated in 2026 and the Python client last in January 2024 (13).); 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.)
- Transparency & trust, BigCommerce API + MCP +39: BigCommerce API + MCP 77 (Closed platform with published terms, now on commerce.com, and an open-source Catalyst storefront (15). The trust centre lists a DPA and a subprocessor document. The commerce.com privacy policy wasn't read in either pass (22). A Deprecations and Sunsets page lists deprecated v2 endpoints and three dated sunsets, the last on 3 June 2024, but the current deprecations carry no sunset dates and no notice period is stated (10). Subprocessor document listed and Google Cloud named as the host (18).); 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.)
- Security & auth, BigCommerce API + MCP +34: BigCommerce API + MCP 70 (API accounts issue a token limited by OAuth scopes chosen at creation and revocable by deleting the account, but tokens never expire and can't be rotated in place (24). Read-only scope variants, and the storefront MCP has no back-office tools, so a guest agent can only shop. The invite-only Store Management MCP beta adds OAuth 2.1 with PKCE, per-scope grants that start at none, products and promotions created hidden or disabled, and refunds only after a quote, but it isn't generally available, so it moves no line (16). The MCP returns merchant product content with no prompt-injection guidance found (5). The store logs API (GET /v3/store/systemlogs) keeps storefront events such as order status changes for 365 days, and the control panel keeps staff action logs (a status incident on 8 July names them). No per-call API log found (8). Trust centre lists PCI DSS Level 1 as merchant and service provider, SOC 1, SOC 2 and SOC 3, ISO/IEC 27001:2022 with 27017, 27018 and 27701, and a vulnerability disclosure programme run through Inspectiv. No security.txt (404 on 2 November) (17).); doola MCP 36 (OAuth with revocation; scopes not published (20 of 30). No read-only mode; no documented confirmation before a filing (3 of 20). Inputs are the user's own details (10). No audit log found (0). No security.txt or programme found (3 of 20). 20 + 3 + 10 + 0 + 3 = 36.)
- Payments & pricing, BigCommerce API + MCP +30: BigCommerce API + MCP 40 (No x402, MPP or L402 (0). Plan prices public, Core $39, Growth $105 and Scale $399 a month with GMV caps and 2.0, 1.0 and 0.6 per cent on orders through non-embedded providers, but nothing per call (10). 15-day free trial, and the pricing page says no credit card is needed (20). An agent can shop any store that has switched on the MCP as a guest with no key, but back-office access needs a person to create an API account (10).); 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.)