3 posts tagged with "Standards"

Today, MCP Apps are live as the first official MCP extension. Tools can now return interactive UI components that render directly in the conversation: dashboards, forms, visualizations, multi-step workflows, and more. It is ready for production.

MCP Apps (SEP-1865) is a recent extension to the Model Context Protocol that lets a server hand the host an interactive UI rather than only text or structured JSON. The host renders that UI inside its own surface — Claude Desktop, ChatGPT and Cursor have all been moving in this direction — and the UI can call back into the server through the existing MCP transport.

The reason it matters is that a lot of the things people want agents to do are not really text-shaped. A pipeline view, a comparison chart, a form with validation, a sortable table — these have always been awkward to express as a tool response. MCP Apps gives them a first-class home without throwing out the auth, sandboxing or audit story that MCP already had.

When OpenAI integrated support for Anthropic's Model Context Protocol (MCP) into ChatGPT's deep research feature, they documented something elegant: a two-tool pattern that gives AI agents a consistent way to engage with any data source. If your MCP server implements search and fetch with their specific signatures, ChatGPT knows exactly how to explore your data without custom integration code.

Both tools accept only a single string parameter. That constraint isn't a limitation—it's what makes the pattern universal.