While they're at it, they might as well check if their answers end with a yes/no question, and, if so, offer a "yes" button so that i can answer yes with a single click.

> If you want a focused comparison next - for example, benchmarks on coding/math, token-cost examples for a typical session, or API usage differences - I can produce a compact table with sources and numbers.

--> can be answered with yes, so please add a yes button. A no button is not needed.

I dont think people realize how important this is.

If one of the vendors manages to get their protocol to become the target platform (eg oai and app sdk), that is essentially their vendor lock in to become the next iOS/Android.

Private API’s or EEE strategies are gonna be something to keep an eye for and i wish regulators would step in to prevent them before its too late.

Ah, yes, please add more security vulnerabilities to all apps, so I can tell a chat bot to tap a button for me!

Original title: MCP Apps: Extending servers with interactive user interfaces

The post title is quite editorialized.

Looks like OpenAI, Anthropic, and the MCP-UI team actually worked together on a common standard for MCP Apps: https://blog.modelcontextprotocol.io/posts/2025-11-21-mcp-ap...

Honestly, I think the biggest friction for MCP adoption has been how un-userfriendly it is. It’s great for devs, but not the average users. Users don't always want to chat, sometimes they just want to click a button or adjust a slider. This feels like the answer to that problem.

Full disclosure, I'm partial here because of our work at https://usefractal.dev. We were early adopters when MCP first came out, but we always felt like something was missing. We kept wishing for a UI layer on top, and everyone says it's gonna take forever for the industry to adopt, maybe months, maybe years.

I cannot believe the adoption comes so quickly. I think this is gonna be huge. What do you guys think?