Designed to fail safely.
Content automation should make routine work faster without turning one malformed request into a damaged page.
The source is read-only
There is no MCP tool for updating, deleting, or publishing a source page. Writes target a new or service-owned draft.
Every write has a revision
Source and draft hashes stop stale operations. If content changed after inspection, the request stops.
Retries are deterministic
Idempotency keys prevent retries from creating duplicate drafts or applying a different operation.
Results are fetched again
After a write, Safe Strapi fetches the full draft and compares it with the intended payload.
Ownership is enforced
A draft must exist in the ownership registry before modification tools can touch it.
Publishing stays human
The service never publishes. Editors retain the final review and release decision in Strapi.
Strapi tokens stay in server-side secrets and are never returned through MCP. Client keys should be distributed through a password manager and rotated when access changes.