MCP: The silent update that is currently changing all CMS platforms - Portal Works

Liferay DXP 2026.Q1 LTS ist da – Jakarta EE, neues CMS & MCP Server Mehr erfahren → Liferay 2026.Q1 LTS →

MCP: The silent update that is currently changing all CMS platforms

In November 2024, Anthropic, the manufacturer of Claude, published the Model Context Protocol (MCP) as an open standard. Not a big marketing event. Simply a specification. And yet, since then, Liferay, Magnolia, Contentful, Strapi and other enterprise CMS platforms have been working on integrating this standard into their core systems.

Artikelbild

I’m currently observing something that will fundamentally shift the way teams work with content systems—and most decision-makers haven’t even noticed it yet.
In November 2024, Anthropic, the creator 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 working to integrate this standard into their core systems.

What MCP actually does—in a nutshell:

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

Why this matters for CMS teams:

Imagine your editor typing into their AI assistant: “Create a new article on our website, titled ‘Q2 Product Launch,’ with this content.” And it happens. Without API documentation. Without tokens. Without developers in the loop. This isn’t a promise for the day after tomorrow. It’s possible today—if the platform supports MCP.

What really interests me here:

Not all platforms are at the same stage. Liferay provides a native MCP server directly within the platform. Contentful likely has the most mature integration, including a hosted endpoint and OAuth. Magnolia approaches MCP strongly from a developer’s perspective. Strapi demonstrates how a community-driven solution is already productive today—and announces native core integration.
Each platform solves the same problem—but with a different focus, different strengths, and different target audiences.

Over the next few days, I’ll take a closer look at each of these four platforms individually:
→ Liferay: MCP built right into the enterprise CMS, with a full permissions 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’re using Liferay, Contentful, Magnolia, or Strapi and want to know what MCP specifically means for your team – follow me for the series. Or reach out to me directly.

Fragen dazu?

Marc Hermann antwortet persönlich – kein Vertriebsteam, kein Formularautomatismus.