Most AI-in-your-CMS pitches look like a toddler holding car keys: lots of enthusiasm, very little supervision. Drupal just put out something closer to a driving instructor with a passenger-side brake pedal, and frankly, it's the most grown-up AI demo we've seen from a CMS all year.
Northmoor University, Population: Guardrails
In a Drupal.org post published October 2, Jeremy Chinquist laid out what the Drupal AI initiative shipped after Dries Buytaert's DrupalCon Rotterdam keynote. The headline item is the Drupal AI Demo, a full fictional site called Northmoor University, live now at drupal.org/ai/demo. It scans programs, courses, people, news and policy pages for weak content, checking accuracy, tone and inclusive language, and then lets regular content editors fix the flagged items without calling in a specialist.
On the visitor side, the demo answers questions using only the site's own content, with citations, and politely declines anything outside that scope. AI assistants can draft page updates, but those drafts need a human to approve them before they go live, and every interaction is logged. Drupal Canvas components can be AI-assisted as well, with the output checked against Canvas Workbench, ESLint and the Canvas CLI.
From 1,000 Lines to 20 Attributes
The forward-looking bit is where developers should lean in. Right now, exposing a Drupal module's features to AI assistants over Model Context Protocol (MCP) takes about 1,000 lines of code. A prototype recipe built on Simple OAuth, MCP Server and Tool API modules gets that down to roughly 20 PHP attributes, under a "describe once, use in multiple places" idea. Next up is the Rosetta Sprint, a four-day session with key maintainers to standardize capability descriptions that AI agents, orchestration platforms and frontends can all read. Date and location are still to be announced.
The part most people will skim past is the boring stuff: approval workflows, audit logs, refusing out-of-scope questions. That's exactly what legal, compliance and a nervous university provost need to see before they let a chatbot anywhere near the admissions page. Drupal has always sold itself on governance, and here it's applying that same instinct to AI. Dries described a "reputation gap" in Rotterdam, where Drupal is more capable than outsiders think, and a demo like this does more to close it than any keynote slide could.
The AI writes the draft, a human approves it, and the logs record who did what. That's how you get AI onto a site without needing a crisis-comms plan afterward.
If you've been wanting AI-assisted content workflows on your Drupal site but aren't keen on a chatbot freelancing on your homepage, let's talk about wiring in the guardrails first.
Source: Drupal.org