MCP Server for Drupal
About
A TypeScript-based MCP server that acts as a companion to the Drupal MCP module, communicating via STDIO.
Details
- Author
- Omedia
- GitHub stars
- 51
- Downloads
- 314
- Categories
- Developer Tools, Other, Automation
Jump to
- Works with Drupal MCP module via STDIO transport
- Exposes resources (templates, reads) and tools (calls)
- Supports authentication via token or basic auth
- Available as Docker image, compiled binary, or JSR package
- Built with Deno and signed with cosign
- No prompts are exposed
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
MCP Server for DrupalCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install via Docker, compiled binary, or JSR package. Configure the server with --drupal-url and authenticate using environment variables (DRUPAL_AUTH_TOKEN, DRUPAL_AUTH_USER, DRUPAL_AUTH_PASSWORD). Example for Docker: set command to docker and args to ["run", "-i", "--rm", "ghcr.io/omedia/mcp-server-drupal", "--drupal-url=__DRUPAL_BASE_URL_"].
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mcp server for drupal": {
"mcp-server-drupal": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/omedia/mcp-server-drupal",
"--drupal-url=__DRUPAL_BASE_URL_"
],
"env": []
}
}
}
}McpServers
{
"mcp-server-drupal": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/omedia/mcp-server-drupal",
"--drupal-url=__DRUPAL_BASE_URL_"
],
"env": []
}
}A TypeScript-based MCP server that acts as a companion to the Drupal MCP module, communicating via STDIO.
This is a typescript based companionModel Context Protocol(MCP)server for theDrupal MCP modulethat works with theSTDIOtransport. In order to useSSEtransport this server is not required.
[!important] Important 📖 Detailed docs are avilable atdrupalmcp.io
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 withdocker:
{ "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 theInstallationsection in the docs
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] Note Make sure to turn the authentication on the Drupal MCP module settings page.
[!note] Note If bothDRUPAL_AUTH_TOKENandDRUPAL_AUTH_USER/DRUPAL_AUTH_PASSWORDare set, the token will be used over the username and password.
📖 Check theAuthenticationsection in the docs for more details
- All instruments are defined by the Drupal API during the initialization phase
[!note] Note The server now exposes the following
- Resources (templates, reads)
- Tools (calls)
No prompts are exposed by the server for now
[!note] Note Use deno version2.0.0or above
deno task build --output build/mcp-server-drupal
[!tip] Tip To build for the specific platform use the--targetflag and check thedocs
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using theMCP Inspector, which is available as a deno task:
deno task inspector --drupal-url [DRUPAL_BASE_URL]
drupal_mcp_serverbinaries and container images are signed bycosignusing identity-based signing.
You can verify your binary by downloading thesignatures.tar.gzfile 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"
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
This server enables AI assistants and other MCP clients to interact with Directus instances programmatically.
Agency-grade MCP server for WordPress Elementor — multi-site fleet management, safe page/widget-level editing, template export/import, version tracking with snapshot/rollback.
Connect Cursor, Claude Code, or any MCP-compatible tool directly to your ElmapiCMS instance. Manage collections, content, and assets through natural language.
MCP server for NomaCMS. Manage collections, fields, content, and assets via AI agents.
Manage your Storyblok CMS using natural language through AI tools.
MCP server for WordPress: connect Claude, ChatGPT, Cursor, and other AI clients to manage content, edit themes, run WP-CLI, and automate self-hosted WordPress sites.
The MCP server for Bitrix24 provides AI assistants with structured access to the Bitrix24 API. It delivers up-to-date method descriptions, parameters, and valid values, allowing assistants to work with precise data instead of guesswork. This reduces code errors and accelerates Bitrix24 integration development.
Connect bugAgent to any MCP-compatible AI client. File, classify, and manage bugs, feature requests, and more directly from your AI coding assistant. No context switching, no copy-paste — just describe the issue and bugAgent handles the rest.
What Shopify did for ecommerce, Chipp does for AI agents. Build, deploy, and monetize AI agents for your business — no engineering team required.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
