Drupal Code Query MCP server

Name: Drupal Code Query MCP server
Author: mcp.tresbien.tech

MCP serverMCP

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"drupal-code-query","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability108/108 checks ok

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	16 ms	server drupal-code-query 0.48.0 · protocol 2025-06-18 · 17 tools
10 h ago	mcp initialize	ok	200	19 ms	server drupal-code-query 0.48.0 · protocol 2025-06-18 · 17 tools
17 h ago	mcp initialize	ok	200	18 ms	server drupal-code-query 0.48.0 · protocol 2025-06-18 · 17 tools
24 h ago	mcp initialize	ok	200	50 ms	server drupal-code-query 0.48.0 · protocol 2025-06-18 · 17 tools
31 h ago	mcp initialize	ok	200	23 ms	server drupal-code-query 0.48.0 · protocol 2025-06-18 · 17 tools
2 d ago	mcp initialize	ok	200	20 ms	server drupal-code-query 0.48.0 · protocol 2025-06-18 · 17 tools
2 d ago	mcp initialize	ok	200	25 ms	server drupal-code-query 0.48.0 · protocol 2025-06-18 · 17 tools
2 d ago	mcp initialize	ok	200	22 ms	server drupal-code-query 0.48.0 · protocol 2025-06-18 · 17 tools
3 d ago	mcp initialize	ok	200	22 ms	server drupal-code-query 0.48.0 · protocol 2025-06-18 · 17 tools
3 d ago	mcp initialize	ok	200	24 ms	server drupal-code-query 0.48.0 · protocol 2025-06-18 · 17 tools

Tools observed via MCP handshake

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 composer_lock after 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 the question. - No a
get_change_record — Return one core change record in full: title, flavour, target version, machine-checkable tracks, linked issues, linked core symbols, and contrib adoption counts
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 symbol-level diff, u
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: "who subclasses Fo
list_projects — List drupal.org projects after filters, largest install base first, paged. Examples: "top modules without an 11.4 branch", "themes over 10k installs without sec
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
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 containing it instea
project_profile — Answer "what is this contrib project, how big is it, which core versions does it support, what moves with it" for one drupal.org project. Pending change records
project_upgrade_report — Answer "is this contrib project ready for a target core version, and what work is left". For one record's detail, use get_change_record. For a symbol's users, u
query_dataset — Run read-only DuckDB SELECTs over the dataset behind the other tools, for a question none of them asks. Call describe_dataset first; it lists the 36 views, thei
reroll_patch — Re-roll one composer patch that check_patches reported conflicts or fuzzy: a new diff that applies to the installed release. Call check_patches first for the wh
scan_composer — Which of a site's drupal/* packages need a new release for a target core, and which have none? Send composer.lock and composer.json once; do not query one packa
search_code — Search the source of every indexed contrib project, plus core, for a code pattern: which files, or with by_repo which projects. Who-uses-a-core-symbol counts: l
subsystem_coupling — Answer "what else tends to fail when a merge request touches this core subsystem" from CI history over about 9,000 core merge requests. With issue_nid: "which s
what_changed — Answer "what changed in the core API between two core versions": symbols added, deprecated and removed, as ranked groups with counts. One symbol: lookup_core_sy
wordpal_theme — Answer "does this WordPress block theme convert to Drupal with WordPal". The WordPal gallery converts every block theme on wordpress.org each night. With slug:

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

Read-only access to a nightly static analysis of Drupal core and 12,500+ contrib projects. Core change records with their break-or-new-API flavour. Core symbol lifecycle and which projects still call each symbol. Per-project upgrade readiness with file and line evidence. Install history, dependencies and co-installs per project. The core subsystem co-failure graph built from CI runs. Regex code search across contrib and core. Composer patch verdicts against any release tag: applies, already shipped, or needs a re-roll. Ad-hoc SQL over the same parquet bundle. Whether a WordPress block theme converts to Drupal with WordPal. Every answer has index-wide counts and a ranked head.

drupalphpcode-searchdeprecationsupgrade

kind ARD catalog (/.well-known/ard.json)

name ARD catalog (/.well-known/ard.json)

summary ARD catalog (/.well-known/ard.json)

version Official MCP Registry

description ARD catalog (/.well-known/ard.json)

homepageUrl ARD catalog (/.well-known/ard.json)

publisherUrl ARD catalog (/.well-known/ard.json)

publisherName ARD catalog (/.well-known/ard.json)

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrytech.tresbien/drupal-code-query

first seen 2 mo ago · fetched 2 d agoopen ↗

ARD catalog (/.well-known/ard.json)urn:air:mcp.tresbien.tech:server:drupal-code-query

first seen 2 mo ago · fetched 9 d agoopen ↗

Field history (12 recent events)

9 d ago · declared · description → "Read-only access to a nightly static analysis of Drupal core and 12,500+ contrib projects. Core change records with the
9 d ago · declared · version → "0.48.0"
1 mo ago · declared · version → "0.42.0"
2 mo ago · declared · version → "0.41.0"
2 mo ago · declared · summary → "Read-only access to a nightly static analysis of Drupal core and 12,500+ contrib projects. Core change records with the
2 mo ago · declared · name → "Drupal Code Query MCP server"
2 mo ago · declared · description → "Read-only access to a nightly static analysis of Drupal core and 12,500+ contrib projects. Core change records with the
2 mo ago · declared · publisherName → "mcp.tresbien.tech"
2 mo ago · declared · publisherUrl → "https://mcp.tresbien.tech"
2 mo ago · declared · version → "0.40.0"
2 mo ago · declared · publisherName → "tech.tresbien"
2 mo ago · declared · description → "Drupal core API changes, contrib usage, upgrade readiness, patch verdicts, code search, SQL."

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from