BCMS vs Contentstack

BCMS 15

Graded on BCMS Cloud with the hosted lines. No status page was found (0) and no incident history could be read (5). The terms refer to rate limits, but no numbers were found in the docs (0). No 429 or retry guidance was found (0). No SLA; Enterprise is by quote (0). The MCP server card says version 3.0.0 and nothing is labelled beta (10). 0+5+0+0+0+10 = 15.

Contentstack 81

Read with the hosted lines and scored on the Content Management API. status.contentstack.com is a Statuspage site with components by cloud, region and service and a full incident history (20). history.atom, read on 2 November, lists five incidents touching the product from 4 August to 2 November 2026, each confined to one region. Webhook delivery on AWS Europe stopped on 28 August for every customer in that region, with publishing unaffected (posted 11:16 to 12:15 UTC, though the post says investigation began around 08:00 UTC). Publishing and webhooks were delayed on Azure Europe on 1 September (51 minutes) and 16 September, newly published content was delayed on Google Cloud North America on 19 September, and Custom Agents, Polaris and Automation were disrupted on Google Cloud North America on 10 October. Two outages of the support portal and live chat (16 September and 22 October) didn't touch the APIs. The 7 October reading came from the page's /api/v2/incidents.json, which the host's robots.txt disallows, so it is struck. That reading counted the 28 August webhook outage as a major (10). This run reads an incident limited to one region or one service as partial and minor, so minor incidents only (20). Rate limits have numbers, 10 reads and 10 writes a second per organisation and one bulk request a second (15). The docs say a 429 is returned and name X-RateLimit-Limit and X-RateLimit-Remaining. Adaptive Rate Limiting (13 October 2026) adds Retry-After on 429s, but only for the Content Delivery, Image Delivery and GraphQL delivery APIs and only in an Early Access Program on request. No Retry-After, backoff guidance or idempotency key was found for the Content Management API (6 of 15). The Services Description commits to 99.50 or 99.95 per cent monthly availability by plan, with service credits (10). The v3 API is generally available. The MCP server is at version 0.9.0 (10). 20+20+15+6+10+10 = 81.

BCMS 16

@thebcms/client 2.0.3 was published on 16 March 2026, more than 180 days ago, and no dated API or MCP change was found. The terms of 30 July 2026 and the 3.0.0 server card show the product is current, so 5 of 30. No dated releases or changelog entries in the last 90 days (0). No public changelog; support by contact form (4 of 25). Not in the official MCP registry; one current JavaScript client (4 of 15). The client hasn't been released since March (3 of 10). 5+0+4+4+3 = 16.

Contentstack 82

The changelog's newest entry is 30 October 2026 (Polaris in the Visual Editor), after CLI 2.0.2 and 1.69.0 on 21 October with bug fixes, and the JavaScript management SDK 1.31.2 (changelog 22 September, tag 5 October) only resolved dependency vulnerabilities (30). Dated entries from 4 August to 2 November include the limit change on 11 September, recursive embedded items on 7 September, Adaptive Rate Limiting on 13 October, Java management SDK 1.13.1, 1.14.0 and 1.14.1 (17, 24 and 31 August) and Python management SDK 1.11.2 (10 August) (20). Closed service with a public changelog and RSS feed, email support and a Discord community. We didn't test a support channel (10 of 15). Official management SDKs in four languages, all with releases since 27 July 2026. The MCP server isn't in the official MCP registry (15). The JavaScript SDK repository has unit-test, CodeQL and dependency-scan workflows, and its changelog shows regular dependency fixes. We didn't see the CI results (7 of 10). 30+20+10+15+7 = 82.

BCMS 36

45 MCP tools, more than 30 (5). We added 3 because keys without schema permission hide the schema tools (8 of 25). No pagination or filter parameters were found in the docs read (6 of 20). Error guidance covers 403 and permission errors only (8 of 20). Annotations weren't readable; entry history and trash give a way back, and the docs say to list and confirm ids before deletes (6 of 20). One JavaScript client and a CLI (8 of 15). 8+6+8+6+8 = 36.

Contentstack 67

Responses can be sized with only[BASE][], except[BASE][] and limit. The MCP server's default group is 78 tools and about 66 KB of schema, split from nine other groups by --groups (17 of 25). limit up to 100, skip, include_count, sort and a JSON query filter (20). Errors use standard status codes with a JSON body, with 412 and 422 explained in the docs. Error bodies aren't in the spec (12 of 20). No idempotency keys or conditional writes were found, and the MCP package contains no readOnlyHint or destructiveHint annotations. Entries keep version numbers, which helps check a write after a lost response (4 of 20). Management SDKs in JavaScript, Python, Java and .NET. Every call needs two headers and the right regional host (14 of 15).

BCMS 39

Keys are scoped per template and media and can be revoked and rotated (25), less 10 because the MCP key is accepted only as ?mcpKey= in the URL and REST examples pass apiKey the same way (15 of 30). Scoped keys, schema tools gated by key, and scoped delete permission; no approval step (12 of 20). Entries hold text written by people and no prompt-injection guidance was found (3 of 15). Entry history and log history (2 days on Hobby, 30 on Pro) let the operator see what an agent changed (9 of 15). No security.txt, disclosure policy or certification was found (0). 15+12+3+9+0 = 39.

Contentstack 69

OAuth 2.0 with scopes per module and action (cm.entry:read, cm.entry:write and cm.entry:publish are separate), 60-minute tokens, a refresh grant and revocation by users or organisation admins. Management tokens can be read-only, branch-limited and expiring, and are shown once. PKCE isn't mentioned in the OAuth docs (27 of 30). Read-only tokens and separate publish scopes allow least privilege, and stacks have workflows and publish rules. The MCP server has no read-only switch and no confirmation step, and its default group includes nine delete tools (13 of 20). Entries are written by a stack's own users and can still carry instructions. No prompt-injection guidance was found in the MCP docs (3 of 15). A stack audit log records creates, updates, deletes and publishes by user, with an API endpoint and MCP tools to read it. Its retention period isn't stated (13 of 15). SOC 2 Type II, ISO 27001:2022 and penetration tests twice a year. Reports go to security@contentstack.com with a stated 24-hour response, and SDK security fixes are listed in the changelog with CVE numbers. security.txt returns 404 and no bug bounty was found. We didn't search NVD (13 of 20).

BCMS 50

The docs link an OpenAPI reference at app.thebcms.com/open-api-docs, but that host's robots.txt disallows every path, so it wasn't read. The MCP tool schemas need a session (10 of 25). llms.txt, docs llms.txt, llms-full.txt, Markdown pages and a public SKILL.md (10). llms.txt says when to use BCMS and when not to, and the MCP page gives each tool group's purpose (12 of 20). Input typing couldn't be checked (5 of 15). Curl and JavaScript examples, and troubleshooting for 403 and permission errors (7 of 15). API v3 paths and a 3.0.0 server card, with no changelog found (6 of 15). 10+10+12+5+7+6 = 50.

Contentstack 79

An OpenAPI 3.0.0 file for the Content Management API is public, with 138 paths and 221 operations, and every MCP tool has a JSON Schema published at mcp.contentstack.com (25). www.contentstack.com/llms.txt indexes the docs, the full-text export llms-full.txt answered on 2 November (about 25 MB, it returned 502 on 7 October), and doc pages are served as Markdown at their .md path (10). Operation descriptions in the spec are long (median 1,189 characters, in HTML) and MCP tool descriptions say what each tool does (median 142 characters in the cma group). Few say when not to use a tool (15 of 20). The spec has no enums and no component schemas, and request bodies are examples. The cma tool schemas have 369 properties with two enums and 13 untyped objects such as entry_data. Version 0.9.0 says it adds enums from the connected stack at run time, which we couldn't see without an account (7 of 15). The spec carries 494 examples but documents only a 200 response for each operation. The docs list status codes in a table (9 of 15). The API version is in the path, and a dated changelog with an RSS feed covers API, SDK and CLI changes. A behaviour change to limit shipped inside v3 (13 of 15). 25+10+15+7+9+13 = 79.

BCMS 52

A closed service with terms of 30 July 2026; the old open-source edition is MIT but unmaintained (15 of 30). Terms and privacy policy of 30 July 2026 agree, name providers such as Stripe and OAuth sign-in, and describe retention in general terms with backups rotating out (18 of 30). The open-source repository's end of maintenance is dated; no API deprecation policy (5 of 20). Providers are named by purpose without data locations (10 of 20). 15+18+5+10 = 48.

Contentstack 74

The service is closed under a Master Agreement last updated 17 July 2026 and Terms of Service from August 2022. The spec, SDKs, CLI and MCP package are MIT, though the MCP repository named on npm isn't public (15). The privacy policy of 30 June 2026 says customer content is deleted within 180 days of termination, data processing agreements for the US and for EMEA are published, and the AI addendum of 27 July 2026 says customer data isn't used to train general AI models. The older Terms of Service only say access to content ends on termination (24 of 30). No deprecation policy with a notice period was found. The Services Description lets Contentstack end a service during a term with a pro-rata refund, and the limit change was announced on the day it applied (5 of 20). The sub-processor list was updated on 25 May 2026 with purposes and locations. It gives the United States for Azure and Google Cloud although both have European regions in the API docs, and the page states no notice period for changes (15 of 20).