Drupal

What is mcp-server-drupal?

mcp-server-drupal is a TypeScript-based companion server for the Drupal MCP (Model Context Protocol) module. It facilitates interaction with Drupal using the STDIO transport layer. This server is not required if you are using SSE transport.

How to use mcp-server-drupal?

mcp-server-drupal can be installed and used via several distribution channels:

• Docker container: A quick example for Docker usage is provided in the README, allowing you to run the server with a simple docker run command.
• Compiled binary: Available through releases.
• JSR package.

For detailed installation instructions, refer to the documentation.

Authentication

The server supports authentication via environment variables:

• DRUPAL_AUTH_TOKEN: For token-based authentication.
• DRUPAL_AUTH_USER and DRUPAL_AUTH_PASSWORD: For basic authentication. If both token and username/password are provided, the token takes precedence. Authentication must also be enabled in the Drupal MCP module settings.

Development

The project is built with Deno (version 2.0.0 or above). Development involves installing dependencies (deno install), running with auto-rebuild (bun task dev), and building the server (deno task build). Debugging can be done using the MCP Inspector.

Key Features of mcp-server-drupal

• STDIO Transport: Designed to work specifically with the STDIO transport layer for Drupal MCP.
• Multiple Distribution Channels: Easy deployment via Docker, compiled binaries, or JSR package.
• Flexible Authentication: Supports both token-based and basic authentication.
• Deno-based: Built with Deno for modern and efficient development.
• Resource and Tool Exposure: Exposes Drupal resources (templates, reads) and tools (calls) to the MCP.
• Binary and Image Verification: Binaries and container images are signed by cosign for integrity verification.

Use Cases of mcp-server-drupal

• Extending Drupal Functionality: Enables external applications to interact with Drupal's Model Context Protocol.
• Building Custom Integrations: Provides a robust server for integrating custom applications with Drupal.
• Headless Drupal Setups: Facilitates communication in headless Drupal architectures where external services need to interact with Drupal data and logic.

FAQ about mcp-server-drupal

• Is this server required for SSE transport? No, this server is specifically for STDIO transport. For SSE transport, this server is not needed.
• How can I authenticate with the server? You can use either a DRUPAL_AUTH_TOKEN or a combination of DRUPAL_AUTH_USER and DRUPAL_AUTH_PASSWORD environment variables. Remember to enable authentication in your Drupal MCP module settings.
• What kind of MCP elements does the server expose? The server currently exposes Resources (templates, reads) and Tools (calls). It does not expose prompts.
• What Deno version is required for development? Deno version 2.0.0 or above is recommended for development.
• How can I debug the server? The MCP Inspector, available as a Deno task, is recommended for debugging STDIO-based communication.

MCP Server for Drupal

This is a typescript based companion Model Context Protocol(MCP) server for the Drupal MCP module that works with the STDIO transport. In order to use SSE transport this server is not required.

[!IMPORTANT] 📖 Detailed docs are avilable at drupalmcp.io

Installation

The STDIO Binary is available through multiple distribution channels to accommodate various environments:

• Docker container
• Compiled binary
• JSR package

Here is a quick example of how to use the server with docker:

{
  "mcpServers": {
    "mcp-server-drupal": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/omedia/mcp-server-drupal",
        "--drupal-url=__DRUPAL_BASE_URL_"
      ],
      "env": {}
    }
  }
}

📖 For more details check the Installation section in the docs

Authentication

The server supports both authentication via environment variables. You can use either a auth token or a basic auth with username and password combination . The following environment variables are supported:

• DRUPAL_AUTH_TOKEN: The authentication token.
• DRUPAL_AUTH_USER: The username for authentication.
• DRUPAL_AUTH_PASSWORD: The password for authentication.

[!NOTE] Make sure to turn the authentication on the Drupal MCP module settings page.

[!NOTE] If both DRUPAL_AUTH_TOKEN and DRUPAL_AUTH_USER/DRUPAL_AUTH_PASSWORD are set, the token will be used over the username and password.

📖 Check the Authentication section in the docs for more details

MCP

• All instruments are defined by the Drupal API during the initialization phase

[!NOTE] The server now exposes the following

• Resources (templates, reads)
• Tools (calls)

No prompts are exposed by the server for now

Development

This project is built with Deno.

[!NOTE] Use deno version 2.0.0 or above

Install dependencies:

deno install

For development with auto-rebuild:

bun task dev

Build the server:

deno task build --output build/mcp-server-drupal

[!TIP] To build for the specific platform use the --target flag and check the docs

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a deno task:

deno task inspector --drupal-url [DRUPAL_BASE_URL]

Verifying the binaries and images

drupal_mcp_server binaries and container images are signed by cosign using identity-based signing.

You can verify your binary by downloading the signatures.tar.gz file from the release page, extracting the signature and running the following command:

cosign verify-blob ${YOUR_BINARY_NAME} \
--bundle signatures/${YOUR_BINARY_NAME}.bundle \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-identity-regexp https://github.com/Omedia/mcp-server-drupal/.github/workflows/release.yml@refs/tags/v \
--certificate-github-workflow-repository Omedia/mcp-server-drupal

On the container side you can verify the image by running the following command:

cosign verify ghcr.io/omedia/mcp-server-drupal:latest \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  --certificate-identity-regexp "https://github.com/Omedia/mcp-server-drupal/.github/workflows/release.yml@refs/tags/v"