MCP server for AEM

Hi @kamaraj_aem ,

There are some set up and prerequisite that you need to follow:

• Node.js >= 18.0.0
• npm
• Access to AEM instance(s)

1. Install the package globally:

2. During installation, an example configuration file will be automatically created at ~/aem-instances.yaml if it doesn't already exist

3. Configure your AEM instances in ~/aem-instances.yaml with your actual server details (see configuration example below, or check examples/aem-instances.example.yaml in the installed package)

You can follow below link for more details:

https://github.com/arkadiusz-rosiak/aem-dev-mcp/blob/master/README.md

-Tarun

Hello @kamaraj_aem ,

You are correct that the default AEM MCP server configurations do not expose page creation as a built-in tool - most public and open-source reference MCP servers for AEM provide read access to pages and components, but not page creation, for both security and simplicity reasons.

If page creation is your goal, you likely need to:

• Write or add a custom MCP tool function (e.g., create_page) that wraps AEM’s PageManager or /bin/wcmcommand create operation.
• Ensure your MCP tool does proper input validation, template selection, path safety, and approval.

Hello @kamaraj_aem 

1. Most public MCP servers for AEM only provide read/list/list-components capabilities by default. "Create page" is a write operation and needs explicit server support.

2. Out-of-the-box, the aemaacs-mcp-server (and similar public repos) do not provide tools for creating new pages.

3. To support page creation, you may :
- Implement a "create_page" operation as a new tool in your MCP server code.
- This tool would call the AEM API to create a page (e.g., using the REST API or Sling POST).
- The operation should at minimum accept: parent path, template, page title (and optionally, name).

4. To use the tool with AI/agent clients, ensure:
- The MCP tool is registered and visible in your configuration (e.g., in tools or mcpTools list).
- You grant the necessary permissions for write actions (not just read).

Hi @kamaraj_aem,

There is a new experimental API (https://developer.adobe.com/experience-cloud/experience-manager-apis/api/experimental/sites/pm/#tag/Pages ) which has create page API. This API can be used to generate the MCP server using the Postman's MCP Server Generator (https://www.postman.com/explore/mcp-generator ). You can use this approach to generate the MCP Server. You probably have to add the access token generation implement to the MCP Server, because I doubt it implicitly have it implemented when generated. I personally haven't tried this API, but it did work for other APIs. This way you can avoid implementing the MCP server from scratch.   

You probably have to reach out to Adobe Support team to get this experimental API access through Developer console.

Hi @kamaraj_aem ,

The MCP Server for AEM currently supports reading and analyzing content but does not support direct page creation via AI or API calls out of the box.
If you’re using the GitHub version you mentioned, that project mainly exposes content structure for external tools-it doesn’t include endpoints for creating new AEM pages.
To create pages using AI or external automation, you need to-
Extend the MCP server by adding a custom servlet or endpoint that uses PageManager.create() to generate new pages.
Or, use AEM’s Sling POST servlet or Page Creation API instead of MCP for page creation tasks.
The MCP server you’re using doesn’t support page creation natively — you’ll need to extend it with a custom API or use AEM’s native page creation endpoints.