Prismic vs Webflow

Prismic

The hosted MCP server stages every write as a draft in a release, cannot delete, and publishes only when a user with the Publisher role asks. Write tokens for the Migration, Asset and Types APIs have no scopes, no OpenAPI file was found, writes are limited to one request a second, and the acceptable use policy forbids access by scripts.

Webflow

The Data API has a public OpenAPI 3.1 spec with 140 operations, scoped OAuth and site tokens, and CMS items that stay drafts until a separate publish call. The MCP server loads 34 multi-action tools and can't create new localised CMS items. The free plan holds 50 CMS items, and the activity log needs the $2,500 Team plan.

Prismic

1. Ask a repository Administrator to activate Prismic MCP in Settings first. Activation can take several minutes, and each environment has its own setting
2. Call list_repositories, then get_custom_type or get_shared_slice for the empty content template before create_document
3. Create a release with create_release and write into it. Call publish_release only on an explicit request, because a publish cannot be undone through MCP
4. For the Migration API send Authorization: Bearer <write token> and a repository header, one page a request, one request a second, and keep each returned id for later PUT calls
5. Upload media first (upload_asset or POST to https://asset-api.prismic.io/assets) and reference the asset id in image and media link fields

Webflow

1. Send the token as Authorization: Bearer to https://api.webflow.com/v2. Ask for cms:read and cms:write only, plus sites:write if the task publishes
2. Create or update items first, then call Publish Items or Publish Site. An item with isDraft true and a lastPublished date is live with unpublished changes
3. Stay under 60 requests a minute on Starter and Basic and 120 on Premium, read X-RateLimit-Remaining, and wait for Retry-After on 429
4. Page item lists with limit (maximum 100) and offset, and filter with filter[<fieldSlug>][<operator>], up to 10 terms
5. Upload an asset in two steps (create the asset with a file hash, then POST the bytes to the presigned URL). Write localised content with the item's cmsLocaleId