Changelog

MCP Content Management Update: Maintain Website Content in AI Conversations

CatchCMS connects MCP-compatible AI clients with permission-aware website content management, token control and post-operation verification.

CatchCMS now connects to MCP-compatible AI clients so teams can query and maintain website content in conversations. Editors can ask for changelog organization, article summaries or targeted content updates. The client reads the site's actual categories and field definitions before carrying out the requested operation.

What's included in this update

  • Find operations when needed: The client can search the functions available to the current account, read parameter details and then execute the selected operation through one consistent entry point.
  • Follow admin permissions: An MCP token is associated with an admin account, so business operations use that account's identity and permissions. Site-level operations identify the target site for multi-site work.
  • Manage access tokens: Super administrators can issue tokens for enabled admin accounts, set expiration periods and revoke them when needed. The full token is shown once at creation while the server stores its hash.
  • Verify after each operation: The client can query an article again to check its title, body, category and status, completing the content maintenance workflow.

Useful workflows

For a product website, AI can read existing changelogs first and turn verified feature changes into an article. It can also add summaries or improve the structure of content in a selected category. Every write follows the content model and account permissions.

Getting started

Create a token in the admin's MCP access token section, then configure the site MCP endpoint and token in an MCP-compatible client. Confirm the account and target site before reading categories and content. Save the token when it is created and revoke it after the intended work is complete.