Contentstack vs Kontent.ai

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.

Kontent.ai

Management API keys take per-area permissions, environment limits and an expiry from one minute to two years, and changes made with a key are named in the audit log. Rate limits and Retry-After are documented. No price is published, and no OpenAPI file was found. Access starts with a 30-day trial that a person opens in a browser.

Contentstack

1. 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
2. Send api_key and authorization headers on every Content Management API call. Ask for a read-only management token when the task only reads
3. Page with limit (100 at most), skip and include_count=true. limit=0 no longer returns everything
4. Stay under 10 reads and 10 writes a second per organisation, and one bulk request a second. Watch X-RateLimit-Remaining and back off on 429
5. Start the MCP server with --groups cma only, and add cma-extended when the task needs audit logs or version history. Publishing and deleting need no confirmation

Kontent.ai

1. Send Authorization: Bearer <key> to https://manage.kontent.ai/v2/projects/{environment_id}/.... The Management API must be switched on under Environment settings, General, Enabled APIs first
2. Ask for a Management API key with only the permissions the task needs. Read content alone gives a read-only key, and keys expire after six months by default
3. Stay under 10 requests a second and 400 a minute per environment, send requests one at a time, and wait the seconds in Retry-After on a 429
4. Page lists by passing the continuation_token from the response back in the x-continuation header
5. Create items with an external_id and write with the upsert PUT at /items/external-id/{id} so a retry after a lost response does not create a duplicate
6. With the MCP server, call get-patch-guide before any patch tool, and use a client that prompts on destructiveHint