Niches · CMS & website publishing
Publish a change and confirm it is live, or roll it back
Two or three companies' docs show a full fit.
What counts as done
Each entry reads as published through the delivery API and the public URL shows the new content; a rollback restores the previous revision's content through the API; nothing outside the approved set goes live.
Measured, for our own tests: the public URL shows the new content within 60 seconds, and the rollback takes at most two calls. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: publish it
, is it live yet
, put the old version back
, schedule this for Monday 9am
Does the job 3
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Contentstack B Contentstack Inc. | publish_an_entry and deploy_a_release publish per environment and take a version, so an older version can be republished; whether front-end caches refresh is outside the docs read. source |
| DatoCMS BB Dato Srl | Publish is a separate call, the Delivery API serves published versions by default, and itemVersions.restore rolls back; how fast the owner's site refreshes isn't in the docs. source |
| WordPress B WordPress.org, an open-source project. The WordPress trademark belongs to the WordPress Foundation | status publish puts a post live on the site, and a rollback is a GET of the revision then a POST of its content, but caching plugins decide how fast the public URL changes. source |
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 | Publishing means setting a status the front end filters on, plus a webhook for rebuilds; entry history is read-only over MCP with no restore tool. source |
| ButterCMS D ButterCMS LLC | status=published publishes posts and pages, but collection items created as drafts must be published in the dashboard, and no revision or restore route exists. source |
| Cosmic BB Cosmic Inc. | Status update publishes and webhooks fire with trigger_webhook; rollback means reading a revision, posting it as a draft revision and publishing, three calls, and dashboard restore is a paid add-on. source |
| Directus C Monospace Inc. (doing business as Directus) | Publishing a version is POST /versions/{id}/promote over REST only, since the MCP refuses directus_versions; revisions are kept but no single restore route was found. source |
| dotCMS C dotCMS LLC | The PUBLISH action and push-publishing bundles publish content; Bring Back restores versions in the editor, and no API route for it was found. source |
| Ghost C Ghost Foundation Ltd | A PUT with status published puts the post live on Ghost's own site, and save_revision stores a revision, but no documented route restores one. source |
| Hygraph B Hygraph GmbH | publish_entry publishes from DRAFT, but unpublish is rejected over MCP, no mutation restores a version, and Hobby has no version history. source |
| Kontent.ai BB Kontent CZ s.r.o. | publish-content-item-variant publishes or schedules and the published version can be read apart from the draft, but no tool restores an earlier version. source |
| Payload D Payload CMS, Inc. | _status published publishes and restoreVersion rolls back, but acc-20 shows MCP publishes skipping cache revalidation, so the live page keeps old content with no error. source |
| Prismic C Prismic.io Inc. | publish_release puts a whole release live, but it is irreversible through MCP, needs a Publisher role, and migration releases can't be published over MCP. source |
| Sanity BB Sanity US Inc. (with Sanity AS) | publish_documents and releases publish precisely the approved set, but the MCP has no tool to restore an earlier revision. source |
| Storyblok B Storyblok GmbH | The publish endpoint is reachable, but the MCP can't read the Content Delivery API to confirm what's live, and version history is 1 day on Starter. source |
| Strapi BB Strapi, Inc. | publish_<slug> publishes and discard_<slug>_draft reverts unpublished changes, but no tool restores an earlier published version. source |
| Webflow BB Webflow, Inc. | publish_collection_items and publish_site put changes live on Webflow hosting, but acc-25 shows the MCP can't read live items to confirm, and no tool restores an earlier version. source |
Doesn't do this job 1
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| CookieYes MCP Server D CookieYes Limited | Can check whether a banner is live (get_banner_status) but publishes no content and has no revisions. source |
What stops agents finishing
- publish saves but cache revalidation never runs, with no error
- no API route to restore a revision (WordPress, Ghost, ButterCMS, Hygraph)
- revision history shorter than a day on the free plan (Storyblok Starter) or absent (Hygraph Hobby)
- site publish limited to one a minute (Webflow)
Around it
Before: cms.draft-post, cms.edit-in-place, cms.bulk-audit-fix. After: web-scrapers.page-to-markdown, notifications.send.
Where this comes from
Weight 11 of 100 in CMS & website publishing: 5 of 39 accounts, raised by 1 because every Building benchmark check reads the finished live site
The same as data: /api/v1/use-cases/cms.publish-and-verify.json, or the MCP tool get_use_case with id cms.publish-and-verify. 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.