And book! That's a very exciting bit of tooling to add into an assistant, but there's lots of complexities...
Each result includes a booking link directly to the flight chosen
Oh well, we're not at the future we hoped for yet then, but it's progress.
- 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
> Servers MUST NOT use elicitation to request sensitive information
For any LLM based flows to gain enough trust by the general public to handle flows that involve money, esp large sums of money, we need the equivalent of “pad lock on my browser means I’m secure” level of something easy to understand and teach everyone to see.
I suspect the argument is going to get tricky, but the business interest will win out.