# BCMS vs Kontent.ai (slim)

> Kontent.ai scores 70.6 (BB) to BCMS's 33.5 (F) for content management. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/bcms-vs-kontent-ai.md (~5,150 tokens) · this version ~3,230 tokens · JSON https://www.anchorterminal.com/compare/bcms-vs-kontent-ai.json · canonical https://www.anchorterminal.com/compare/bcms-vs-kontent-ai
- 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)

Kontent.ai scores 70.6 (BB) on agent readiness against BCMS's 33.5 (F), and leads in 6 of 7 scored categories. BCMS leads on payments & pricing. Both do content management.

- BCMS: F 33.5, rank #1383 of 1486 · https://www.anchorterminal.com/tools/bcms.min.md
- Kontent.ai: BB 70.6, rank #193 of 1486 · https://www.anchorterminal.com/tools/kontent-ai.min.md
- BCMS, good for Small sites and agencies that want a cheap hosted CMS an agent can edit. Ahead on Payments & pricing, 30 against 20.
- Kontent.ai, good for A company already on Kontent.ai, or evaluating it on a trial, that wants an agent to draft, localise, move through workflow and publish structured content with a permission-limited key and an audit trail. Ahead on Reliability, 82 against 15; Schema & documentation, 74 against 50; Agent ergonomics, 71 against 36; Security & auth, 81 against 39; Maintenance & community, 83 against 16; Transparency & trust, 76 against 52. Also Agent-ready, a grade of BB or better; Runs on your own machine.

| Category | BCMS | Kontent.ai |
| --- | --- | --- |
| Reliability (16%) | 15 | 82 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 50 | 74 |
| Agent ergonomics (13%) | 36 | 71 |
| Security & auth (14%) | 39 | 81 |
| Payments & pricing (10%) | 30 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 16 | 83 |
| Transparency & trust (7%) | 52 | 76 |

| Fact (where they differ) | BCMS | Kontent.ai |
| --- | --- | --- |
| Vendor | Becomes tech, LLC | Kontent CZ s.r.o. |
| Hosted endpoint | `https://app.thebcms.com/api/v3/mcp` | `https://manage.kontent.ai/v2` |
| Transports | HTTP, Streamable HTTP | HTTP, stdio, Streamable HTTP |
| Licence | none | Proprietary service under the Kontent.ai Terms of Service. The management SDKs for JavaScript and .NET and the MCP server on GitHub are MIT |
| Tools exposed | 45 | 54 |
| Read-only variant documented | no | yes |
| MCP registry | not listed | `io.github.kontent-ai/mcp-server` |
| Last release | 2026-03-16 | 2026-10-30 |
| Terms last updated | 2026-07-30 | 2026-09-11 |
| Privacy policy last updated | 2026-07-30 | 2025-06-02 |
| Terms restrict benchmarking | not found in the text | yes |
| Popularity | 396 npm/wk | 8.4k npm/wk |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Reliability, Kontent.ai +67: 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.); Kontent.ai 82 (Read with the hosted lines and scored on the Management API. status.kontent.ai is a Statuspage site with components by region, the Management REST API among them, and an incident history (20). Re-read on 1 November, its feed lists three incidents between 3 August and 1 November 2026. The GraphQL service was disrupted for about 31 minutes on 16 September with the Management API unaffected, content item saves failed for about 40 minutes on 24 September for a subset of EU projects using regex validation, and requests to the deprecated `*.kenticocloud.com` domain pattern failed from 13:30 to 16:06 UTC on 20 October after a registrar change. Each hit one service or a subset of requests, so we read them as minor. The 29 July login incident has left the window (20). Rate limits have numbers, 10 requests a second and 400 a minute per environment, re-read on 1 November (15). A 429 carries Retry-After, the docs call each failed request safe to retry and ask for a retry policy on 5xx. There are no idempotency keys, though the upsert PUT by external ID repeats safely (13 of 15). Annex 4 of the terms defines availability with a refund formula, but the guaranteed level is in each order form and the definition names the administration interface and the Delivery API, not the Management API (4 of 10). Management API v2 is generally available. The open-source MCP server is at 0.39.0, and Kontent.ai has hosted it at manage-mcp.kontent.ai since 22 October (10).)
- Maintenance & community, Kontent.ai +67: 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.); Kontent.ai 83 (The newest product update is dated 30 October 2026 (Aiko Agent and Expert agents generally available), after the hosted MCP server on 22 October, and the JavaScript SDK repository's last commit is 22 October (30). Nine product updates fall between 3 August and 1 November 2026, from 14 August to 30 October. The MCP server tagged 0.38.0 (11 August), 0.38.1 (18 August) and 0.39.0 (31 August), and the JavaScript SDK 8.5.5 (18 August), 8.5.6 and 8.5.7 (21 September) (20). Closed service with a dated changelog and RSS feed, in-app chat stated as 24/7 on all plans and a Discord community. We did not test a support channel (11 of 15). Official SDKs for JavaScript and .NET (.NET 8.3.1 tagged on 17 July 2026), and the official MCP registry lists io.github.kontent-ai/mcp-server with 0.39.0 as the latest active version, read on 1 November (15). The repositories have build and test workflows and pinned, recent dependencies. We did not see CI results (7 of 10).)
- Security & auth, Kontent.ai +42: 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.); Kontent.ai 81 (Management API keys have selectable permissions, environment limits, an expiry from 1 minute to 2 years (6 months by default), email reminders before expiry and revocation by regenerating. Keys travel only in the `Authorization` header, and the hosted MCP server takes a Management API key in that header and rejects personal keys. There is no OAuth (27 of 30). A key can be read-only, the API follows the workflow transition rules, and the MCP server marks 22 tools destructive so a client can prompt. Neither surface has its own confirmation step (15 of 20). Content is written by a project's own users and can carry instructions. The MCP README and, since the hosted server, the MCP docs page warn about prompt injection and recommend a least-privilege key. The API docs say nothing on it (10 of 15). The audit log keeps 90 days and names the API key behind each change, with content item changes included since 2 October 2026. No API for reading it was found (12 of 15). security.txt is valid to 21 July 2027, re-read on 1 November, the disclosure policy has a safe harbour and discretionary rewards, a penetration testing policy lets customers test, and the trust centre lists SOC 2 Type 2 and ISO 27001, 27017, 27018 and 42001. Reports are gated and no public advisories were found. We did not search NVD (17 of 20).)
- Agent ergonomics, Kontent.ai +35: 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.); Kontent.ai 71 (Scored on the API. No field selection on Management API reads was found, and the docs send filtering to the Delivery APIs. A filter endpoint returns references only and a bulk-get endpoint fetches the chosen items. The MCP server at 0.39.0 loads 54 tools. The hosted server's tool list wasn't read, because its robots.txt disallows every path (13 of 25). Lists page by continuation token, and items with variants can be filtered. No page-size control was found (14 of 20). Errors carry a request ID, a code, a message and validation errors with path, line and position (17 of 20). No idempotency keys. Items can be addressed and upserted by external ID or codename, the docs say failed requests are safe to retry, and they advise against parallel requests. All 54 MCP tools in 0.39.0 set readOnlyHint and destructiveHint (13 of 20). Two official SDKs, JavaScript and .NET, and a call needs only the environment ID and a key (14 of 15). The API reference is per the 9 October check, not re-read on 1 November.)
- Schema & documentation, Kontent.ai +24: 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.); Kontent.ai 74 (No OpenAPI file was found on the docs pages read. The reference links a Postman collection in a public workspace, which we did not read, and the MCP server's tools have typed schemas in its source (15 of 25). kontent.ai/llms.txt exists and is an index of marketing and docs pages. No Markdown copies of the docs were found, only PDF downloads (5 of 10). Each endpoint states its purpose and its limits, for example that scheduling a published variant has no effect and which endpoint to use instead (15 of 20). Attributes are typed with required, read-only and write-only flags, formats and length limits. Element values vary by element type (12 of 15). Each operation has request samples in TypeScript, C# and cURL, response status codes and an error object with validation paths (13 of 15). The version is in the path, product updates are dated with an RSS feed, breaking changes can be had by email, and a page lists which changes are not treated as breaking (14 of 15). The reference pages are per the 9 October check, not re-read on 1 November.)
- Transparency & trust, Kontent.ai +24: 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.); Kontent.ai 76 (The service is closed under Terms of Service effective 11 September 2026, re-read on 1 November. The SDKs and MCP server are MIT (15). The terms include a Data Processing Addendum and an AI annex that rules out training on customer content, and the privacy policy of 2 June 2025 covers product users. The periods differ by document. Content is kept 30 days after a subscription ends, the addendum says personal data is returned or deleted within 14 days, and the privacy policy keeps account data up to 90 days (23 of 30). No deprecation policy with a notice period was found. Removals are announced with dates, such as Sitemap on 14 July for 30 September 2026, and the terms give 14 days to object to a material change. The hosted MCP docs say only the latest server version runs, so tool names and behaviour can change between versions (13 of 20). The sub-processor page names each vendor with its address, location and the data sent, Anthropic and Microsoft among them, and the four data centre regions are documented, per the 9 October check, not re-read on 1 November (18 of 20).)