# Tresbien Drupal Code Query MCP server

Source: https://glimind.com/server/mcp-registry%2Ftech.tresbien%2Fdrupal-code-query
Registry id: `mcp-registry/tech.tresbien/drupal-code-query`
Status: live (checked 2026-10-27T04:27:03.004Z)

## Verdict

Tresbien Drupal Code Query MCP server answered 99.09% of Glimind's liveness checks over 30 days, better than 9% of MCP servers, with 981 ms median handshake and 43 outages in 90 days. Its agent-readiness grade is A (96/100) across 17 tools, costing an agent about 8,266 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.09% | 9% of MCP servers |
| Median handshake latency | 981 ms | 19% of MCP servers |
| p95 handshake latency | 3456 ms | — |
| Checks in 30 days | 4,991 | — |
| Outages, 90 days | 43 | — |
| Median recovery | 4 min | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 17 | — |
| Tool-list size for an agent | ~8,266 tokens | 33% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "tresbien-drupal-code-query-mcp-server": {
      "type": "http",
      "url": "https://mcp.tresbien.tech/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http tresbien-drupal-code-query-mcp-server https://mcp.tresbien.tech/mcp
```

## Tools (17)

- `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: 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.