An MCP Server acts as a bridge between your solution and AI models. For us, the new Liferay DXP MCP Server exposes our Headless APIs through a standardized interface that LLMs can understand and interact with allowing them both to retrieve information, but also interact with Liferay DXP to create or update different types of entities.

Key Benefits:

• MCP is a standard protocol that allows users to integrate easily Liferay DXP to any compatible AI ( like ChatGPT, Gemini, Github Copilot, etc ), reducing implementation and maintenance costs.

• Because MCP defines a standard protocol, AI models can reliably query, call functions, and retrieve data in structured ways (JSON schemas, typed responses, etc.).

• Leveraging the Headless APIs in the MCP server, we ensure that our permission system enforces that LLMs access only the information the user making queries can access.

Easier Content Management, Headlessly 

With Liferay’s new Headless CMS, you can create, organize, and publish content across multiple channels easily in a single interface. With a unified content creation and management experience, you’re able to: 

• Go to market faster by reusing content across different sites, pages, and channels through APIs. 

• Use flexible content structures or even define custom structures without any coding knowledge. 

• Streamline collaboration with shared spaces and built-in publishing workflows. 

Eliminate Data Silos with HubSpot Lead Connector 

By creating a seamless, automated bridge between Liferay DXP and HubSpot CRM, you can ensure that every new contact, company, and lead captured in Liferay DXP is instantly synced and ready for your next campaign. 

Easily Promote Content Among Environments 

Transfer data and content across environments safely and reliably. Through a significant change to the infrastructure, users are able to: 

• Move elements that use the new infrastructure at the instance level, such as Object Definitions, Picklists, or Roles, and freely export and import Object Entries with any scope.

• Use partial imports to avoid blocking users in the case of errors. 

• Receive clearer error messages that give the user full control to recover from errors and missing references.