AEM Content Manager (ACM) MCP Server

AEM Content Manager (ACM) is an MCP integration. Validate and run Groovy scripts on Adobe Experience Manager through AEM Content Manager (ACM).

Packages and local setup

The published npm package is @wppes/acm-mcp-server, version 0.1.4. Its declared MCP transport is stdio.

The package declares ACM_CONFIG_FILE (required): Path to the ACM config document: the acm.instances list (with per-instance authMode, secret, readonly, enabled), acm.activeInstance and timing keys, same keys as the VS Code extension settings; ACM_CONFIG: The same config document inline instead of a file; takes precedence over ACM_CONFIG_FILE.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.4 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.