Niches · CMS & website publishing
Create or change the content model
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
The model changes in a sandbox or branch first, existing entries still validate (or are migrated in the same job), validators survive the change, and the schema read back matches the repository format.
How agents ask for it: add an author field to posts
, create a collection for events
, set up a CMS for this site
, rename this field across all documents
Does the job, with a limit 14
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| BCMS F Becomes tech, LLC | create-template and update-template work over MCP, but no sandbox or branch flow and no code export format are documented. source |
| Contentstack B Contentstack Inc. | Content types can be created, exported and compared across branches, a sandbox in effect, but acc-28 shows the MCP's content type JSON differs from the CLI export. source |
| Cosmic BB Cosmic Inc. | cosmic_types_create and cosmic_types_update edit object types, but no sandbox, branch or environment for trying a change first is documented. source |
| DatoCMS BB Dato Srl | Sandbox environments fork and promote, and CLI migrations script the change, but no schema export in a repository format was found to compare a read-back against. source |
| Directus C Monospace Inc. (doing business as Directus) | collections, fields and relations tools change the model over MCP, but no sandbox or branch environment is documented, so changes land on the live instance. source |
| dotCMS C dotCMS LLC | The token must hold content-type write permission and execute can change types, but no sandbox flow or export format comparison was found in the pages read. source |
| Hygraph B Hygraph GmbH | submit_batch_migration applies changes in one transaction with dry_run, per environment, but no code export format exists to compare against a repository copy. source |
| Kontent.ai BB Kontent CZ s.r.o. | create-content-type and patch-content-type use move, addInto, remove and replace operations, but sandbox environments and export parity weren't covered in the pages read. source |
| Payload D Payload CMS, Inc. | The model is TypeScript in the repository, so a branch is the sandbox and validators are code; changes go through the codebase and a deploy, not the API or MCP. source |
| Prismic C Prismic.io Inc. | The MCP only reads custom types and shared slices; changes go through the Types API or Slice Machine in the repository, outside the MCP. source |
| Sanity BB Sanity US Inc. (with Sanity AS) | schema_fields_patch takes a schemaVersion for concurrency and datasets can act as sandboxes, but acc-26 shows a serialised schema losing the slug uniqueness validator and blocking every publish. source |
| Storyblok B Storyblok GmbH | Components are Management API resources the MCP can write, and environments mirror a space for testing, but export parity with the CLI's component files wasn't checked. source |
| Strapi BB Strapi, Inc. | Content types are JSON schema files in the project and the MCP only generates tools from them; changing the model means editing code and restarting, not an API call. source |
| Webflow BB Webflow, Inc. | Collections and static, option and reference fields can be created and updated, but there is no CMS sandbox; page branches cover pages only and need Enterprise. source |
Doesn't do this job 4
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| ButterCMS D ButterCMS LLC | The spec says page types and collections must be configured in the dashboard; the API cannot create them. source |
| CookieYes MCP Server D CookieYes Limited | No content model. source |
| Ghost C Ghost Foundation Ltd | Ghost has fixed post and page types with no custom content types or fields to model. source |
| WordPress B WordPress.org, an open-source project. The WordPress trademark belongs to the WordPress Foundation | Post types and fields are registered in PHP code; the REST API reads them but can't create or change them. source |
What stops agents finishing
- validators that are code are lost when the schema is serialised
- no sandbox environment on the plan
- schema permission bundled into a broad token
Around it
Before: code.read-repo. After: cms.migrate-content, cms.draft-post.
Where this comes from
Weight 6 of 100 in CMS & website publishing: 3 of 39 accounts; vendors (Sanity, Cosmic, Hygraph, DatoCMS) push this harder than users report it
The same as data: /api/v1/use-cases/cms.change-schema.json, or the MCP tool get_use_case with id cms.change-schema. Other jobs in this category: /api/v1/niches?category=cms.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.