Drupal's AI Plan: Less Hype, More Receipts (and Citations)

Drupal's AI Plan: Less Hype, More Receipts (and Citations)

Every CMS on the planet spent the last two years slapping a sparkly "AI" button on the toolbar and calling it a strategy. Drupal, true to form, showed up at DrupalCon Rotterdam with something more unusual: a working demo, a governance story, and a to-do list. It's the Hermione Granger approach to AI — slightly less flashy, considerably more homework done.

Northmoor University Opens Its Doors

In his DriesNote on September 29, Drupal project lead Dries Buytaert framed the platform's roadmap around three pillars: multilingual, JavaScript/headless, and AI. A follow-up post on Drupal.org from the AI Initiative lays out what's actually usable right now, headlined by the Drupal AI Demo, a fictional "Northmoor University" site live at drupal.org/ai/demo.

The demo shows AI scanning content for accuracy, tone, and inclusive language; letting editors fix flagged issues themselves without waiting on a specialist; answering visitor questions with every source cited; and generating drafts that require human review before anything gets published. Every interaction is logged. The initiative has now passed 100 contributors, and Dries also showed AI-assisted component building in Drupal Canvas, where the assistant checks its own work against Canvas Workbench, ESLint, and the Canvas CLI.

Twenty Attributes Instead of a Thousand Lines

The quietly huge item is Model Context Protocol support. According to the initiative, exposing Drupal capabilities to AI agents via MCP drops from roughly 1,000 lines of code to around 20 PHP attributes, with prototype modules including Simple OAuth, MCP Server, Tool API, and FlowDrop. Next up is the "Rosetta Sprint," a four-day maintainer summit to standardize how Drupal describes its capabilities to agents and orchestration tools (date and location TBA).

Here's the angle that matters for anyone running a real organization: the demo's headline features aren't "write 400 blog posts while you sleep." They're citations, human sign-off, and audit logs. That's the stuff legal, compliance, and accessibility teams actually ask about before they let AI anywhere near a public website, and it's where most bolt-on AI plugins quietly fall down.

Drupal isn't trying to win the loudest-AI contest; it's trying to win the one where the AI is still allowed to run after the first audit. Smart bet.

If the Northmoor demo has you wondering what grounded, human-reviewed AI would look like on your own Drupal site, let's talk through it — this is exactly the kind of integration we build.

Source: Drupal.org