Mcp Server Drupal

What is Mcp Server Drupal about?

Mcp Server Drupal offers a TypeScript‑based companion server for the Drupal MCP module, enabling communication through the STDIO transport. It exposes Drupal‑defined resources (templates, reads) and tools (calls) for Model Context Protocol clients.

How to use Mcp Server Drupal?

• Installation: Choose one of the distribution channels:
  • Docker container (ghcr.io/omedia/mcp-server-drupal)
  • Pre‑compiled binary from the GitHub releases page
  • JSR package (@omedia/mcp-server-drupal)
• Docker example:

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

• Authentication: Set one of the following environment variables before starting the server:
  • DRUPAL_AUTH_TOKEN – token authentication (preferred)
  • DRUPAL_AUTH_USER and DRUPAL_AUTH_PASSWORD – basic authentication
• Running: After installation, start the server with the chosen command; it will listen on STDIN/STDOUT for MCP messages.

Key Features

• STDIO‑only transport (SSE not required)
• Auto‑generated resources and tools based on Drupal API at initialization
• No prompt exposure (focus on data and actions)
• Built with Deno 2.0+; supports compiling to native binaries
• Signed binaries and container images (Cosign) for supply‑chain security
• Debugging support via the MCP Inspector Deno task

Use Cases

• Enable AI agents to query Drupal content (templates, reads) and invoke Drupal services (tools) through a lightweight STDIO bridge.
• Provide a secure, signed execution environment for production deployments of MCP‑enabled Drupal sites.
• Facilitate local development and debugging of MCP interactions with Drupal using the built‑in inspector.

FAQ

• Do I need this server for SSE transport? No, the server is only required for STDIO. SSE works without it.
• Which authentication method takes precedence? If both token and basic credentials are set, the token (DRUPAL_AUTH_TOKEN) is used.
• How can I verify the downloaded binary or Docker image? Use the provided cosign verify-blob (binary) or cosign verify (image) commands with the signature bundles from the release page.
• Can I run the server on Windows? Yes, via the Docker container or the compiled Windows binary.
• What Deno version is required? Deno 2.0.0 or newer.
• How do I debug MCP messages? Run the deno task inspector --drupal-url [DRUPAL_BASE_URL] task to launch the MCP Inspector.

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"