The CData Code Assist MCP for Adobe Experience Manager defines each connection to Adobe Experience Manager as a named configuration that an MCP Client (such as Claude Desktop) can use when sending natural language queries.

You create and manage these configurations using the CData Code Assist MCP Configuration Tool. The tool automatically handles formatting, storage, and registration with MCP clients.

Understanding Connection Configurations

Each connection configuration is stored in a .mcp file. This file includes the details needed to initialize the connector when an MCP Client starts a session.

• On Windows, configuration files are stored in "~/AppData/Roaming/CData/Adobe Experience Manager Data Provider/".
• On macOS, configuration files are stored in "~/Library/Application Support/CData/Adobe Experience Manager Data Provider/".

The .mcp file is a text file that contains a list of connection properties and a timestamp. For example:

#Tue May 20 15:48:40 EDT 2025
AuthScheme=Basic
User=myUser
Password=myPassword
Security Token=myToken

The configuration tool handles these settings automatically. Each saved configuration enables an MCP client to launch a dedicated MCP server instance with the correct connector and options. Manual file editing is not required.

Connecting to Adobe Experience Manager JCR Repository

This connection allows you to access content stored in an Adobe Experience Manager (AEM) JCR repository using WebDAV. The JCR (Java Content Repository) is the underlying storage system used by AEM to manage content nodes, properties, and metadata. You can connect to both local AEM instances and cloud-based AEM environments.

1. Set the URL to the WebDAV-enabled JCR server.
   • Local development: http://localhost:4502/crx/server
   • AEM as a Cloud Service: https://XXXX-pXXXX-eXXXX.adobeaemcloud.com/crx/server
2. Depending on the AuthScheme used:
   • For Basic make sure to provide User and Password.
   • For None no authentication is required and no additional configuration is necessary.

Once the connection is configured, you can query JCR nodes and properties exposed through the WebDAV endpoint using standard SQL queries. Ensure that the configured user has sufficient permissions to access the required content paths in the AEM repository.