The Detail
Department

The Detail Department / Content and commerce

The AI CMS Index

Use AI to draft, edit and publish content. Compare daily tasks, limits and the work needed to connect your CMS.

MCP connects an assistant to a tool. An API-only route needs a developer to build the connection.

Explore the AI Media Index

Find a tool for the task

Readiness What the labels mean

Even “Production” needs the setup shown. These are documentation assessments, not claims of workflows we have run.

10 tools shown

01

Commerce content

4 tools in this field.

Back to index start
Commerce content: daily tasks, limits and setup
ToolWhat you can doLimits and checksGetting started

Shopify

Admin GraphQL API, custom integration

Grade BTest
  • Create a blog article or information page.
  • Set its publication status or schedule when creating it.

Review the copy and check the storefront after publication. Translation and editorial approvals need their own workflow.

Developer setup

A developer must create an authenticated app, grant content permissions and build the assistant’s API connection.

Admin API setup guide for Shopify
Sources, capabilities and assessment for Shopify

Documentation reviewed .

Supported actions

Read
Unverified
Draft
Yes
Edit
Unverified
Publish
Yes
Localise
Unverified

Create articles and pages with publication settings. This review does not establish a turnkey editorial MCP or general store-management coverage.

Why this grade

  • Documented article and page creation with publication settings.
  • Explicit API scopes provide a configurable access boundary.

Limits

  • Requires an app and custom integration work.
  • Editing, deletion and localisation are not verified by the creation endpoints assessed here.

Check the sources

Official route documentation Page creation and publication Developer AI toolkit

WooCommerce

Official Abilities and MCP Adapter, developer preview

Grade BTest
  • Find products for a content review.
  • Create or update the product fields exposed by the store’s Abilities.

The connection is a developer preview. Version 11.3 changes older connections; check support for extension fields and languages separately.

Admin setup

A site administrator installs the MCP Adapter and creates a limited WordPress application password. Check the installed WooCommerce version and its Abilities before connecting.

Connection documentation for WooCommerce
Sources, capabilities and assessment for WooCommerce

Documentation reviewed .

Supported actions

Read
Yes
Draft
Unverified
Edit
Yes
Publish
Unverified
Localise
Depends

Product query, creation, updates and deletion are documented. Editorial fields depend on the exposed Ability schemas.

Why this grade

  • Official product operations use WordPress permission checks.
  • The adapter can expose supported store tasks directly to an assistant.

Limits

  • The integration remains developer preview.
  • Version changes, extension fields and publication behaviour need a store-level test.

Check the sources

WooCommerce MCP integration Version 11.3 migration advisory Version 11.3 beta status

BigCommerce

Pages V3 and Blog Content APIs

Grade BTest
  • Update information pages and their metadata.
  • Create, edit and publish blog posts.

Review changes before writing, then check the storefront. Your integration must handle each channel’s content and language conventions.

Developer setup

A developer must create a store API account, grant content permissions and build the connection to the assistant.

API account setup for BigCommerce
Sources, capabilities and assessment for BigCommerce

Documentation reviewed .

Supported actions

Read
Yes
Draft
Partial
Edit
Yes
Publish
Partial
Localise
Depends

Read, create, edit and delete pages or blog posts. Blog posts have a publication flag; page visibility is not a complete editorial approval workflow.

Why this grade

  • Documented page and blog operations cover recurring content edits.
  • Blog publication is explicit in the API.

Limits

  • Requires a custom authenticated integration.
  • Page visibility and blog publication have different semantics.

Check the sources

Pages V3 Official blog Content API schema

Adobe Commerce / Magento

CMS REST API, PaaS or on-premises

Grade BTest
  • Update CMS page copy and reusable content blocks.
  • Prepare page changes and set the page’s active state.

Check the rendered page and use the editor for visual Page Builder work. This assessment does not establish a complete approval process or Adobe Commerce SaaS feature parity.

Developer setup

A developer must configure an integration with CMS permissions and connect it to the assistant. The team must confirm the store’s version, deployment type and content conventions.

API documentation for Adobe Commerce / Magento
Sources, capabilities and assessment for Adobe Commerce / Magento

Documentation reviewed .

Supported actions

Read
Yes
Draft
Partial
Edit
Yes
Publish
Partial
Localise
Depends

Read, create, update and delete CMS pages and blocks. Page content and activation are separate fields; storefront delivery still needs a check.

Why this grade

  • Explicit CMS page and block operations.
  • CMS access is controlled through integration permissions.

Limits

  • Requires custom engineering and deployment-specific checks.
  • An API write does not prove the storefront or Page Builder layout is correct.

Check the sources

Adobe Commerce REST API overview CMS API routes CMS page content and activation fields

02

CMS and site builders

3 tools in this field.

Back to index start
CMS and site builders: daily tasks, limits and setup
ToolWhat you can doLimits and checksGetting started

WordPress.com

Official hosted MCP

Grade B+Test
  • Create a draft post and edit supported page content.
  • Publish approved posts through the tools enabled for the site.

Review changes before sending them: edits to a published post can go live immediately. Account tool settings are shared across connected assistants.

Sign in and connect

Enable account MCP, connect with OAuth and select tool access; availability varies by plan, host and user permissions.

Connection documentation for WordPress.com
Sources, capabilities and assessment for WordPress.com

Documentation reviewed .

Supported actions

Read
Yes
Draft
Yes
Edit
Yes
Publish
Yes
Localise
Depends

Documented post and page operations support drafts, updates and publication. Inspect the live tool catalogue for the connected site.

Why this grade

  • Draft creation and post-section editing are documented.
  • Existing WordPress roles and tool controls govern access.

Limits

  • Tool availability varies by site, plan and account settings.
  • Shared account-level settings need review before enabling writes.

Check the sources

Official route documentation WordPress.com tool reference

Webflow

Official Webflow MCP

Grade B+Test
  • Update CMS items and supported page content.
  • Edit existing secondary-language items where the tool supports them.

New items in secondary languages still need another route. Some actions also require the right site role or an open Designer session.

Admin setup

Authorise the right workspace and site role. Some design operations also need the Designer and its bridge app open.

Connection documentation for Webflow
Sources, capabilities and assessment for Webflow

Documentation reviewed .

Supported actions

Read
Yes
Draft
Yes
Edit
Yes
Publish
Unverified
Localise
Partial

Manage CMS collections and items, with partial localisation and additional design tools. Scope publication tools to the connected site.

Why this grade

  • Combines structured content and site-design operations.
  • Uses existing site permissions and roles.

Limits

  • New localised CMS items are not supported through this route.
  • Some visual operations require the Designer, and new site creation stays in the dashboard.

Check the sources

Official route documentation Webflow MCP limitations and localisation

WordPress MCP Adapter

Official adapter and registered Abilities

Grade BTest
  • Ask an assistant to run the Abilities registered on your site.
  • Expose a specific editorial task once its code and permissions exist.

Installing the adapter does not add editorial tools by itself. A developer must supply and check each task, including its permissions.

Developer setup

A developer must install the adapter and supply the WordPress Abilities you need. Each Ability needs code, an input definition and a permission check.

Connection documentation for WordPress MCP Adapter
Sources, capabilities and assessment for WordPress MCP Adapter

Documentation reviewed .

Supported actions

Read
Depends
Draft
Depends
Edit
Depends
Publish
Depends
Localise
Depends

The adapter connects agents to explicitly exposed Abilities; it is not a bundled, complete editorial toolset.

Why this grade

  • Uses a common WordPress Abilities contract.
  • The site can define narrowly scoped operations and permission checks.

Limits

  • Requires technical setup and suitable Abilities.
  • Editorial coverage varies by plugin and site configuration.

Check the sources

Official route documentation

03

Content platforms

3 tools in this field.

Back to index start
Content platforms: daily tasks, limits and setup
ToolWhat you can doLimits and checksGetting started

Contentful

Official hosted MCP

Grade A-Production
  • Draft and edit entries, assets and locale content.
  • Publish approved content or organise it into a release.

Check the user role and the tools enabled for the environment. Publishing in Contentful does not deploy your website; a local token-based connection has different access rules.

Admin setup

An administrator enables the required tools for each space and environment. You then connect the assistant with your own Contentful account.

Connection documentation for Contentful
Sources, capabilities and assessment for Contentful

Documentation reviewed .

Supported actions

Read
Yes
Draft
Yes
Edit
Yes
Publish
Yes
Localise
Yes

Create and update entries, publish or unpublish content, manage locales and validate or schedule releases.

Why this grade

  • Explicit entry and release publication tools.
  • Per-environment tool gating supplements user permissions.

Limits

  • Each environment needs MCP app configuration.
  • Local-server defaults do not restrict a PAT to one environment.

Check the sources

Official route documentation

Sanity

Official Sanity MCP

Grade A-Production
  • Find and edit structured content with its schema in view.
  • Publish drafts or prepare content in a release version.

Check the schema, language setup and draft or release version before editing. Some document types skip drafts. Context MCP is a separate, read-only connection.

Admin setup

Connect with your Sanity account or a scoped API token. Select the correct project and dataset, and check the role’s write permissions.

Connection documentation for Sanity
Sources, capabilities and assessment for Sanity

Documentation reviewed .

Supported actions

Read
Yes
Draft
Yes
Edit
Yes
Publish
Yes
Localise
Depends

Query with GROQ, create or edit structured content and publish drafts. Release versions require their own document IDs.

Why this grade

  • Schema-aware document operations and explicit publishing tools.
  • Supports draft and release-version workflows.

Limits

  • Localisation depends on project schema and conventions.
  • Wrong draft or release IDs can target a different editorial state.

Check the sources

Official route documentation Read-only Sanity Context MCP

Directus

Official built-in MCP

Grade B+Test
  • Find and edit content in configured collections.
  • Use the publication and language fields your project defines.

Your project defines which fields control publication and languages. Check the role’s edit and delete permissions before changing content.

Admin setup

Use Directus 11.12 or later, enable MCP and create a dedicated user with suitable permissions and an access token.

Connection documentation for Directus
Sources, capabilities and assessment for Directus

Documentation reviewed .

Supported actions

Read
Yes
Draft
Depends
Edit
Yes
Publish
Depends
Localise
Depends

Create and edit content using the configured collections, roles and workflows. Publication is a project-specific status or workflow, not a universal publish button.

Why this grade

  • Reuses existing Directus permissions.
  • Content operations do not require a separate middleware layer.

Limits

  • Publication and localisation need project-specific modelling.
  • A broad service role can expose more data than an editorial assistant needs.

Check the sources

Official route documentation

What the labels mean.

We assess the connection described in each entry. A tool’s full website or app may do more. Grades are our editorial assessment; they are not vendor scores or client results.

Production
Dependable enough for a controlled recurring workflow today.
Test
Worth piloting, but access, maturity or control needs a bounded test.
Research
Useful specialist capability, not a daily operating interface.

These CMS entries are documentation reviews; we have not connected accounts or executed live writes. “Production” describes readiness for controlled use; it does not mean we have run the workflow. A publish action in a CMS also needs a check on the live site.

Editorial lead: Léon Houlier. Read the methodology.

Catalogue snapshot.

10 tools across 3 categories. Catalogue updated ; individual review dates are shown with each entry.

  • Production220%
  • Test880%
  • Research00%
10tools reviewed
3sections

Review the source catalogue at 5d1e8ff1.