MCPIO Alpha Introduces Two-Tool MCP Interface for Drupal

The MCPIO project has released version 1.0.0-alpha1, its first public alpha on Drupal.org. The module gives external AI clients a way to discover and run actions on a Drupal site through the Model Context Protocol. Dimitris Spachos, the project's maintainer, created MCPIO in Drupal.org's Artificial Intelligence ecosystem on 6 September 2026. Drupal.org lists amazee.io as a supporting organisation.

Model Context Protocol, usually shortened to MCP, is an open standard for connecting AI clients with external tools and data. In practical terms, it gives an AI application a structured way to ask what a system can do and then request an allowed action. MCPIO applies that model to Drupal, allowing an external client to discover available site operations instead of relying on a separate custom integration for every task.

The main difference in MCPIO is the small interface it presents to the AI client. The module exposes two MCP tools called search and execute. Search helps the client find an available Drupal action, while execute runs the selected action with the required arguments. These are entry points, not the full capability set, so two visible tools can provide access to many different Drupal operations behind them.

The initial alpha includes actions for tasks such as checking site health, running cron and cache operations, searching and reading content, creating drafts, updating revisions, publishing content, and retrieving user information. MCPIO can also make compatible actions from MCP Tools available through the same search-and-execute flow. MCP Tools currently documents 226 tools across 36 optional submodules, covering areas such as content types, fields, taxonomy, permissions, Views, Layout Builder, media, translations, and administration.

Drupal already has other projects for connecting sites to MCP clients, so MCPIO is not Drupal's first MCP server. The MCP Server project, for example, can expose individual Drupal tools directly to a client and supports a broader set of MCP features. MCPIO takes a different approach by keeping the client-facing interface limited to two entry points while the larger catalogue of Drupal actions remains behind them.

Access control still determines what an external client can do. MCPIO supports per-user API keys through Key Auth, which the project recommends, as well as HTTP Basic authentication. Drupal accounts also need the access mcpio endpoint permission, and administrators can decide which capability groups and MCP Tools plugins are exposed. The project's documentation says its execution path applies argument validation, permission checks, scopes, and read-only policies.

The release is still experimental. Drupal.org marks version 1.0.0-alpha1 as an alpha release and notes that the project is not covered by Drupal's security advisory policy. MCPIO declares MCP protocol version 2024-11-05, while the current MCP specification is 2026-07-28. The project also warns that clients requiring newer transport behaviour may not work with the current alpha.

MCP is also becoming more visible in Drupal's wider AI discussions. A DrupalCon Rotterdam session on 29 September 2026 will examine how Drupal content types, taxonomy, media, and workflows can be made available to AI agents through MCP, including questions around authentication and permissions. Another session on 30 September 2026 describes the use of MCP Server and MCP Tools in a broader agentic operations platform. Neither session is about MCPIO specifically, but both show that MCP-based connections between Drupal and external AI systems are becoming an active area of experimentation.