Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>AEM Content Manager (ACM)New to Visual Studio Code? Get it now.
AEM Content Manager (ACM)

AEM Content Manager (ACM)

Preview

WPP Enterprise Solutions

|
9 installs
| (0) | Free
Write, validate and run AEM Content Manager (ACM) Groovy scripts from VS Code. The ACM MCP server for AI agents is registered automatically.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

AEM Content Manager (ACM) for VS Code

Write, validate and run AEM Content Manager (ACM) Groovy scripts on Adobe Experience Manager without leaving the editor. The ACM MCP server is registered automatically for the enabled instances, so AI agents can validate and run scripts, follow executions and read outputs on your AEM right after installing, with no configuration.

Using another AI tool or editor? Run ACM: Copy MCP Setup Prompt and paste it into the agent: it sets up the same MCP server by itself.

Works with AEM as a Cloud Service, AEM 6.5 and AMS, wherever ACM is installed.

Preview. Feedback and issues are welcome on GitHub.

Features

  • Zero-config start. A local AEM SDK at http://localhost:4502 with admin/admin works right after installing, together with the ACM MCP server for AI agents and the ACM scripting skill (see AI agents). The Get Started with ACM walkthrough shows the rest.
  • Run scripts and selections on the active instance. Inputs declared in describeRun() are edited together as JSON and run with the editor's play button (files are selected and uploaded first), console output streams into the ACM output channel, and a running script can be aborted. Manual scripts run from the Instance Scripts view, or from their opened editor, run by ID: the instance's stored version executes and its executions are listed under the script.
  • Run without history while iterating on read-only code, for users with ACM's console/execute/nohistory permission. Such runs are still traced in ACM's audit log.
  • Compile errors on save. Scripts are checked by ACM on the active instance and errors show up in Problems.
  • Code completion and docs for the whole ACM script API (repo, acl, inputs, outputs, conditions, …), generated from the ACM source. Lifecycle methods follow the script type: canRun/doRun for manual and automatic scripts, prepareRun/completeRun for extension scripts, request/respond for mock scripts.
  • Documented templates. File > New File... > ACM Script starts from a template: content migration, ACL setup, CSV and Excel export and import, scheduled cleanup, console code or HTTP mock. Type acmdoc to add the documentation header shown in the ACM UI.
  • Project, instance and execution views. Project Content lists the scripts and ACM snippets of the project's content packages (found automatically or set in acm.scripts.roots; several packages are listed side by side) and creates new ones from templates, with duplicate, rename, delete and reveal in Explorer next to run and compare; Instance Scripts lists what is deployed, named and grouped like in the ACM UI; Executions browses the history with logs and downloadable outputs and filters it by script or status. Compare a script with its counterpart on the other side from the context menu.
  • Instance status in the status bar: switch instances or open their settings in one click, while each view links to its related settings; see at a glance when an instance is unreachable, unauthorized or unhealthy. While a script runs, a separate Abort button appears next to it. The instance picker also enables or disables instances (enabled hides one from every tool, e.g. to park prod temporarily). Its tooltip shows the instance health (listing issues when it is unstable), the running execution with an Abort link and quick actions, and opens the ACM web UI, and a script or execution opens in ACM from its context menu (ACM: Open ACM in Browser picks any page).
  • AI agents. Copilot gets the ACM scripting skill and the ACM MCP server for all enabled instances, registered automatically; other tools set up the same server from one copied prompt or an exported config file (see below).

AI agents

The extension contributes:

  • the ACM Groovy scripting skill, so agents write scripts with the real ACM API, dry runs, abort checks and documentation;
  • the ACM MCP server for all enabled instances, so agents in agent mode can validate and run scripts, follow executions and read outputs — and compare one instance against another.

The MCP server is bundled and runs on the editor's own Node.js; credentials come from VS Code secret storage, never from mcp.json or other files. acm.activeInstance picks the default instance (tools accept an instance argument for the others), a readonly instance is read-only for the agent too, and a disabled instance is not visible to it. Turn it off with acm.mcp.enabled.

For tools that do not pick up MCP servers contributed by extensions (Claude Code, Cursor, Devin, …) run ACM: Copy MCP Setup Prompt and paste it into the agent, or ACM: Export MCP Config to write the same instances as a config file for ACM_CONFIG_FILE (without secrets, which stay in secret storage). The prompt lists concrete steps (register the server with your instances as inline ACM_CONFIG, verify) and the agent knows where its tool keeps MCP configuration; a local admin instance needs no secret, other instances reference environment variables that you define for the tool. The prompt is a snapshot: after changing instances, run it again or edit the JSON in the registration. If several tools should share one configuration, export it once to a file and point each of them at it with ACM_CONFIG_FILE. Both use the standalone @wppes/acm-mcp-server package, which needs Node.js 22 or later.

Agents run code with your AEM permissions. Prefer readonly instances or a user with limited ACM permissions outside local development, and review tool calls before approving them.

Configuration

Instances live in settings, typically the workspace's .vscode/settings.json, so a project can share them:

"acm.instances": [
  { "name": "author", "url": "http://localhost:4502", "authMode": "basic", "user": "admin" },
  { "name": "dev", "url": "https://author-pXXXX-eYYYY.adobeaemcloud.com", "authMode": "bearer", "readonly": true },
  { "name": "prod", "url": "https://author.example.com", "authMode": "cookie", "enabled": false }
]

Run ACM: Select Instance (or click the status bar) to switch, and ACM: Set Credentials to enter the secret. The picker's eye button toggles enabled per instance:

authMode Secret Typical use
basic password of user local AEM SDK, on-premise
bearer access token, e.g. the local development token from the AEMaaCS Developer Console AEM as a Cloud Service
cookie value of the login-token cookie from a browser session any instance you can log into

Secrets are kept in VS Code secret storage and bound to the instance URL. When they expire, the status bar and error messages lead to ACM: Set Credentials.

Guardrails: running on a readonly instance is blocked, and running on any non-local instance asks for confirmation. In untrusted workspaces, instances are read from user settings only.

Setting Default Description
acm.instances local author AEM instances with ACM installed. readonly blocks running code on an instance; enabled (default true) hides it from pickers, views and the MCP server.
acm.activeInstance Instance used by commands; defaults to the only enabled instance.
acm.validateOnSave true Compile-check scripts declaring doRun() when saved.
acm.mcp.enabled true Offer the bundled ACM MCP server to agents.
acm.mock.mode auto Show Mock scripts: auto when the active instance has its Mock HTTP Filter enabled (off by default in ACM), enabled always, disabled never.
acm.scripts.roots [] Folders with the project's scripts for Project Content; empty finds them in the workspace.
acm.http.timeout 30000 Timeout of each HTTP request to AEM, in ms.
acm.run.timeout 120000 Wait for a run, in ms: the limit of a run without history, and how long the MCP server waits before returning the execution ID. Runs from the editor with history are followed until they finish.
acm.run.pollInterval 1000 How often a queued run is checked, in ms.
acm.health.interval 60000 How often the status bar checks the instance, in ms; 0 only on changes.
acm.executions.limit 50 Past executions shown in the Executions view.
acm.executions.refreshInterval 10000 How often the Executions view reloads while visible and the window is focused, in ms; pauses after an error until a manual refresh. Each reload queries the history on AEM; 0 only on Refresh and after runs from the editor.

Timings apply to the bundled MCP server too.

Requirements

  • VS Code 1.101 or later (or a compatible editor).
  • ACM installed on the instance, and a user with access to the ACM API and the console feature. See ACM permissions.

Contributing

To build, check and release the extension, see the development guide and the roadmap.

License

Apache License 2.0. Provided "as is", without warranty of any kind; use it at your own risk (see sections 7 and 8 of the license).

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft