New MCP Apps Demo by Giorgi Jibladze Set for Drupal AI Summit

The proposed extension, MCP Apps, aims to standardize a long‑standing community demand: allow MCP servers to deliver rich interactive UI (not just text or structured data) to clients. Under the draft specification (see SEP‑1865), UI resources are declared via a new URI scheme (beginning with ui://), and linked to tools through metadata definitions.

When invoked, the client can render the associated HTML interface — sandboxed in an iframe — and exchange messages with the server using the existing MCP JSON‑RPC transport over postMessage. This design enables structured, auditable communication while allowing dynamic, interactive interfaces within AI client environments.

The initial version supports only HTML-based UI resources (MIME type text/html+mcp), setting a baseline for future expansion. A fallback path to text-only responses remains valid for clients that do not support UI rendering, preserving backward compatibility.

According to Giorgi Jibladze, his proof‑of‑concept will use the MCP module for Drupal, showcasing how Drupal backend can deliver frontend components as native MCP resources — effectively transforming Drupal into a host for “agentic apps.” This marks a possible convergence between traditional web frameworks and emerging AI-assisted application platforms.

If widely adopted, MCP Apps could reduce the need for bespoke front‑end adapters for each client, prevent fragmentation, and promote a unified, secure approach to delivering interactive AI-powered experiences across platforms.

Developers and interested contributors can review the draft specification and explore the prototype SDK in the official MCP Apps repository. Early feedback and experimentation will help refine the extension’s design and adoption.