Amadeus CTO Says MCP Can't Handle Complex Travel Workflows — Experts Agree, Partly
The CTO of Amadeus, one of the world's largest global distribution systems, recently stated that the Model Context Protocol cannot manage complex retail workflows, sparking debate in travel tech circles. MCP has gained significant traction over the past two years, praised for enabling seamless AI-to-tool integrations across platforms. Critics and analysts note the CTO's concern is valid but partial — MCP excels at exposing discrete, atomic actions like search and pricing, but lacks built-in support for orchestrating multi-step, stateful processes such as bookings, refunds, and dispute resolution. Developers are advised to use MCP directly for read-only, high-frequency tasks, while relying on orchestration layers like LangGraph or server-side business logic for complex, compliance-heavy transaction flows. The consensus is that MCP is a powerful connection protocol, not a full transaction management system, and architects must decide which parts of a workflow belong at each layer.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in