Head to head · Cms content · October 2026 research run
Contentstack vs DatoCMS
DatoCMS scores 74.4 (BB) on agent readiness against Contentstack's 64 (B), and leads in 6 of 7 scored categories. Both do cms content.
Which one, for what
Good for Teams already on Contentstack, or starting on its free plan, who want an agent to draft, localise, release and publish structured content with scoped credentials and an audit trail.
Also in its favour
- Runs on your own machine
Watch for
The MCP server's default group loads 78 tools, including nine deletes, with no readOnlyHint or destructiveHint annotations and no read-only switch
DatoCMS BB
Good for Teams on DatoCMS who want an agent to create, translate and publish records, upload assets or change models, testing first in a sandbox environment.
Ahead on
- Reliability, 80 against 71
- Schema & documentation, 85 against 77
- Agent ergonomics, 78 against 67
- Security & auth, 77 against 69
- Payments & pricing, 35 against 30
- Transparency & trust, 80 against 73
Also in its favour
- Agent-ready, a grade of BB or better
- No incidents deducted, where Contentstack loses 3 points for them
Watch for
No idempotency keys in the reviewed documentation. Safe retries rest on optimistic locking and the JavaScript client's automatic retry
Score by category
| Category | Weight this run | Contentstack | DatoCMS | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 71 | 80 | DatoCMS +9 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 77 | 85 | DatoCMS +8 |
| Agent ergonomics | 13%16.2 | 67 | 78 | DatoCMS +11 |
| Security & auth | 14%17.5 | 69 | 77 | DatoCMS +8 |
| Payments & pricing | 10%12.5 | 30 | 35 | DatoCMS +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 82 | 81 | Contentstack +1 |
| Transparency & trust | 7%8.8 | 73 | 80 | DatoCMS +7 |
| Negative events | ≤15 | -3 | 0 | |
| Total | 64 · B | 74.4 · BB |
Facts side by side
| Fact | Contentstack | DatoCMS |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Contentstack Inc. | Dato Srl |
| Hosted endpoint | https://api.contentstack.io | https://site-api.datocms.com |
| Transports | HTTP, stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Contentstack's Master Agreement and Terms of Service. The OpenAPI files, the management SDKs, the CLI and the @contentstack/mcp package are MIT | Proprietary service under Dato Srl's terms of service. The API clients in datocms/js-rest-api-clients and the CLI in datocms/cli are MIT |
| Tools exposed | 206 | 9 |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| Last release | 2026-09-22 | 2026-10-01 |
| Terms last updated | 2022-08-01 | couldn't be read |
| Privacy policy last updated | 2026-06-30 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 44k npm/wk, 1.5k PyPI/wk | 153k npm/wk |
Verdicts
Contentstack
The Content Management API has a public OpenAPI file, OAuth scopes that separate read, write and publish, read-only management tokens and a stack audit log. A free plan needs no card. The MCP server loads 78 tools by default with no annotations or read-only switch, and the limit=0 behaviour changed on 11 September 2026 without advance notice.
DatoCMS
The Content Management API publishes a JSON Hyper-Schema for 202 operations, 100 documented error codes and rate-limit headers, and the hosted MCP server adds OAuth with three access levels. There are no idempotency keys, the only official client library is JavaScript, audit logs are Enterprise only, and prices are in euros with no machine payment route.
Before you call either
Contentstack
- Pick the base URL for the stack's region first. North America on AWS is https://api.contentstack.io, and the other six regions use contentstack.com hosts
- Send
api_keyandauthorizationheaders on every Content Management API call. Ask for a read-only management token when the task only reads - Page with
limit(100 at most),skipandinclude_count=true.limit=0no longer returns everything - Stay under 10 reads and 10 writes a second per organisation, and one bulk request a second. Watch
X-RateLimit-Remainingand back off on 429 - Start the MCP server with
--groups cmaonly, and addcma-extendedwhen the task needs audit logs or version history. Publishing and deleting need no confirmation
DatoCMS
- Send
X-Api-Version: 3andAccept: application/jsonon every request, withContent-Type: application/vnd.api+jsonon writes - Records are
items, models areitem_typesand assets areuploadsin every path and payload - Save a record, then call the publish endpoint as a separate PUT. Send
meta.current_versionon updates and re-fetch onSTALE_ITEM_VERSION - Stay under 60 requests every 3 seconds. On 429 wait the seconds in
x-ratelimit-reset, and retry any error whose body hastransientset to true - Fork a sandbox environment for schema changes and promote it when checked. Use
POST /items/validateto test a payload without saving it
Questions
Which is better for AI agents, Contentstack or DatoCMS?
DatoCMS scores 74.4 (BB) on agent readiness against Contentstack's 64 (B), and leads in 6 of 7 scored categories.
Do Contentstack and DatoCMS need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Contentstack and DatoCMS without installing anything?
Yes. Contentstack has a hosted endpoint at https://api.contentstack.io and DatoCMS at https://site-api.datocms.com.
Other comparisons with Contentstack or DatoCMS
- Contentstack vs Directus
- Contentstack vs Ghost
- Contentstack vs Payload
- Contentstack vs Sanity
- Contentstack vs Storyblok
- Contentstack vs Strapi
- Contentstack vs Webflow
- Contentstack vs WordPress
- DatoCMS vs Directus
- DatoCMS vs Ghost
- DatoCMS vs Payload
- DatoCMS vs Sanity
- DatoCMS vs Storyblok
- DatoCMS vs Strapi
- DatoCMS vs Webflow
- DatoCMS vs WordPress
Machine-readable
- This page as Markdown
/compare/contentstack-vs-datocms.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/contentstack.json·/api/v1/tools/datocms.json - From a terminal
anchor compare contentstack datocms(the CLI) - Over MCP
compare_tools {"a": "contentstack", "b": "datocms"}at/mcp, no key