Drupal MCP Toolkit: Four Modules for Agent-Driven Site Management

As AI agents become part of the Drupal workflow, we need infrastructure that makes automation traceable, predictable, and composable. I built four small Drupal modules that together form an MCP Toolkit for agent-driven site management. The Problem When agents modify configuration, create content, or run audits on a Drupal site, you need: Visibility into what agents did and when. Structured access to content and config without scraping rendered pages. Audit checks that agents can invoke programmatically. Configuration snapshots for diffing and CI validation. Each of these is a small, focused concern — so I built each as a separate module with a narrow, well-defined surface. The Toolkit 1. MCP Audit Server A lightweight server that sits between an MCP client and Drupal, capturing structured events: what tools ran, what endpoints were touched, and when. This gives you a decoupled audit trail that doesn't pollute Drupal's application logs. Key takeaway : Treat audit trails as a first-class