Droost

How it works

What Droost is, and how an AI agent turns a request into a working site — explained from zero.

Start here: what is Droost?

You already use an AI coding assistant — Claude Code, Codex, Cursor. It is great at writing code, but a Drupal site is more than code: content types, fields, displays, views, pages. Droost gives your assistant hands on the real site. It is a Drupal module exposing 54 precise tools over MCP, the open standard AI assistants use to call external capabilities.

The difference from prompting alone: the agent never guesses. It reads what actually exists on your site, rehearses every change before writing, writes only through tools a human has unlocked, and verifies the result by reading it back. Drupal itself validates every write.

From idea to site

Say you ask for "a site for my bakery, with a browsable menu of pastries". Every build follows the same arc:

  • Understand
    read the site: versions, types, components
  • Model
    a pastry content type with real fields
  • Compose
    each field bound to a design component
  • List
    the menu page with filters, from one spec
  • Assemble
    home and about as component trees

Every surface is one of three things

The agent sorts every visible thing on your site into one of three buckets — and that decision picks the tool. This is the playbook it is taught.

Structured content droost_display

Repeatable things with fields — products, events, people. The bundle's view display is composed from Single Directory Components: droost_display_compose.

Freeform pages droost_canvas

Landing pages and one-offs are Drupal Canvas component trees, validated by Canvas's own constraints: droost_canvas_tree_set.

Listings droost_views

Inventories, search pages, and featured rows are real Views composed from an intent spec: droost_views_compose.

The safety loop

Every change follows the same rhythm — nothing lands unrehearsed, and nothing goes unverified:

  • Discover
    what exists, what is valid
  • Rehearse
    dry_run: validate, write nothing
  • Write
    through a gate a human opened
  • Verify
    read it back with the matching tool
the shape of every build — here, a listing
droost_views_handlers   -> what is filterable, and how
droost_views_compose     -> dry_run: true
droost_views_compose     -> the real write
droost_views_get         -> read it back, verified

This page practices what it preaches

The reference at /tools is a droost_views-composed view of nodes imported from the live tool registry, rendered as SDC cards composed by droost_display_compose, on Canvas pages written by droost_canvas_tree_set — all through the same MCP tools any agent gets. Even these flow diagrams are the theme's steps component, placed by the agent.

Meet the playbook