The Drupal Code Query MCP server,
connected in one click.

“Use “check_patches”: Does each composer patch still apply to the release the site installed, and is its fix already in that release? - Send composer_json and com.”

“Use “describe_dataset”: Learn the dataset before writing SQL for query_dataset. Call it with no arguments first. Returns text. Prefer a typed tool when one answers.”

“Use “get_change_record”: Return one core change record in full: title, flavour, target version, machine-checkable tracks, linked issues, linked core symbols, and con.”

“Use “list_change_records”: List the core change records (the human write-ups) that target a range of core versions, tagged by flavour and ranked, with counts. For the.”

check_patches — Does each composer patch still apply to the release the site installed, and is its fix already in that release? - Send composer_json and com

describe_dataset — Learn the dataset before writing SQL for query_dataset. Call it with no arguments first. Returns text. Prefer a typed tool when one answers

get_change_record — Return one core change record in full: title, flavour, target version, machine-checkable tracks, linked issues, linked core symbols, and con

list_change_records — List the core change records (the human write-ups) that target a range of core versions, tagged by flavour and ranked, with counts. For the

list_class_relations — List the contrib classes that extend, implement or use a core class, interface or trait, one row per edge with file and line, paged. Example

list_projects — List drupal.org projects after filters, largest install base first, paged. Examples: "top modules without an 11.4 branch", "themes over 10k

list_symbol_users — List every contrib project using one core symbol, or any symbol in a class of symbols, one row per project, paged, with the matched symbols.

lookup_core_symbol — Answer "is this core symbol safe to use, and who still uses it" for one symbol. A name that resolves to nothing returns the catalog entries