Does Acquia DAM have an MCP server? Not yet. Here's where Acquia's MCP work really stands.

No. As of July 2026, Acquia DAM (Widen) does not have an MCP server. Acquia says so itself. The Acquia DAM use-cases page describes "our upcoming MCP (Model Context Protocol) Server," and that sentence sits under a heading called "The Future: Architecting Creative for Agentic AI." Upcoming. Future. That one word of tense is the whole answer.

The confusion is understandable, because Acquia HAS shipped an MCP server. It just belongs to a different product: Acquia Source, its Drupal CMS. That docs page is what most people find when they search this question, and it's easy to misread as "Acquia DAM has MCP." It doesn't.

We checked four primary sources on July 7, 2026. The Acquia DAM use-cases page calls the DAM's MCP server "upcoming." The Acquia Source MCP docs describe a shipped, experimental, CMS-layer server with exactly one DAM-touching tool. Acquia's May 22, 2026 announcement says four DAM AI agents are "planned for release later in 2026." And Zapier hosts a third-party bridge titled "Acquia DAM MCP" that exposes a single action.

This page is dated on purpose. Acquia says the DAM agents land later in 2026, and I expect the MCP story to change with them. When it does, we'll re-verify and update this page. If you're reading this after Acquia ships, check the date stamp and their docs before you decide anything.

Acquia sells a platform, and MCP shows up at different layers of it. The status question only makes sense if you keep the layers straight. Four layers matter here.

Read the table bottom to top and the pattern is clear. Acquia's MCP investment is real, but it sits at the CMS and developer layers. Acquia even documents how to turn Drupal itself into an MCP server, exposing nodes, views, and Drush commands as tools. The DAM, where your actual assets live, is the layer still waiting.

That matters because the DAM is the layer marketers ask about. Nobody searches "acquia dam mcp server" because they want their AI to create a Drupal content type. They want their team's AI to find, check, and use approved assets. That's the part that doesn't exist yet.

Credit where it's due: the Acquia Source MCP server is real and the docs are good. It's an experimental feature you enable per site. It covers three domains: Content Management, Content Modeling, and Drupal Canvas. The docs walk you through connecting Claude Code with a one-line claude mcp add command, plus Claude Desktop and Cursor, all with OAuth. The docs page went up April 15, 2026 and was last updated June 26, 2026.

The tool list is Drupal through and through: create_node, update_node, batch_create_nodes, create_media, create_content_type, field configuration, and nine Drupal Canvas page and layout tools.

Exactly one tool touches the DAM: create_dam_media, described as "Create media using DAM assets." It pulls an existing DAM asset into Drupal as a media entity. That's consumption, not access. It cannot search the DAM. It cannot write metadata, check usage rights, manage collections, or read asset analytics. If your Drupal team builds pages from DAM assets, it's genuinely useful. If you wanted your AI to work inside the DAM, it's not the thing.

So when someone forwards you the Acquia Source MCP docs as proof that "Acquia DAM has MCP now," the accurate reply is: Acquia's CMS has an experimental MCP server, and it can fetch DAM assets into Drupal. The DAM itself still has no MCP surface. Both halves of that sentence are true at once.

On May 22, 2026, Gabe Aguilo, Acquia's VP of Product Management Innovation for Acquia Source, announced four AI agents for Acquia DAM. Each has a clear job. The Curator handles duplicates and taxonomy cleanup. The Producer handles conversions and crops. The Guardian flags AI-generated content and watches brand compliance and rights. The Strategist reads performance analytics. The blog's own FAQ states they are "planned for release later in 2026," and every agent ships with human-in-the-loop governance: nothing reaches production without a human approval step.

That's a credible roadmap, and the post is refreshingly honest. It opens by acknowledging the perception that Acquia DAM "has been standing still while competitors race to ship AI features." The DAM itself already has ten AI features listed on its AI page, from natural language search to duplicate detection to metadata generation, and nearly 300 integrations. This is a deep product. None of those ten AI features mentions MCP or agent access, though.

In Acquia's own words, the announcement describes the payoff of its MCP layer like this: a DAM agent can pass an approved, rights-cleared asset "directly into a web publishing workflow... in Acquia Source," and then makes the argument explicit: "It requires the platform on both sides of the hand-off."

Read that carefully. Acquia's MCP story is agents moving assets between Acquia products. That is a real capability, and if you run your sites on Acquia Source, it could be great. But it's a different promise than the one most buyers hear in "MCP server." It doesn't say your team's Claude, ChatGPT, or Copilot gets to search and use your DAM. Whether these agents will be exposed to third-party MCP clients at all is unclear. Acquia hasn't said, and its "platform on both sides" framing points the other way. Back in April, CMSWire reported that MCP interoperability with Claude, Cursor, and GitHub Copilot was "planned for future release" across the platform. Planned. Same tense as everything else here.

If you run Acquia DAM right now and want your content reachable by AI, you have three honest options, and none of them is a native MCP server.

The API route works. The Widen REST API v2 gives you OAuth 2.0 plus assets, metadata, search, and webhooks, and a custom MCP wrapper on top of it would do what buyers actually want. But you're building and maintaining a product, and most marketing teams shouldn't be in that business.

The Zapier route deserves a plain warning. The page is titled "Acquia DAM MCP Server," which is exactly what people search. The product behind the title is a generic Zapier bridge exposing one Acquia DAM action: Upload Asset. That's it. No search, no retrieval, no metadata. Useful if uploading is your whole need. Misleading if you landed there thinking the DAM has real MCP support.

There's a fourth option, and here's my bias declared: we build a DAM with this already shipped. Masset's MCP server is generally available today with 32 tools, 20 reads and 12 writes, and it works with Claude, ChatGPT, Copilot, Cursor, and any MCP-compatible client. Your permissions are enforced on every tool, and your content never trains AI models. If "our approved content, inside our team's AI tools, this quarter" is the actual requirement, that exists now. The full head-to-head is at Masset vs Acquia DAM. And if Acquia's roadmap fits your stack better, especially if you're deep on Drupal, waiting is a defensible call. Just make it knowingly.

Two sentences sound almost identical in a sales deck. "Our platform has AI agents connected by an MCP layer." And "your content is available inside your team's AI tools." The first means the vendor's AI works inside the vendor's walls. The second means your people's Claude, ChatGPT, and Copilot can search, check, and use your approved assets wherever they already work. Acquia's announced direction is the first. Most buyers searching this phrase want the second.

So ask the question that separates them: can my team's own AI clients search, fetch, and use our approved assets today, with our permissions enforced on every call? "Today" does a lot of work in that sentence. So does "our permissions."

We've been running this same check across the DAM and enablement market, one vendor at a time. The answers vary more than you'd expect. You can see the head-to-head for Brandfolder and Frontify, or the full vendor-by-vendor rundown in the MCP landscape section of our DAM guide.

Acquia will probably ship this. They've said as much, twice, in their own words. When they do, we'll re-verify everything on this page and change the date at the top. Until then, the tense of one sentence on their website is the whole answer.