31–40 of 124 posts
Earlier quoted context omitted.
I wonder how long it'll take you to figure out that you're trying to reinvent deterministic APIs.
MCP is already deterministic. What's huge about it is that it has automatic API discovery and integration built-in. It's a bit rough yet but I think we will only see how it's getting improved more and more.
So, WSDL?
Disclosure: I work at Anthropic, have worked on MCP I also think this is pretty big. I think a problem we collectively have right now is that getting MCP closer to real user flows is pretty hard and requires a lot of handholding. Ideally, most users of MCP wouldn't even know that MCP is a thing - the same way your average user of the web has no idea about DNS/HTTP/WebSockets. They just know that the browser helps the…
The whole surface of the MCP specification is already pretty big, and barely any server implements anything beyond the core parts.
With elicitation there was already a lightweight version of this in place in the standard, and I'm not sure I've ever encountered a server or client implementation of it in the wild, and elicitation is an order of magnitude simpler to integrate on a conceptional level.
I fear that this has a significant risk of splintering the MCP ecosystem further (it's already pretty strained due to the transport protocol iterations), and there isn't really a reason to create a official extension (yet), that may worst case also require multiple iterations to get things right.
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.
Having a chatbot that drives websites inside of it is such an attempted monopolist play. Having a system agent that can interact with apps via API without being connected to the app is the pattern that's both elegant and preserves freedom.
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…
Who wants a button that has indeterministic actions?
google.com (1998-present)
[I'm feeling lucky]Am I missing something or is this essentially same as GPT Apps that have been introduced a while ago and have been discussed 10000 times.
A great example is Github, it's a significantly better dev experience having CC call out to the gh cli for actions than trying to invoke the MCP.
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.
Earlier quoted context omitted.
MCP is already deterministic. What's huge about it is that it has automatic API discovery and integration built-in. It's a bit rough yet but I think we will only see how it's getting improved more and more.
> automatic API discovery and integration So, WSDL?