Learn how to integrate your Core dna account with Claude using the Model Context Protocol (MCP). 

This guide walks you through the OAuth configuration and app creation process to enable seamless interaction between your Core dna DXP and AI tools.

1. Navigate to Core dna login page, and sign in using your Core dna Login Details, eg: https://mysitemcp.com/cdna-admin

Screenshot unavailable

2. Navigate to Users > OAuth Authentication > Configuration

Screenshot unavailable

3. Enable CIMD > Save changes

Screenshot unavailable

4. Open https://claude.ai/ in your browser OR desktop app > Navigate to Customise > Connectors > Add Custom Connector

Screenshot unavailable

5. In the modal populate the:

"Name" field, eg. "My Site MCP"
"MCP Server URL", eg. "https://mysitemcp.com/cdna-mcp"

Click "Add"

Screenshot unavailable

6. Click "Connect"

Screenshot unavailable

7. You will be redirected back to the Core dna site, click "Allow" to authorize Claude to access Core dna 

Screenshot unavailable

8. You will be redirected back to Claude

Screenshot unavailable

9. All done, you can now go back to ChatGPT and write your first prompt.

Screenshot unavailable

⚠️ Warning: AI + MCP Access to Your CMS/eCommerce Platform

Connecting AI agents to your CMS, eCommerce platform, or production systems through MCP (Model Context Protocol) introduces powerful automation capabilities - but also significant operational risk.

AI systems execute actions based on prompts and available permissions. A poorly written, ambiguous, or unintended prompt can trigger destructive actions at scale, including but not limited to:

• Deleting products, pages, collections, or customer data
• Publishing incorrect or unapproved content
• Modifying pricing, inventory, or SEO settings
• Overwriting templates, themes, or configurations
• Sending unintended customer communications
• Triggering irreversible bulk operations

Unlike traditional software workflows, AI agents interpret natural language probabilistically. Even well-intentioned prompts can produce unexpected outcomes if safeguards are not in place.

To reduce risk, we strongly recommend:

• Restricting AI permissions to the minimum required access
• Using staging or sandbox environments whenever possible
• Requiring human approval for destructive or bulk actions
• Implementing backups, versioning, and audit logs
• Testing prompts carefully before production use
• Monitoring all automated AI activity

By enabling MCP-connected AI access, clients acknowledge that AI-generated actions may produce unintended changes or operational disruption if improperly configured or prompted.

Treat AI agents with the same caution as granting administrator access to a human operator - because, at scale, mistakes can cause significant damage within seconds.