Omedia/mcp-server-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:
📖 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:
For development with auto-rebuild:
Build the server:
> [!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:
Verifying the binaries and images
drupal_mcp_server binaries and container images are signed by cosign using identity-based signing.