Skip to content
DrupalMCP

Key Components

MCP flow chart

The MCP protocol defines two transport methods for data exchange between client and server: HTTP and STDIO.

While HTTP is the most common and widely used method, STDIO is better suited for desktop LLM applications. For example, both Claude and Cursor use STDIO to communicate with MCP servers.

To turn your Drupal site into an MCP server, you need to support both transport layers — and the Drupal MCP module does exactly that.
HTTP support comes naturally, since Drupal is already an HTTP-based system.
For STDIO, however, we need a small middleware component that runs locally and handles communication via the STDIO protocol.

So, the full setup consists of three components:

  1. Drupal MCP Module (Server)
  2. Optional STDIO Binary (Middleware)
  3. LLM application (or any MCP client, including the Drupal MCP Client)