A Model Context Protocol server
If you already use Drupal, the drupal mcp server is the piece that lets your assistant work with it directly. A Model Context Protocol server.
The STDIO Binary is available through multiple distribution channels to accommodate various environments:
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
DRUPAL_AUTH_TOKEN — The authentication tokenDRUPAL_AUTH_USER — The username for authenticationDRUPAL_AUTH_PASSWORD — The password for authenticationDebugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCPConfiguration is passed through the environment: DRUPAL_AUTH_TOKEN, DRUPAL_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Drupal's toolset — DRUPAL_AUTH_TOKEN, DRUPAL_AUTH_USER, DRUPAL_AUTH_PASSWORD and 1 more — is a fair guide to whether it matches your workflow. It is maintained by Omedia; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Drupal's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| DRUPAL_AUTH_TOKEN | The authentication token. |
| DRUPAL_AUTH_USER | The username for authentication. |
| DRUPAL_AUTH_PASSWORD | The password for authentication. |
| Debugging | Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a deno task: |
{
"mcpServers": {
"mcp-server-drupal": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/omedia/mcp-server-drupal",
"--drupal-url=__DRUPAL_BASE_URL_"
],
"env": {}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DRUPAL_AUTH_TOKEN | Credential the server authenticates with. | Yes |
| DRUPAL_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.