The Acquia DAM MCP Server implements the Model Context Protocol (MCP). This is an open standard that enables AI assistants such as Claude, Microsoft Copilot Studio, and ChatGPT to securely connect to external tools and data sources. Once connected, users can interact with their DAM through natural conversation.

Enabling the MCP Server

The Acquia DAM MCP Server is available to all customers with the REST API feature enabled.

To enable the MCP Server on your DAM, contact Acquia Support.

Connecting your AI assistant

To connect to the Acquia DAM MCP Server, you must use an existing AI assistant chatbot of your choice. There is no UI in DAM to directly interact with the MCP Server.

The DAM MCP Server can connect to any AI assistant that supports connections to custom MCP servers with OAuth authentication.

The Acquia DAM MCP Server implements the Model Context Protocol (MCP). This is an open standard that enables AI assistants such as Claude, Microsoft Copilot Studio, and ChatGPT to securely connect to external tools and data sources. Once connected, users can interact with their DAM through natural conversation.

Enabling the MCP Server

The Acquia DAM MCP Server is available to all customers with the REST API feature enabled.

To enable the MCP Server on your DAM, contact Acquia Support.

Connecting your AI assistant

To connect to the Acquia DAM MCP Server, you must use an existing AI assistant chatbot of your choice. There is no UI in DAM to directly interact with the MCP Server.

The DAM MCP Server can connect to any AI assistant that supports connections to custom MCP servers with OAuth authentication.

Connection details

Supported AI assistants

Refer to the documentation of your AI assistant for instructions on how to connect custom MCP servers:

• Claude Desktop / Claude.ai
• Claude CLI
• Microsoft Copilot Studio
• ChatGPT
• Gemini Enterprise
• GitHub Copilot documentation - GitHub Docs

Usage

Once connected, your AI assistant has read-only access to your DAM. Each user authenticates individually via OAuth, and the assets and content available to them reflect their own DAM permissions. The same safeguards that prevent users from accessing non-permissioned assets through the web UI and the API also prevent AI assistants from accessing unauthorized content.

Available tools

The MCP Server exposes the following tools for your AI assistant to use. These are called automatically by your AI assistant. Users interact through conversation.

Example use cases and starter prompts

DAM administrators

Metadata quality audits
Find gaps in your metadata before they become a problem.

• "Find all images added in the last 30 days with an empty description field."

Expiration and lifecycle monitoring
Stay ahead of content going stale.

• "Show me all active assets expiring in the next 90 days."

Onboarding new team members
Help new users understand your DAM's structure from day one.

• "What metadata fields exist in our DAM, and how are assets categorized?"

Digital marketers

Campaign asset discovery
Find exactly what you need through conversation, no search syntax required.

• "Find assets from the Digital Government Summit for an email header."

Right-sized assets, no extra steps
Get a CDN-ready, resized image link without downloading and re-uploading.

• "Give me this image as a web-ready 800x600 version."

Build a presentation from your brand assets
Search the DAM, pull an asset, and build a slide in one prompt.

• "Search our DAM for a screenshot of natural language search, then build one pitch slide on the value of AI search."

Creatives

Check before you create
Avoid duplicating work by searching for existing assets first.

• "Do we already have any banner assets we could reuse?"

Understand the metadata schema before starting a brief
Get the exact controlled vocabulary values so your brief matches what's searchable later.

• "What Product and Event tags can I use for this brief?"

Fast reference pulls mid-review
Pull up an asset inline without leaving your AI assistant.

• "Pull up the Digital Government Summit Minnesota header so I can compare it."