Connect Drupal to Model Context Protocol

A TypeScript-based STDIO companion server for the separate Drupal MCP module, which runs inside a Drupal site. This binary is the bridge that lets an MCP client talk to that module over STDIO transport; all of the actual MCP instruments, resources and tools, are defined by the Drupal API itself during initialization rather than hardcoded in this server, so what's available depends entirely on the connected Drupal site's configuration and module setup. If a Drupal site is set up for SSE transport instead, this companion server is not needed at all.

Use it when an MCP client needs STDIO access to a Drupal site running the Drupal MCP module - the server itself is a thin transport bridge, so its actual capabilities are whatever that Drupal site's MCP module exposes, currently resources, templates and reads, and tools, calls, with no prompts exposed yet. It requires the Drupal MCP module to be installed and configured on the target site, with authentication explicitly enabled in that module's settings page - without that, the STDIO server has nothing valid to connect to. Authentication supports either a single auth token or a username and password pair; if both are configured, the token takes precedence.

The server dynamically discovers and exposes whatever the connected Drupal site's MCP module defines at initialization: resources (templates and reads) and tools (calls). No prompts are exposed by the server at this time. Distribution is via a Docker container, a compiled binary for multiple platforms, or a JSR package, and released binaries and container images are signed with cosign for identity-based verification against the project's GitHub release workflow.

Via Docker:

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

Set DRUPAL_AUTH_TOKEN, or both DRUPAL_AUTH_USER and DRUPAL_AUTH_PASSWORD, as environment variables to authenticate, after enabling authentication in the Drupal MCP module's settings.

Drupal site administrators and developers who want an MCP client to reach a Drupal site's own MCP-exposed resources and tools over STDIO transport, with the actual capabilities defined and controlled entirely on the Drupal side. The project is built with Deno 2.0.0+, and its own MCP Inspector task (deno task inspector --drupal-url) helps debug the STDIO connection during development, since stdio-based servers are otherwise hard to inspect directly.