MCP Apps becomes the first official Model Context Protocol extension, standardising interfaces inside assistants

2026-01-26 · Publisher : Model Context Protocol · Domain : Design, UX & UI

An MCP tool can now return an interactive interface (dashboard, form, visualisation) displayed in the conversation, from Claude to ChatGPT and VS Code.

What changes

  • Interfaces are served through the ui:// scheme and displayed in a sandboxed iframe.
  • Derived from MCP-UI and OpenAI's Apps SDK.
  • Supported at launch by Claude, Goose and VS Code Insiders, with ChatGPT the same week.
  • Hosts can require user consent for tool calls triggered by the interface.

### Background On **26 January 2026**, the **Model Context Protocol** blog announced that **MCP Apps** had become an official protocol extension, the first one. Proposed in November 2025, it builds on the community MCP-UI project and OpenAI's Apps SDK. ### Key facts - A tool declares a UI resource served through the **`ui://`** scheme; the host renders it in a **sandboxed iframe** that talks to it over JSON-RPC via `postMessage`. - Clients at launch: **Claude** (web and desktop), **Goose**, **Visual Studio Code Insiders**, and **ChatGPT** from the week of the announcement. - Security model: restricted iframe permissions, optional host review of HTML templates, loggable messages, and **user consent** can be required for UI-initiated tool calls. - Reference package: `@modelcontextprotocol/ext-apps`. ### Why it matters Until now, each assistant had its own embedded-interface format. A shared standard lets a publisher write a dashboard or form once and see it rendered in several assistants. For designers, the assistant becomes a full interface surface with its own constraints. ### Takeaway Generative UI gains an interoperable format; designing a view for an assistant becomes a product deliverable like any other.

Links

Tags : MCP, Generative UI, Assistants