← tresbien.tech

INDIVIDUAL MCP TOOL

get_change_record

Return one Drupal core change record in full: its title, flavour, target core version, machine-checkable tracks, linked issue numbers, and how far contrib has adopted it.

tresbien.technone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.tresbien.tech/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_change_record and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

tresbien.tech

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.

Related tools

  • list_change_records — List the Drupal core change records targeting a range of core versions, each tagged with its flavour so a caller can separate work that is forced from work that is merely offered.
  • list_changed_symbols — List every symbol on one side of the core API diff between two core versions, one row per symbol, in pages.
  • lookup_core_symbol — Look up one Drupal core symbol and answer whether it is safe to use, and who still uses it.
  • project_upgrade_report — Answer whether one contrib project is ready for a target Drupal core version, and what work is left.
  • query_dataset — Run one read-only DuckDB query over the dataset behind the other tools, for a question none of them asks.
  • search_contrib_code — Search the source of every indexed Drupal contrib project, plus core, for a code pattern.
  • what_changed — Diff the Drupal core API surface between two core versions: which symbols were added, which were deprecated, and which were removed.