Acquia DAM Adds Read-Only MCP Access for AI Assistants

Customers using Acquia DAM can connect compatible AI assistants to their digital asset libraries through a Model Context Protocol server with read-only access. In a LinkedIn post, Acquia presents the capability as a way to bring approved DAM assets into AI-assisted workflows, while its product documentation describes the connection and access controls. The MCP Server uses OAuth authentication and limits the assets and information available to each user according to that person's existing DAM permissions.

The connection lets users work with DAM information through natural-language conversations in an existing AI assistant rather than through a separate chat interface in Acquia DAM. The MCP Server exposes tools for searching permitted assets, retrieving asset details (including links, CDN embed URLs, metadata, and security information), and listing metadata fields available in the DAM. Acquia provides connection guidance for Claude, Microsoft Copilot Studio, ChatGPT, Gemini Enterprise, and GitHub Copilot, and says the server can work with AI assistants that support custom MCP servers and OAuth authentication.

The initial release does not allow AI assistants to edit asset metadata or upload new files, although Acquia says it plans to add those capabilities in future versions. Access is available to Acquia DAM customers with the REST API feature enabled, and users may need paid AI assistant plans or administrative access because most assistants' free versions don't include custom MCP connections. Acquia's documented examples include metadata audits, expiration checks, natural-language asset discovery, retrieval of CDN-ready asset links and searches for existing creative material before producing new assets.