Overview
Features
Drupal-defined instruments
All instruments are defined by the Drupal API during initialization, enabling Drupal-driven behavior.
Resources and Tools exposure
Exposes Resources (templates, reads) and Tools (calls) through MCP; no prompts are exposed.
STDIO transport focus
Designed for STDIO transport; SSE transport is not required.
Authentication support
Supports DRUPAL_AUTH_TOKEN or DRUPAL_AUTH_USER/DRUPAL_AUTH_PASSWORD; token preferred if both are set.
Multi-distribution availability
Available as Docker container, compiled binary, and JS package (JSR).
Deno-based development
Built with Deno; requires 2.0.0+; includes install, build, and dev commands.
Debugging tooling
Supports debugging via the MCP Inspector.
Binaries and image verification
Cosign-based signing; verification steps provided for binaries and container images.
Who Is This For?
- Drupal developers:Interact with MCP in Drupal via STDIO to access resources and tools.
- MCP integrators:Use MCP-enabled tooling to call Drupal resources over STDIO.
- DevOps engineers:Deploy and monitor the STDIO MCP server in Dockerized environments.




