Contentful, Sanity, Strapi, microCMS, and genko.me offer official MCP servers for content operations. WordPress has an official MCP Adapter, while WordPress.com provides a hosted server. Official support does not mean identical publishing, schema editing, or file upload capabilities. The hosted microCMS MCP service is in beta.

What should you compare in a CMS MCP server?

First, distinguish a server that searches official documentation from one that operates on your CMS data. Being able to look up a specification does not mean an agent can save an article.

This table follows the vendors' official tool catalogs. “Not listed” means the operation is absent from the standard tools reviewed here, rather than that no official server exists. Custom implementations and plugins are a separate question.

CMS and official reference

Read, create drafts, publish

Schema changes

Media

Contentful

Supported

Create and modify content types

Upload, publish, and other operations

Sanity

Supported

Deployment and editing tools

Upload to datasets and Media Library

Strapi

Supported

No standard model editing tool listed

Browse and update metadata; no new file uploads

WordPress.com

Supported

Post type definition changes not listed

Create, list, update metadata, and more

microCMS

Supported

Read API definitions; changes not listed

Retrieve, upload, delete

genko.me

Supported

Read API and field definitions; changes not listed

Upload, list, update alt text, delete

MCP is not exclusive to Claude. Clients include Claude Code, Codex, and Cursor, among others. Check whether your particular client supports the HTTP transport, OAuth, or custom headers required by the server.

Official capabilities and connections by CMS

Contentful: when agents also need content model access

The official guide lists entry creation, updates, publishing, content type changes, and asset operations. Connect to https://mcp.contentful.com/mcp using OAuth 2.1. Install and configure the MCP app in the target space and environment; both user permissions and the app's allowlist apply.

The local version runs with npx @contentful/mcp-server and a Management API personal access token. Its boundary is the PAT's permissions. A default space setting should not be treated as an access restriction.

Sanity: content and schemas in the same workflow

The official Sanity MCP server runs at https://mcp.sanity.io. OAuth is the default; a Bearer API token is another option. Run npx sanity@latest mcp configure to configure a supported client.

Tools cover querying, creating, changing, and publishing documents, plus schema retrieval, deployment, editing, and asset uploads. Custom validation rules are skipped during MCP validation. Schema access therefore does not mean every Studio validation rule will run.

Strapi: operating within your own instance

Strapi's built-in MCP server requires version 5.47.0 or later. Enable mcp.enabled in the server configuration, restart Strapi, and connect to /mcp on your instance. Authentication uses an Admin token in a Bearer header.

Content tools support reading, creating, and updating. Drafts, publishing, and unpublishing require Draft & Publish on the content type. Version 5.54.0 adds Media Library browsing, metadata changes, and folder management, but new files must be added through the admin interface or Upload API. Tools generated from content models do not imply tools for modifying those models.

WordPress: separate WordPress.com from the Adapter

The official WordPress.com server uses OAuth 2.1 at https://public-api.wordpress.com/wpcom/v2/mcp/v1. Enable MCP access for your account. Self-hosted sites connected through Jetpack can use the same server. Its tool reference says posts.create defaults to a draft, while posts.update with status: publish goes live immediately. Media creation is also available.

For an independently hosted site, the official MCP Adapter is another route. It exposes WordPress Abilities over HTTP or WP-CLI STDIO. The default HTTP path is /wp-json/mcp/mcp-adapter-default-server; authentication and permissions are managed at the transport and Ability levels. The official connection examples use Application Passwords through an HTTP proxy, or --user with STDIO. Installing the Adapter alone does not guarantee a complete toolset; check the exposed Abilities.

microCMS: distinguish content operations from documentation search

The official microCMS MCP service is a hosted beta at https://mcp.microcms.io/mcp/{service-id}. Supply an API key through an Authorization: Bearer header. OAuth is not supported.

Alongside reads, tools cover draft creation, publication status changes, scheduling, and media operations. Separate tools create published content or drafts, and update published content or drafts only. Check the exact tool name. API definitions can be retrieved, but schema changes are absent from the catalog. The Document MCP Server serves a different purpose: searching and retrieving official documentation.

genko.me: separating draft work from publishing permission

The genko.me MCP server uses OAuth with Streamable HTTP at https://genko.me/mcp. Its CLI provides configuration for Claude Code, Codex, Cursor, and VS Code.

Save with create_draft and update_draft; publish or schedule with publish_entry and schedule_entry. On a published entry, update_draft saves unpublished changes that discard_changes can discard. This differs from restoring a historical version after publication.

Editing requires an editor role or higher and mcp:write; publishing and scheduling also require mcp:publish. Media operations are supported, but uploads remain subject to plan storage and file size limits. No MCP tool for changing schemas is listed.

What to check before an agent publishes

Try a small workflow in this order when evaluating a CMS. This is an operational example, not a claim that every CMS provides the same approval features.

  1. Connect with read access first. Retrieve the site, environment, API, language, and field definitions. Check whether the connection can reach anything outside the intended scope.

  2. Create one test draft. Read it back and check the body, references, images, and publication state. Establish whether an “update” takes effect immediately on an already published article.

  3. Approve publishing separately. Have a person review the entry ID, diff, language, and publication time. Combine a draft-only instruction with restrictions enforced by tokens or roles.

  4. Test auditing and recovery. Establish how to trace the actor, target ID, before-and-after content, and execution time. Check the availability and conditions of history, audit, and restore features individually. Keep a separate copy of previous data if needed.

  5. Check the public site afterward. Treat CMS success, cache refresh, and build completion as separate results. If a response is interrupted, inspect existing data before creating it again.

Unpublishing, restoring an older version, and discarding unpublished changes are different operations. Decide what recovery must cover instead of assuming the same procedure can undo media or schema deletion.

If you already use Contentful or Sanity and need model management, their official MCP tools are worth evaluating. Strapi or the WordPress Adapter are candidates when operating your own instance is a requirement. If microCMS already works well for your team, test its official MCP permissions and beta conditions before deciding whether a migration is necessary. genko.me is another option for drafts, publishing, and media operations, but does not fit a requirement to delegate model changes through MCP.

For a concrete authoring workflow, see creating drafts and publishing from Claude. For the boundary between content operations and application development, see AI agent and CMS integration.

FAQ

Does an official MCP server mean an agent can publish articles?

A documentation-only server cannot publish. Even a content management server needs both a publishing operation and the required permissions. Review the tool catalog and the actual scope granted after authentication.

Can Codex or Cursor use a CMS MCP server?

Compatible clients can; this is not a Claude-only integration. Match the server's transport, OAuth, and Bearer header requirements against the client's capabilities.

Can an agent be limited to creating drafts?

Choose draft tools and consider a configuration that restricts publishing permissions. Whether write access also permits an operation that immediately publishes varies by product. Check with test content.

Can MCP change a CMS schema?

Contentful and Sanity provide related tools. Equivalent model definition changes were not confirmed in the standard catalogs reviewed for Strapi, WordPress.com, microCMS, and genko.me. Reading an API definition does not establish that it can be changed.