Drupal-Code-Query Adds Tools for Patch-Heavy Drupal Upgrades

Maintainers using the Drupal-Code-Query MCP server now have three tools aimed at Composer compatibility and patch handling during Drupal upgrades. Drupal core committer Théodore Biadala described the additions in a Très Bien Tech blog post published on 26 August 2026. The tools are scan_composer, check_patches, and reroll_patch.

The scan_composer tool accepts composer.lock, composer.json, and a target Drupal core version to assess installed Drupal packages against that target. check_patches checks whether an existing Composer patch still applies to a module release or whether its change is already included, while reroll_patch can return a re-rolled diff for a patch that no longer applies. Biadala says these results come from locally available contributed-project repositories and code and issue indexing rather than an LLM. Composer scanning and patch checking are also exposed through read-only API endpoints that he says do not query an LLM when producing a response.

Biadala illustrates the maintenance problem with a Drupal 10.6 project containing 120 contributed modules and 47 patches that needs to move to Drupal 11.4. In his own tests, he says using the MCP tools with Claude Opus 5 reduced an update from 40 minutes to 30 minutes, used about half as many tool calls, and cost 26% less; he also reports that a Mistral-based tool completed an update in seven minutes instead of 20 minutes. These figures come from Biadala's tests and are not independently validated benchmarks. More details about the tools, APIs, and test results are available in Biadala's original Très Bien Tech post.