For two years the deal with AI assistants was simple and a bit grim. Your tool hands the model some text, the model hands you back some text, and if you wanted an actual button to click you built a separate web app and hoped anyone used it. That deal is changing, and most people running a small operation have not noticed yet.
MCP Apps is the extension that lets a tool render a real, interactive interface, a form, a booking calendar, a live dashboard, straight inside the chat window. It was the first official extension to the Model Context Protocol, the open standard that lets assistants like Claude and ChatGPT call your tools, and it has now been folded into the protocol’s finalised specification, published on 28 July 2026. The original proposal was co-authored by Anthropic, OpenAI and the community MCP-UI project, which is a rare bit of agreement between rivals.
What it actually does
Quick jargon check. Model Context Protocol (MCP) is the plug socket. A server exposes tools, search my tickets, book a slot, pull today’s numbers, and any MCP-compatible assistant can call them. Until now a tool could only reply with text or structured data. MCP Apps adds a third option: the server publishes an HTML interface as a ui:// resource, links it to a tool through a metadata field, and the host renders it in a locked-down iframe. Messages travel both ways over the JSON-RPC channel MCP already uses, so the panel can talk back to the assistant and the assistant can update the panel.
In plain English, your tool can now answer with a working calendar instead of a paragraph describing one. Interfaces render today across Claude, VS Code, Goose, Postman and MCPJam, with ChatGPT support rolling out. Test before you promise a client anything.
Why a solo operator should care
Every hand-off between a chat window and an external dashboard is a place people drop out. If a customer can confirm a booking, tweak a filter or approve an invoice without leaving the conversation, you lose fewer of them. This is the difference between an assistant that describes your business and one that runs a slice of it.
What to do this week
One, take a single tool you already expose over MCP, ideally one whose output is a mess of text nobody reads. Two, grab the MCP-UI SDK and wrap that tool’s result in a small HTML view, a table with a couple of buttons is plenty to start. Three, declare it as a ui:// resource and link it to the tool with the _meta field, exactly as the spec describes. Four, test it in more than one host, because a panel that behaves in Claude can misbehave elsewhere while support is still landing.
Two warnings. The iframe is sandboxed for a reason, so do not pass secrets or tokens into the interface and assume they are hidden. And keep the first version boring. A reliable form beats a clever dashboard that breaks the moment a client actually clicks it.
Did you know: the ui:// scheme is a deliberate echo of file:// and https://, a quiet signal that the people writing this standard want interfaces to be addressable resources like everything else on the web.
Related on Top Tool Stack: MCP goes stateless · Cloudflare’s agent rails