Drupal

Drupal

Server for interacting with Drupal using STDIO transport layer.

48
Stars
7
Forks
4
Releases

Overview

This is a TypeScript-based companion MCP server for the Drupal MCP module that operates over the STDIO transport. It serves as a bridge between MCP-enabled tooling and Drupal's MCP implementation, exposing a finite set of capabilities initialized via the Drupal API. At startup, all instruments are defined by Drupal, and the server exposes two primary categories: Resources (templates, reads) and Tools (calls). Prompts are not exposed by the server. The MCP server can be distributed as a Docker container, a compiled binary, or a JS package (JSR), and is started by supplying the Drupal base URL (e.g., via --drupal-url). Authentication is supported via environment variables using either a token (DRUPAL_AUTH_TOKEN) or a basic username/password (DRUPAL_AUTH_USER/DRUPAL_AUTH_PASSWORD); if both forms are provided, the token takes precedence. Development uses Deno (2.0.0+) with commands for installation, building, and optional auto-rebuild. For debugging, the MCP Inspector is recommended. Binaries and container images are cosign-signed, with verification steps provided in the release notes. Detailed documentation is available at drupalmcp.io.

Details

Owner
Omedia
Language
TypeScript
License
MIT License
Updated
2025-12-07

Features

Drupal-defined instruments

All instruments are defined by the Drupal API during initialization, enabling Drupal-driven behavior.

Resources and Tools exposure

Exposes Resources (templates, reads) and Tools (calls) through MCP; no prompts are exposed.

STDIO transport focus

Designed for STDIO transport; SSE transport is not required.

Authentication support

Supports DRUPAL_AUTH_TOKEN or DRUPAL_AUTH_USER/DRUPAL_AUTH_PASSWORD; token preferred if both are set.

Multi-distribution availability

Available as Docker container, compiled binary, and JS package (JSR).

Deno-based development

Built with Deno; requires 2.0.0+; includes install, build, and dev commands.

Debugging tooling

Supports debugging via the MCP Inspector.

Binaries and image verification

Cosign-based signing; verification steps provided for binaries and container images.

Audience

Drupal developersInteract with MCP in Drupal via STDIO to access resources and tools.
MCP integratorsUse MCP-enabled tooling to call Drupal resources over STDIO.
DevOps engineersDeploy and monitor the STDIO MCP server in Dockerized environments.

Tags

DrupalMCPSTDIOTypeScriptDenOServerDockerAuthentication