This project is not covered by Drupal’s security advisory policy.

Drupal, built by AI agents the way your team would build it.

Droost gives an AI coding agent two things it does not have on its own:
first-hand knowledge of the Drupal site in front of it, and a process that
takes every change through plan → code → test → complete, with a gate at
each step that the agent cannot talk its way past.

This page is the map. Droost is several projects, some on drupal.org and
some on GitHub, and each does one job. Start here, then follow the link to
the part you need.

Website and documentation: droost.org

The three parts

1. Droost, inside the site (drupal/droost)

A Drupal module that lets an agent read the live site and change it through
checked writes: entity types and fields, configuration and its drift,
routes, services, logs, Views, displays and Canvas pages. Its 54 tools are
Tool API tools, so they are reachable
from drush droost:tool, Drupal AI's function calling and MCP. They are
grouped into three permissions:

  • content tools: what an editor manages. Safe for production.
  • build tools: configuration, fields, Views, displays. Development only.
  • developer tools: the database, modules, PHP evaluation. Local only.

Every write sits behind a gate in settings.droost.php, which only a person
at a terminal can arm. droost_mcp offers the content tools to Claude
Desktop, claude.ai and other MCP clients, holding each call to the
connected account's own Drupal access.

2. The brain, what the agent knows about the code

droost code:wiki, droost code:tree and droost search:arch: a wiki
page for every installed contrib module and theme, the code's structure
(classes, hooks, services, routes), and plain-text search over the
documentation. It reads the project's files and a local code index. No
Drupal is booted and drush is never called, so it answers in milliseconds,
and still answers while the site is broken.

3. The workflow, how a change gets built

One command, droost, runs each piece of work as a phased run:
plan → code → test → complete. Every phase has an entry gate and an
exit gate: coding standards, static analysis, unit and browser tests,
configuration that exports clean, documentation that still matches the
code. You choose what "pass" means per project in one version-controlled
file, droost/droost.yml, and dial the strictness from low to max. A
harness guard holds the agent to the run: no edits out of phase, and no
running the operator's commands or rewriting the rules it is held to.
Claude Code today.

The brain and the workflow ship together as
droost/workflow, a PHP
package installed in the project's own tools/droost/ folder. It is not a
Drupal module and needs no site to run. The module and the command work
independently, and work best together.

Drupal.org projects

Project What it is Version
Droost The module: the site's tools for agents, with the submodules droost_build, droost_dev, droost_canvas, droost_mcp, droost_ai and droost_devel 2.0.x
Droost UI Kit Builds Manage Display from Single Directory Components, on UI Patterns 2, through droost's build tools 2.0.x
Droost CMS A recipe for Drupal CMS sites an agent builds: the starter, Canvas, UI Patterns, Droost Theme and droost's content tools 1.0.x
Droost Theme An agent-first base theme: Tailwind v4 and daisyUI with no build step, design tokens in one file, 21 Canvas-ready components 1.0.x

Droost UI Patterns is
retired; use Droost UI Kit.

Repositories

Package What it is
droost/workflow (Packagist) The droost command: the knowledge commands, the phased run and its gates, the guard
droost/engine (Packagist) The framework-free engine beneath it: the files it writes for agent harnesses (AGENTS.md, CLAUDE.md, skills), and the wiki and code-search cores

Getting started

  • A new site: start from Droost CMS
    on a fresh Drupal CMS project. It brings the module, the theme and a
    worked design pattern.
  • An existing site: install the
    Droost module for the site's
    tools, and droost/workflow
    for the knowledge commands and the workflow.

The full guides are at droost.org/docs.

Requirements

  • Drupal 11.3 or later, PHP 8.3 or later.
  • Tool API, for the module.
  • An AI coding agent. The guard supports Claude Code today.

Support

Report an issue in the queue of the project it belongs to: the module's,
the recipe's, the theme's or UI Kit's on drupal.org, and the command's or
the engine's on GitHub. Not sure which? Use
Droost's issue queue.

All Droost projects are GPL-2.0-or-later.

Project information

Releases