Liferay DXP 2026.Q3 includes a capability I have been wanting to experiment with: Liferay can now act as a Model Context Protocol server.

I knew what MCP was conceptually, but I had no idea what I would actually find once I connected an AI client to Liferay and let it explore.

So I did what seemed reasonable.

I started a disposable local Liferay instance, enabled MCP, connected Claude Code, gave it an Omniadmin account, and let it investigate.

The result was much more interesting than "AI can retrieve some content."

Claude created Liferay Objects, added fields and relationships, published them, immediately discovered the new APIs generated from those Objects, created and queried data, built out a Commerce catalog and storefront configuration, and even created MCP prompts and profiles.

That changed how I thought about the feature.

MCP isn't really about adding an AI API to Liferay.

It is about making the Liferay platform itself discoverable and operable by an AI agent.

What MCP Actually Means

The Model Context Protocol, or MCP, is an open standard for connecting AI applications to external tools and data.

Starting with Liferay DXP 2026.Q3, Liferay can act as an MCP server. An MCP-capable client such as Claude, GitHub Copilot, Cursor, or Gemini CLI can connect to Liferay and interact with capabilities exposed by the platform.

See the Liferay documentation for the complete setup and configuration details: Using Liferay as an MCP Server.

At a high level: