mcp-ui

The MCP clients are still missing some key features to get to a fully autonomous booking, but we are getting there: - With MCP Elicitations (https://modelcontextprotocol.io/specification/draft/client/e...) the server will be able to secure ask for complementary info like your name, passport and even your payments details. - With mcp-ui (https://github.com/idosal/mcp-ui), supporting MCP Clients could allow the server to re-create the same booking flow UI that you find today on an aggregator's website

Here's someone experimenting with what I mean: https://github.com/idosal/mcp-ui

Hey, We've just open-sourced MCP-UI, a project that provides lean client and server SDKs to enable passing rich, interactive UI components over vanilla MCP. We believe it'll enable a future where AI interaction will be based on UI snippets for interactive experiences. MCP-UI is meant to be a playground to bootstrap the initiative. Hopefully, through experimentation, the community can find the best way to enable this new future. Under the hood, the SDK enables any MCP server to respond with an EmbeddedResource with a "ui://" URI. The client SDK allows hosts to render it using a supported method (currently raw HTML or an external app) and handles follow-up interactions through events (e.g., further tool calls). We need better delivery methods, starting with React Server Components and Remote-DOM for better security. There are many other thi