MCP has this in the spec: it's called "elicitation", and I'm pretty confident this push from OpenAI sets the stage for them to support it.
Once a service can actively involve you and/or your LLM in ongoing interaction, MCP servers start to get real sticky. We can safely assume the install/auth process will also get much less technical as pressure to deliver services to non-technical users increases.
> Once a service can actively involve you and/or your LLM in ongoing interaction
Is there any progress on that front? That would unlock a lot of applications that aren't feasible at the moment.
Edit: Sampling is a piece of the puzzle https://modelcontextprotocol.io/specification/2025-03-26/cli...
I also see a lot of discussion on Github around agent to agent (a2a) capabilities. So it's a big use case, and seems obvious to the people involved with MCP.
And Dropbox is just an FTP server with SVN.
A lot of the fundamental issues with MCP are still present: MCP is pretty single-player, users must "pull" content from the service, and the model of "enabling connections" is fairly unintuitive compared to "opening an app."
Ideally apps would have a dedicated entry point, be able to push content to users, and have some persistence in the UI. And really the primary interface should be HTML, not chat.
As such I think this current iteration will turn out a lot like GPT's.