Part of the Droost ecosystem · 5 projects
Droost provides AI coding agents with structured information about your Drupal application, exposing details like versions, configuration, routes, and database schema. It acts as a developer acceleration toolkit, offering guarded operations and discoverable tools for agents, but should only be used in local development environments.
Let an AI agent ask your Drupal site about itself, and then change it
through checked, gated writes.
An agent writing Drupal code normally works blind. It does not know which
modules are installed, what entity types and fields exist, which service to
inject, or whether the last request errored, so it guesses. Droost gives it
the answers from the live site: entity types and fields, configuration and
its drift, routes, services, logs, Views, displays and Canvas pages. Each
answer is structured JSON, not shell output to parse.
drush droost:tool # the tools, by what they are about
drush droost:tool droost_entities help # what one does, and its arguments
drush droost:tool droost_entities '{"entity_type_id":"node"}'
Every tool is a Tool API tool, so the
rest of the ecosystem reaches it too: drush tool:run, Drupal AI's function
calling, and MCP Server's Tool API bridge. Each call checks the tool's
permission and its declared inputs before it runs, and returns one envelope:
{success, message, data}.
What an agent can ask, and do
54 tools: 9 in droost itself, 45 across five submodules.
- Read the site (ungated): application info, entity types and fields,
entity values, content queries and counts (trash-aware), configuration
(secrets redacted) with its drift and schema, the database schema and a
read-only query, routes with access, services with the interface to
type-hint, logs and the last error, permissions, pending updates, tokens,
URLs, runtime state (hooks, plugins, the theme registry), SDC components,
displays, Views and the request profiler. - Change the site (gated): configuration through the entity API,
fields, bundles and view modes, entity create, update and delete, Views,
module install and uninstall, cron, cache rebuild, raw SQL writes and PHP
evaluation.
Writes report what they left behind: the saved state of an entity, and what
still points at one that was deleted.
Three permissions, by what a tool touches
Permission Tools Whereuse droost content tools
entity values and writes, Canvas pages, listings, URLs, tokens
any site, production included
use droost build tools
configuration, fields, bundles, view modes, Views, displays, components
development and staging
use droost developer tools
routes, services, runtime state, logs, the database, modules, cron, PHP evaluation
local development only
Build and developer tools refuse any web request.
Submodules
- droost itself: the content tools, all a production site needs.
- droost_build: site building (configuration, fields, Views, displays).
Development sites only. - droost_dev: developer tools (introspection, the database, modules, PHP
evaluation). Local only. - droost_canvas: Canvas pages and their trees, page variants, component
toggles and an SDC lint against Canvas's requirements. - droost_mcp: the content tools over MCP, for editors.
- droost_ai: the site's AI function calls.
- droost_devel: generated content through Devel.
Writes are disarmed until a person arms them
Every write category has its own gate: allow_entity_write,
allow_config_write, allow_db_write, allow_module_ops,
allow_scaffold and allow_eval. The gates live in settings.droost.php
beside settings.php, never in exported configuration, so an armed gate
cannot travel to another site. Arming one needs an interactive terminal
(drush droost:gate), so an agent cannot arm a gate for itself. PHP
evaluation and raw SQL writes stay off until the site turns them on.
drush droost:gate # every gate and its state
drush droost:gate allow_eval on # turn on PHP evaluation, locally
/admin/config/development/droost shows every gate, and
/admin/reports/droost is a read-only status page.
Over MCP, for editors
droost_mcp offers the content tools to Claude Desktop, claude.ai and other
MCP clients, through MCP Server
and its Tool API bridge.
Every tool mapping ships disabled, and you enable the ones you want. Each
call is the connected account's own: entity access, field access and
validation apply just as in Drupal's own UI, writes need their switch armed,
and every call is kept in an audit log.
Install
Tool API is still in beta, so the site requires it at that stability:
composer require 'drupal/tool:^1.0@beta' 'drupal/droost:^2.0'
drush en droost
- For MCP, also require MCP Server and its bridge:
composer require 'drupal/mcp_server:^2.0@beta' 'drupal/mcp_server_tool_bridge:^1.0@beta'. - For agents: droost ships the
droost-toolsskill, which says which
tool does what and how the write rules work. - droost conflicts with twig 3.30.0, which breaks Drupal's escape filter.
If your project has it locked, usecomposer require -W ….
The rest of what an agent needs
This module is what the agent knows about the site. What it knows about
the code, and the process each change goes through, is the droost
command, installed in the project's own tools/droost/ folder. It is not a
Drupal module, never boots Drupal, and still answers while the site is
broken:
- droost/workflow (on
Packagist): the knowledge
commands (code:wiki,code:tree,search:arch) and the gated
plan → code → test → complete run. - droost/engine (on
Packagist): the engine
beneath it.
The module and the command each work without the other. Guides are at
droost.org.
Upgrading from 1.x or a 2.0 alpha
1.x is deprecated and no longer supported. There is no upgrade path
from 1.x, nor from the 2.0.0 alphas: 2.0.0 is rebuilt on Tool API, and
several submodules are gone (droost_eca, droost_examples, droost_snyk,
droost_tool_api, droost_workflow). Uninstall droost and every
droost_* submodule while its code is still on disk, then install 2.0
fresh:
drush pm:uninstall droost # and every droost_* submodule you enabled
composer remove drupal/droost
composer require 'drupal/tool:^1.0@beta' 'drupal/droost:^2.0'
drush en droost
Uninstall first, not after. A module left enabled whose code is gone from
disk breaks Drupal's bootstrap before anything could repair it.
Requirements
- Drupal 11.3 or later, PHP 8.3 or later.
- Tool API 1.0.0-beta12 or later.
- Drush 12 or later, for
drush droost:tool. - Optionally, core's Database Logging (
dblog), for the log tools.
Part of Droost Framework
Droost Framework is the
map of the whole ecosystem: the droost command, its repositories and the
documentation at droost.org. The Drupal projects:
Ask your assistant about Droost
Check compatibility with your Drupal and PHP version, maintenance and security coverage, from current release data. How it works
Depends on
Dependencies of the latest stable release
Required by
1 tracked project depends on this one
- Droost UI Kit 1 sites
More in the Droost ecosystem
Most installed first
Activity
Release Timeline
Releases
| Version | Type | Core | PHP | Release date | |
|---|---|---|---|---|---|
| 1.0.0-alpha2 | Pre-release | 10–11 | Jul 6, 2026 | ||
| 1.0.x-dev | Dev | 10–11 | Jun 25, 2026 |