Liferay Legacy MCP

An MCP server for Liferay DXP releases that don’t have one: 7.4 U1–U92, and 2024.Q1 to 2025.Q4. AI assistants, such as desktop chat apps, IDEs and coding agents like Claude Code, can then find, read and change your Liferay’s content in plain language, with Liferay’s own permissions, and with a preview a person confirms before anything changes.

A community app, for experimental use. Liferay Legacy MCP is shared by Liferay Community APAC. It isn’t a Liferay product: Liferay doesn’t support it, and it comes as is, with no warranty and no support commitment. Use it to explore and evaluate on a test or development copy of your Liferay, not in production. AI assistants can misread a request, so start with writes off, and check every preview before you confirm it. Running it still requires a Liferay DXP Enterprise Subscription.

Getting StartedWhat the server does, and the shortest way to try it with a desktop AI assistant. InstallingThe service user, the OAuth connection, and the server for one person, or for services and people over HTTPS. Using the ServerWhat to ask, how writes are previewed and confirmed, and the page inspection tools. ReferenceTools, settings, compatibility, and known issues.

Highlights

For releases with no MCP. Liferay DXP 2026.Q1 and later can be reached by AI through Liferay’s own features. This server brings the same to 7.4 U1–U92 and 2024.Q1 to 2025.Q4, without changing Liferay.
Runs outside Liferay. The server is a separate container that uses Liferay’s public Headless and JSON web service APIs. Nothing is installed into Liferay’s code, so a Liferay update doesn’t need a new server version unless an API it uses changes, and tools whose APIs a release doesn’t have show as unavailable.
Only configuration in Liferay. The OAuth 2 client extension creates an OAuth application and adds no code to Liferay, so it isn’t tied to a Liferay version.
Content tools. Search, read, create and update web content, documents, blogs, categories and tags, navigation menus, knowledge base articles and translations, and run review workflows.
Every API, when you need it. Generic tools reach all of Liferay’s Headless REST APIs and its JSON web services, so the AI assistant isn’t limited to the dedicated tools.
Safe writes. Writes are off by default. When turned on, every change is shown as a preview, and runs only after it’s confirmed. Deletes, batches and permission changes need their own setting. Every attempt is written to an audit log.
Least privilege. The server acts as one service user, through an OAuth 2 application whose scopes limit what it can reach. Liferay enforces both.
Page inspection. See a page’s headings, links, missing image descriptions and errors, and take screenshots, as a guest or as a view-only user.

Supported Versions

Liferay Legacy MCP	Liferay DXP
1.1.0	2024.Q1 to 2025.Q4, tested on the latest update of each quarter.
1.1.0	7.4 U1–U92: U92 tested, with OAuth 2 or a password; U1 to U91 with a password connection instead of OAuth 2.

A Liferay DXP Enterprise Subscription is required, even though Liferay Legacy MCP is a community app for experimental use that Liferay doesn’t support. It works only with Liferay DXP: by default, the server refuses to start unless the Liferay it connects to is Liferay DXP.

The server is a container image, ghcr.io/liferay-community-apac/liferay-legacy-mcp, for linux/amd64 and linux/arm64. To install it, follow Installing.