Liferay

MCP: The Quiet Update That Is Changing Every CMS Platform Right Now

In November 2024, Anthropic, the maker of Claude, released the Model Context Protocol (MCP) as an open standard. No big marketing event. Just a specification. And yet: since then, Liferay, Magnolia, Contentful, Strapi, and other enterprise CMS platforms have been busy integrating this standard into their core systems.

I am currently observing something that will fundamentally shift the way teams work with content systems – and most decision-makers do not have it on their radar yet.
In November 2024, Anthropic, the maker of Claude, released the Model Context Protocol (MCP) as an open standard. No big marketing event. Just a specification. And yet: since then, Liferay, Magnolia, Contentful, Strapi, and other enterprise CMS platforms have been busy integrating this standard into their core systems.

What MCP actually does – in one sentence:

MCP gives AI assistants such as Claude or Cursor direct, structured access to external systems. One standardized interface for everything.
The image that keeps coming up captures it well: MCP is the USB-C port for AI integrations.

Why this matters for CMS teams:

Imagine your editor types into their AI assistant: “Create a new article on our website, title 'Product News Q2', with this content.” And it happens. Without API documentation. Without a token. Without a developer in the loop. This is not a promise for the day after tomorrow. It is possible today – if the platform supports MCP.

What really interests me here:

Not all platforms are equally far along. Liferay delivers a native MCP server directly in the platform. Contentful probably has the most mature integration, including a hosted endpoint and OAuth. Magnolia approaches MCP strongly from the developer perspective. Strapi shows how a community-driven solution can already be used productively today – and is announcing native core integration.
Every platform solves the same problem – but with a different focus, different strengths, different target groups.

Over the next few days, I will take a look at each of these four platforms individually:
→ Liferay: MCP directly in the enterprise CMS, with the full permission model
→ Contentful: The most mature headless-native solution
→ Magnolia: MCP for developers – and what that means for teams
→ Strapi: Open source meets AI integration

If you use Liferay, Contentful, Magnolia, or Strapi and want to know what MCP concretely means for your team – follow me for the series. Or message me directly.

Marc Hermann
Questions about this topic?
Marc Hermann, working with Liferay and Magnolia since 2008, replies personally.
Get in touch →