Fact copy: Guide to MCP system integration

Factual summary

This knowledge page explains guide to mcp system integration as an engineering and governance problem. It distinguishes protocol behaviour, travel-domain rules, system ownership and evidence required for production use.

Preserving travel-domain semantics

Integration must preserve identities, traveller and order references, currency, tax and fee components, fare or rate conditions, freshness and transaction boundaries. A technically valid mapping can still be commercially wrong when it loses offer expiry, ticketing time limits or cancellation rules.

NDC, ONE Order, OpenTravel messages, proprietary GDS interfaces, PMS and CRS APIs are source contracts. MCP adds an AI-facing capability layer; it does not replace their domain semantics or make incompatible identifiers interchangeable.

Failure and consistency model

Capabilities that aggregate several suppliers must define partial results, timeouts, retry policy, deduplication and compensation. Before a write, the server revalidates inventory, price, authorization and the current order state.

Free-form database access should normally be replaced by bounded domain queries or parameterized views. This constrains both data exposure and the semantic ambiguity presented to an AI host.