MCP: Your Backbone for Scalable, Enterprise-Ready AI
How the MCP Server Works with Liferay DXP
MCP Server + AI Hub
The MCP server acts as the bridge that enables connections to the LLMs powering AI agents within Liferay's AI Hub. By routing contextual data through the MCP, these AI services become available as actors you can orchestrate directly within your automations. With MCP support built in, AI Hub workflows can leverage LLM intelligence without custom integrations, making it faster to design, refine, and scale intelligent automations across your DXP.
Learn more about Liferay's AI Hub here.
MCP Server + Security
The MCP automatically respects all Liferay permissions, so that an agent run by a user can only see the same content and sensitive data that the user is allowed to see to begin with.
MCP Server + Low-Code
Users can create and configure new MCP tools and prompt templates through a low-code interface.
Frequently-Asked Questions
MCP servers are programs that expose specific capabilities to AI-powered tools through standardized protocol interfaces. Common examples include:
- File system servers that allow AI to read and navigate documents.
- Database servers for data queries.
- GitHub servers for code management.
- Calendar servers for scheduling.
Liferay's MCP Server provides out-of-the-box tools and low-code interfaces to create prompts. By connecting LLMs to Liferay's MCP server, you can leverage those AI services to configure agents within Liferay DXP with the AI Hub. This way, the MCP ensures that every interaction remains consistent, governed, and extensible as your AI needs grow.
Think of Liferay's MCP server as LLM-agnostic. You can use it to connect to your preferred LLM, like OpenAI, Gemini, Azure AI, and more.
Liferay's MCP server includes the core MCP server, business user tool and prompt management, out-of-the-box context providers, permissions, and a clear API and developer framework.
Through the MCP, LLMs can securely access the full context of your DXP application and analytics. The MCP automatically respects all Liferay permissions, so that an agent run by a user can only see the same content that the user is allowed to see to begin with.