The real agentic CMS story is not content generation. It's governed content operations.

On March 31, Kontent.ai launched Expert Agents — purpose-built AI agents that run continuously inside its Agentic CMS platform, handling content operations without waiting for human instructions. According to Kontent.ai, 60 organizations are already running the platform. The agents handle tasks that don't require human judgment, can be configured with natural language prompts, and operate within user permissions. Content doesn't publish until a person approves it.

Read past the press release, and something more interesting is happening. This isn't one vendor announcing a feature. It's a convergence point — where multiple CMS and DXP vendors arrived at the same architectural conclusion at roughly the same time.

AI writing assistance was the warm-up act

The first wave of CMS AI features was creative: generate a headline, rephrase this paragraph, suggest a meta description. That's useful. It's also table stakes now, and nobody's writing press releases about it anymore.

The current wave is different. Vendors are describing agents that audit content for accessibility violations and fix them. Agents that scan your entire site for SEO problems and update them. Agents that enforce brand style guides across thousands of pages. Agents that monitor content for policy compliance and flag or remediate automatically.

Acquia's three new AI agents for Acquia Source include a Site Builder Agent that creates multi-page campaign sites from a creative brief, an AI Writing Assistant optimizing for both search and answer engines, and a Web Governance Agent that scans and fixes accessibility and compliance issues (CMSWire). Siteimprove and Optimizely connected their AI agents directly — an agent-to-agent integration for accessibility remediation, governance, and optimization inside the CMS workflow (CMSWire).

That's not content generation. That's operational automation at scale.

What agentic CMS actually changes

Content systems are becoming execution environments

When an agent can update alt text across your entire image library, fix WCAG violations in your templates, or push updated policy language into thousands of pages, the CMS stops being a publishing tool and becomes something closer to an execution environment. The authoring interface is still there, but the real action is happening in background processes.

Kontent.ai's architecture makes this explicit. There are two layers: a Main Agent that lets teams operate the platform through natural language, and Expert Agents built for specific high-value operations — always on, always checking, acting within defined boundaries.

Governance is moving inside the workflow

The approval layer is built into these systems from day one. Kontent.ai agents don't publish without human sign-off. Acquia's governance agent flags violations before they go live. This is good — it's how you keep autonomous agents from doing something irreversible.

But there's a difference between governance of agent actions and governance of the information agents act on. The first is access control and approval workflows. The second is source truth quality. The CMS vendors are solving the first problem well. The second problem is largely assumed away.

MCP is turning content ops into enterprise infrastructure

Brightspot put it plainly: MCP servers are becoming expected infrastructure for content platforms. That matters because it means the CMS is no longer a standalone system — it's a node in a broader enterprise agent network. Content can flow in and out, be referenced by agents elsewhere in the stack, and be updated by processes that originate outside the CMS entirely.

That's a significant shift. When your content platform is an MCP server, what it contains is accessible as context to any authorized agent in your organization. The quality of that content becomes infrastructure quality, not just editorial quality. (More on the trust questions this raises: The real MCP problem isn't more tools — it's whether you can trust them.)

Knowledge freshness is the hidden bottleneck

Here's the problem nobody in the vendor announcements is addressing directly. Agents that execute accessibility remediation or SEO optimization are reading from somewhere. They're applying standards that come from a source. When an accessibility agent decides what "compliant alt text" looks like, it's drawing on rules. When an SEO agent decides to update content for AEO readiness, it's working from a definition of what that means.

If those underlying rules and standards are outdated — if WCAG 2.2 came out and the agent's knowledge still reflects 2.1, or if your brand voice guide was updated six months ago but the agent is working from the old version — the agent doesn't hesitate. It scales the stale standard across your entire content operation.

That's the real risk. Manual errors are isolated. Agent errors are systematic.

What this means for enterprise content teams

The operational upside is real. Agents can handle accessibility audits that used to require specialized contractors. They can enforce SEO and AEO standards at a pace no human team can match. They can catch policy violations before they reach a human reviewer. That's hours and budget recovered.

The governance responsibility shifts accordingly. The question a digital team used to ask was: did we catch this problem before publishing? The question now is: is the information our agents are working from actually current?

For organizations in regulated industries — healthcare, financial services, legal — this is not an abstract concern. An agent that applies an outdated clinical policy standard across patient-facing content because nobody updated the source document is a compliance problem, not a content quality problem. The scale of execution risk when agents read ungoverned knowledge is proportional to how autonomous those agents are. Agentic CMS is making them substantially more autonomous.

The layer that's still missing

Permission and approval controls are real progress. An agent that can't publish without a human sign-off is meaningfully safer than one that can act unilaterally.

But approval controls don't validate context. When a human reviewer approves an agent's work, they're approving the output based on what they can see. They're not auditing whether the standard the agent applied was current, whether the source document the agent referenced was accurate, or whether there's a contradiction between that document and three others in the same knowledge base.

That's the gap. The execution governance is improving. The knowledge governance is being assumed.

Platforms like Mojar AI address this at the layer below the CMS: source-attributed retrieval so every agent response traces back to a specific document, contradiction detection across the knowledge base, permission-aware access so agents see what they're supposed to see, and natural-language maintenance so keeping source documents current doesn't require a separate manual effort. The argument isn't that CMS vendors should build all of this themselves. It's that content operations running on agentic execution need a governed knowledge layer beneath them, and that layer doesn't come included with the CMS.

What to watch

The next 12 months will separate vendors who built agent features from those who built agent infrastructure. Watch for CMS platforms adding knowledge verification capabilities — not just workflow approvals, but source quality checks before agents act. Watch also for MCP-native integrations between content platforms and knowledge management layers. The teams that get this right won't win because they added the most agents. They'll win because their agents had access to knowledge that was actually worth trusting.