Developer Tools

tresbien.tech

Provides Drupal developers with core change records, symbol lookups, and upgrade readiness reports.

1 endpoint16 known toolsFirst detected August 18, 2026Last detected September 18, 2026

ENDPOINT 1

https://mcp.tresbien.tech/mcp

No auth detected

MCP server metadata

Name: drupal-code-query
Version: 0.42.0

Capabilities

tools.listChanged

Server instructions

Tools over Drupal core and contrib: - core change records and the core symbol lifecycle - contrib upgrade readiness, install history and dependencies - the core subsystem co-failure graph - code search across contrib and core, and SQL over the same data Each dataset tool returns index-wide counts, a ranked head of results, and identifiers for a narrower call. Quote the counts when stating scale. Use the identifiers when the user asks for detail. For a question no tool asks, call describe_dataset first, then query_dataset with a recipe. Upgrading a site takes three calls, in this order. 1. scan_composer with composer_lock set to its path (composer.lock) and composer_json as text: the answer is a curl command. Run it from the site root; it uploads the files and prints the plan. A slim lock fits as text instead. 2. check_patches with the same files, plus patch_files for every patch, after composer update: gives every composer patch its verdict against the installed release. 3. reroll_patch with the same project, version and patch, once per item that came back conflicts: returns the re-rolled diff. Do not download releases. Do not run patch --dry-run. Do not re-roll by hand.

Known tools 16

check_patches

Does each composer patch still apply to the release the site installed, and is its fix already in that release?

Inferred read-only

describe_dataset

Learn the dataset before writing SQL for query_dataset.

Inferred read-only

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.

Inferred read-only

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.

Potential side effects

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.

Inferred read-only

list_projects

List drupal.

Inferred read-only

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.

Inferred read-only

lookup_core_symbol

Answer "is this core symbol safe to use, and who still uses it" for one symbol.

Inferred read-only

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.

Inferred read-only

project_upgrade_report

Answer "is this contrib project ready for a target core version, and what work is left".

Inferred read-only

query_dataset

Run read-only DuckDB SELECTs over the dataset behind the other tools, for a question none of them asks.

Inferred read-only

reroll_patch

Re-roll one composer patch that check_patches reported conflicts or fuzzy: a new diff that applies to the installed release.

Inferred read-only

scan_composer

Which of a site's drupal/* packages need a new release for a target core, and which have none?

Inferred read-only

search_code

Search the source of every indexed contrib project, plus core, for a code pattern: which files, or with by_repo which projects.

Inferred read-only

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.

Inferred read-only

what_changed

Answer "what changed in the core API between two core versions": symbols added, deprecated and removed, as ranked groups with counts.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.drupal-code-query]
url = "https://mcp.tresbien.tech/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: drupal-code-query
Remote MCP URL: https://mcp.tresbien.tech/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "drupal-code-query": {
      "url": "https://mcp.tresbien.tech/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "drupal-code-query": {
      "type": "http",
      "url": "https://mcp.tresbien.tech/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "drupal-code-query",
  "transport": "streamable-http",
  "url": "https://mcp.tresbien.tech/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.