Unknown Title

Key Concepts

• MCP (Model Context Protocol): An open standard that enables AI models to interact with external data and tools.
• MCP Apps: A new standard (SEP 1865) allowing MCPs to provide rich UI/UX elements instead of just text.
• SEP 1865: The technical proposal/standard developed by Anthropic, OpenAI, Microsoft, and the MCP UI team to standardize UI components in AI assistants.
• UI/UX Control: The ability for developers to define how information is presented to the user (e.g., charts vs. raw text).

The Problem: The "Wall of Text" Limitation

The current state of MCPs is hindered by a "text-in, text-out" limitation. While LLMs are powerful, the protocol historically restricted MCPs to returning raw text.

• Low Engagement: Data shows that 20% to 80% of users who install an MCP never use its tools more than once.
• Lack of Visual Context: When an MCP performs an action (like editing a file or fetching data), the AI often returns a vague confirmation like "I edited a block. Done." This leaves the user without visual confirmation or context.
• Cognitive Load: Relying on "walls of text" forces users to manually parse information, whereas visual representations (like charts) allow for immediate data comprehension.

The Solution: MCP Apps (SEP 1865)

To bridge the gap between AI logic and user experience, the industry has moved toward MCP Apps.

• Collaborative Standardization: In a rare industry alignment, competitors including Anthropic, OpenAI, and Microsoft collaborated on SEP 1865 (proposed in November, launched January 26th).
• Functionality: This standard allows MCPs to push UI components directly into the chat interface. Instead of just receiving text, the AI client can now render interactive widgets, charts, and specialized interfaces.
• Ecosystem Support: Major platforms including Claude, ChatGPT, VS Code, and Goose have adopted the standard. Popular integrations like Figma, Asana, Slack, Canva, and Box are already leveraging these capabilities.

Strategic Impact and Implementation

• Value Proposition: The speaker argues that if "images are worth 1,000 words," then a high-quality UI/UX is worth "10,000 words." By enabling rich UI, the utility and value of MCPs are expected to increase significantly throughout the year.
• Desktop Commander Case Study: Desktop Commander is actively transitioning to this new standard. In version 0.2.36 (released mid-February), they introduced their first UI widget, moving away from text-only responses to provide a more intuitive user experience.

Conclusion

The shift from "putting chatbots into applications" to "putting applications into chatbots" represents a fundamental change in AI interaction. By adopting the SEP 1865 standard, developers can move beyond the limitations of text-based protocols, providing users with visual, actionable, and efficient interfaces that significantly improve retention and usability. The future of AI assistants lies in their ability to render complex data through standardized, rich UI components.