aem

AEM MCP Server provides a modern, TypeScript-based MCP implementation for Adobe Experience Manager. It exposes a rich set of REST and JSON-RPC endpoints to manage content, components, assets, templates, and localization within AEM, along with integrations for AI assistance, chatbots, and automation workflows. You can interact with the server using the bundled JSON-RPC methods (e.g., listPages, createPage, updateComponent, searchContent, uploadAsset) as well as the REST API for method discovery and execution. The server also includes an interactive dashboard for API exploration and testing, making it straightforward to validate operations against your AEM instance. To run local tests, point the MCP server at your AEM instance (local or remote) and start the Node server; you can then issue RPC calls or REST requests to the server’s endpoints to perform content and asset management, page and component operations, and advanced searches.

Typical workflows include: creating and updating pages and components, uploading assets to DAM, performing full-text searches across content, and orchestrating multi-step operations via the JSON-RPC interface or REST methods. The server is designed to be scriptable and friendly for automation engineers, AI copilots, and developers who want to manage AEM programmatically or via natural-language interfaces that translate to MCP calls.

Prerequisites:

• Node.js 18+ (LTS)
• Access to an AEM instance (local or remote) with appropriate credentials

Installation steps:

1. Clone the repository:

git clone https://github.com/indrasishbanerjee/aem-mcp-server.git
cd aem-mcp-server

2. Install dependencies:

npm install

3. Build the project (production-ready build):

npm run build

4. Configure environment variables (optional but recommended):

• PORT: Port number to run the MCP server (default 3001)
• AEM_HOST: URL of your AEM instance (e.g., http://localhost:4502)
• AEM_USERNAME / AEM_PASSWORD: Credentials for AEM (if authentication is required)

5. Start the server (production):

npm start

6. (Development) Enable hot-reload during development:

npm run dev

If you prefer running via a specific runtime command, ensure your mcp_config points to the proper entry file (see mcp_config section).

Notes and tips:

• Environment variables: Set AEM_HOST, AEM_USERNAME, AEM_PASSWORD to enable authenticated operations against your AEM instance.
• The MCP server exposes both REST and JSON-RPC interfaces. Use /api/methods for a list of available methods and /mcp for RPC invocations.
• If you see port conflicts, change PORT in your environment or mcp_config to an available port.
• Ensure CORS and security configurations are aligned with your deployment environment if exposing the API externally.
• The server supports AI integrations (OpenAI, Anthropic, Ollama) and can be extended with custom HTTP APIs and automation workflows.
• For production deployments, consider containerizing the server and using a reverse proxy for TLS termination.